#container twenty-server-1 is unhealthy

1 messages · Page 1 of 1 (latest)

copper anvil
copper anvil
merry scroll
#

Misconfigured database url?

#

Make sure your postgres is alive and healthy and that the credentials are correct/matching

copper anvil
#

man i really dont know a lot about databases, linux etc.
i just wanted a free crm lmao
i can send you my .env though

merry scroll
#

You should uncomment both Redis URL and PG_DATABASE_HOST

copper anvil
#

still the same

image.png
#

same error in logs also

image.png
merry scroll
#

Well now it doesnt complain that it cant connect to the database. Now the issue is, the username/passwords are not matching

copper anvil
#

i left name on default though

merry scroll
#

Check the env variables directly on the container

#

if they are the same

copper anvil
#

how do i do that

merry scroll
#

docker inspect container <container_id>

#

replace the <container_id> with the actual ID

#

you can get the id using docker ps

copper anvil
#

should i check
twentycrm [twenty-server-1] [this gives me an error in basic installation]
or
postgres:16 [twenty-db-1]

merry scroll
#

well both

#

I dont think the container must be running in order to inspect it

#

Just need to make sure that PG_USER and PG_PASSWORD are matching in both

#

Another trick that might work is by adding

      - .env

to both postgres and twenty compose services

copper anvil
merry scroll
#

Yep seems to match.

#

Try downing the deployment and removing the volumes with docker compose down -v

#

and upping again

#

Could be a different password for postgres user was initialized before

copper anvil
#

😭 😭 😭 😭

image.png
merry scroll
#

Wait its still unhealthy?

copper anvil
#

yeah

merry scroll
#

Any errors now?

copper anvil
#

wait a sec, im trying to run a solution right quick which somebody found helpful

image.png
merry scroll
#

but that would only reset the db

#

doesnt help with the fact that your container is unhealthy

copper anvil
#

worth of shot i think

#

.......

merry scroll
#

But since youve downed and removed the volumes, the deploy should be clean

#

imo the easiest solution would be to just create a new folder, go step by step from the docs and try it out again

copper anvil
#

and i dont see any particular errors

#

everyting seems fine, at least for my eye

#

server-1 | Successfuly migrated DB! but still this twenty-server-1 is unhealthy

merry scroll
#

Eh who cares

#

its accessible

copper anvil
#

WAASDASDSA

#

YEA

#

man

#

thanks

#

i love you

merry scroll
#

I mean its just a health check

#

those can have false positives as well

#

but usually they do indicate errors

copper anvil
#

so everything cool?

merry scroll
#

Yeah as long as its working fine

#

and not spitting out any errors

copper anvil
#

thanks

#

a lot

#

really

merry scroll
#

btw you should change your passwords now 😄

copper anvil
#

for sure 🤣

merry scroll
#

as you've exposed them publicly, along with your IP 😄

copper anvil
#

yeahh, i will redirect it to main domain though

#

and hide the ip thing

merry scroll
#

Technically, you wont be hiding it 😛

#

It will just be mapped to a domain