container twenty-server-1 is unhealthy

Original message was deleted

kajn•4/22/25, 10:37 PM

Kkajn Click to see attachment

kajn•4/22/25, 10:37 PM

docker compose logs

xBlaz3kx•4/22/25, 10:44 PM

Misconfigured database url?

xBlaz3kx•4/22/25, 10:45 PM

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

kajn•4/22/25, 10:48 PM

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

kajn•4/22/25, 10:48 PM

xBlaz3kx•4/22/25, 10:49 PM

You should uncomment both Redis URL and PG_DATABASE_HOST

kajn•4/22/25, 10:51 PM

still the same

kajn•4/22/25, 10:51 PM

same error in logs also

xBlaz3kx•4/22/25, 10:51 PM

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

kajn•4/22/25, 10:52 PM

i left name on default though

xBlaz3kx•4/22/25, 10:52 PM

Check the env variables directly on the container

xBlaz3kx•4/22/25, 10:52 PM

if they are the same

kajn•4/22/25, 10:53 PM

how do i do that

xBlaz3kx•4/22/25, 10:55 PM

docker inspect container <container_id>docker inspect container <container_id>

xBlaz3kx•4/22/25, 10:55 PM

replace the <container_id> with the actual ID

xBlaz3kx•4/22/25, 10:55 PM

you can get the id using

docker ps

docker ps

kajn•4/22/25, 10:57 PM

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

xBlaz3kx•4/22/25, 10:57 PM

well both

xBlaz3kx•4/22/25, 10:57 PM

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

xBlaz3kx•4/22/25, 10:58 PM

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

xBlaz3kx•4/22/25, 10:59 PM

Another trick that might work is by adding

   env_file:
      - .env

   env_file:
      - .env

to both postgres and twenty compose services

kajn•4/22/25, 11:00 PM

whole lotta text in there

message.txt16.1KB

message.txt12.42KB

kajn•4/22/25, 11:02 PM

xBlaz3kx•4/22/25, 11:02 PM

Yep seems to match.

xBlaz3kx•4/22/25, 11:03 PM

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

xBlaz3kx•4/22/25, 11:03 PM

and upping again

xBlaz3kx•4/22/25, 11:03 PM

Could be a different password for postgres user was initialized before

kajn•4/22/25, 11:04 PM

xBlaz3kx•4/22/25, 11:05 PM

Wait its still unhealthy?

kajn•4/22/25, 11:05 PM

yeah

xBlaz3kx•4/22/25, 11:05 PM

Any errors now?

kajn•4/22/25, 11:07 PM

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

xBlaz3kx•4/22/25, 11:08 PM

but that would only reset the db

xBlaz3kx•4/22/25, 11:08 PM

doesnt help with the fact that your container is unhealthy

kajn•4/22/25, 11:09 PM

❓︱helpContainer twenty-server-1 Error

here i saw similar case

kajn•4/22/25, 11:09 PM

worth of shot i think

kajn•4/22/25, 11:11 PM

kajn•4/22/25, 11:11 PM

.......

Kkajn https://discord.com/channels/1130383047699738754/1331189052216705034 here i saw...

xBlaz3kx•4/22/25, 11:12 PM

Yeah sounds like a similar issue, which is likely a database provision issue

xBlaz3kx•4/22/25, 11:13 PM

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

xBlaz3kx•4/22/25, 11:13 PM

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

XxBlaz3kx Any errors now?

kajn•4/22/25, 11:15 PM

i runned through logs

kajn•4/22/25, 11:15 PM

and i dont see any particular errors

kajn•4/22/25, 11:15 PM

everyting seems fine, at least for my eye

kajn•4/22/25, 11:16 PM

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

xBlaz3kx•4/22/25, 11:16 PM

Eh who cares

xBlaz3kx•4/22/25, 11:16 PM

its accessible

xBlaz3kx•4/22/25, 11:16 PM

http://91.99.75.50:3000/create/workspace

Twenty

A modern open-source CRM

kajn•4/22/25, 11:17 PM

WAASDASDSA

container twenty-server-1 is unhealthy

Similar Threads

Similar Threads

Similar Threads