mirror of
https://github.com/plankanban/planka.git
synced 2025-12-15 17:23:19 +03:00
Docker build not accepting connections #808
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rickyelopez on GitHub.
Maybe I'm doing something silly, but don't see where I could be messing up...
docker-compose.yml:
Can't connect at all (double checked port is open), I see this error in the docker-compose logs on first startup, no errors following that:
Any other info I can provide to be helpful?
@rickyelopez commented on GitHub:
OK makes sense. I tried with the hostname and the ip, nothing. I also tried using the hostname, localhost and 0.0.0.0 in the base url in the docker-compose.yml. Tried different ports too. No luck
@meltyshev commented on GitHub:
Ah no, it's an ok error, I have the same. It happens because Postgres doesn't have enough time to initialize (it fixes by retry timeout in the command section). What address do you use in the browser to access Planka?
@meltyshev commented on GitHub:
Hi! It seems that the server cannot connect to the database. Do you have postgres service in the docker-compose.yml?
@rickyelopez commented on GitHub:
Could it be because the containers that end up getting created are called
planka_postgres_1andplanka_planka_1but the docker-compose refers to the postgres server withpostgres/planka?@rickyelopez commented on GitHub:
Hi there! Yes, I do, I'm pretty much using the sample docker-compose.yml. See below for full docker-compose.yml file:
@rickyelopez commented on GitHub:
Yes the output of that command is as expected. I'm running about 5 other apps through docker containers, and all of the rest of them are accessible, so I doubt it's a network thing...
@meltyshev commented on GitHub:
It looks like the server is properly lifted, so something in the network or docker settings. Try to exec
docker container lsit should be0.0.0.0:[YOUR_PORT]->1337/tcpin the PORTS column. Can you try to run some other app like Rocket.Chat?@rickyelopez commented on GitHub:
Here's a full log, maybe that will point to something:
@rickyelopez commented on GitHub:
Nevermind, just tried adjusting the url in docker-compose.yml accordingly and it didn't change anything
@peterk commented on GitHub:
I tried to reproduce this error but could not. My docker environment is on Windows 10 with the Linux subsystem. I set ports to
4000:1337andBASE_URL=http://localhost:4000docker psgives0.0.0.0:4000->1337/tcpWhat is the output of
docker-compose exec planka wget -qO- 'http://0.0.0.0:1337'? Is the web server in the container responding?@zahidhanif commented on GitHub:
I had the same issue was really disappointed because I wanted to get give this a go. Instead of using docker compose, I used the docker CLI. I created a separate Postgres container for shared databases across containers, a Postgres network and it all ran fine. I can post my docker CLI code if anyone is interested.
@phrogg commented on GitHub:
For me the problem was related to planka not finding postgres (I'm using Portainer). I fixed it by changing this line:
- DATABASE_URL=postgresql://postgres@postgres/plankato my the ip of my portainer machine:- DATABASE_URL=postgresql://postgres@10.10.10.10/planka.@kaythomas0 commented on GitHub:
I was running into this same error, I fixed it by changing the postgres container's image to
postgres:12-alpinein the docker-compose file.@vorwd commented on GitHub:
I also had this issue, and it was due to my Nginx Proxy Manager setup. Had the proxy configured properly, with websockets enabled, but forgot to setup a stream for the database. Added a proxy stream with the protgres port pointing to postgres container and all started working.
@phrogg commented on GitHub:
I have the same issue, anyone found out something?