second connect to postgres fails
after a container is deployed (after the initial deployment) this error occurs when trying to connect to it via DATABASE_URL
Solution:Jump to solution
no worries. it seems to be fixed after destroying it and recreating it. it was an old project
7 Replies
Project ID:
17ebdb2c-d451-4fe9-997a-dd53742e883a
17ebdb2c-d451-4fe9-997a-dd53742e883a
i am able to connect to the db from the public url, i am able to see the previous deployment's migrations as well
if i delete the database and recreate it, the first deployment / connection to it works, then i redeploy a service and it can no longer be connected to
we cant help without a project, can you provide an id for a new project?
i decided to try to reconstruct it. tearing it down and rebuilding it in the same config did the job. i also noticed that i was unable to change the port. maybe a state from the project being so old? anyway, issue is gone now
we have never allowed you to change the proxy port, it is random
ah, no, the port going out to the generated url
in the service that was connecting
Solution
no worries. it seems to be fixed after destroying it and recreating it. it was an old project