Repository navigation
Replies: 1 comment
|
Hi @xloyb, During the next outage, please run these before restarting Docker and share the output: traefik_id=$(docker ps -q --filter label=com.docker.swarm.service.name=easypanel-traefik | head -n 1)
docker exec "$traefik_id" wget -S -T 5 -O /dev/null http://easypanel:3000
docker exec "$traefik_id" wget -S -T 5 -O /dev/null http://tasks.easypanel:3000
sudo systemctl is-active firewalld
docker service logs easypanel-traefik --since 1h --tail 100 --timestamps
sudo journalctl --since "1 hour ago" -u docker -u firewalld -u NetworkManager --no-pager
sudo journalctl -k --since "1 hour ago" --no-pagerThe first two checks help distinguish a Docker service-address problem from broader container connectivity issues. Please also mention:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I'm experiencing a recurring and frustrating issue where all my applications suddenly become inaccessible and show Bad Gateway, without any apparent reason — no server reboot, no deployments, nothing changed.
What happens:
What I found via SSH:
Traefik loses connectivity to other containers over Docker's overlay network. Even though all containers are running, Traefik can't reach them internally:
The overlay network becomes corrupted at the kernel level, containers are listed as connected but packets can't travel between them.
The only fix that works:
This rebuilds Docker's overlay network routing tables and everything comes back within 60 seconds.
My questions:
Environment:
This is happening repeatedly and is causing unexpected downtime. Any help or insights from the team or community would be greatly appreciated!
All reactions