Open inctiveo opened 1 week ago
@qdm12 is more or less the only maintainer of this project and works on it in his free time. Please:
I believe I'm experiencing the same issue here. But with the lack of logs decided to hold off on creating an issue until I could investigate more.
I'm curious, if you docker exec into one of your containers that uses gluetun while it's having that issue does it show that the network interfaces were removed? For example when my containers are working properly I believe they have 3 network interfaces active, and when they are having an issue I've noticed that only the lo: interface is active.
Edit: Looks like this could be a related issue https://github.com/qdm12/gluetun/issues/2469
I'll check the next time it happens which tends to be every other day. At the moment I manually redeploy to keep things working. I'm unsure if this is related but when I was running containers individually I never experienced this issue but I started using docker compose, as it does make my life easier but since doing so I've been having these issues with gluetun connected containers becoming inaccessible.
You're absolutely right, it seems to be a common issue if you check the recent comments on #405
Is this urgent?
No
Host OS
Synology DSM
CPU arch
x86_64
VPN service provider
ProtonVPN
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2024-08-25T07:04:32.409Z (commit 01fa993)
What's the problem 🤔
The containers running on the gluetun vpn network randomly become inaccessible after a matter of hours or days if I'm lucky. I have tried many different solutions by changing my docker compose file without success. There are never any errors in the logs for any containers that I can see, I'm lost here.
Share your logs (at least 10 lines)
Share your configuration