-
-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: qbittorrent works with "container:gluetun"
but not with "service:gluetun"
#2452
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
Maybe #1697 (which I need to do soon ™️) would help, I'll report back here once this is implemented. |
"container:gluetun"
but not with "service:gluetun"
I don't know, that one sounds like an issue related to port forwarding to be reachable from the outisde. When the issue is currently happening and all trackers are unreachable, I can still ping the outside world from inside the qB container. I can also have a download going, in case the client still remembers some of the peers from before the issue occured. If this were truly related, my guess is that if I stop forwarding the port, the issue should go away. If it doesn't go away, then it is not related to that other issue. Yes? Does that make sense? |
Is this urgent?
No
Host OS
Ubuntu Server 22.04
CPU arch
x86_64
VPN service provider
Windscribe
What are you using to run the container
Portainer
What is the version of Gluetun
Running version latest built on 2024-08-25T07:04:32.409Z (commit 01fa993)
What's the problem 🤔
As per the wiki, containers defined in the same compose/stack should be connected to gluetun via
network_mode: "service:gluetun"
. When done this way, qBittorrent does not work: It cannot connect to any tracker, does not find peers, etc. and will just complain that everything is unreachable. I can ping the outside world fine from within the qb container, though.When I separate the qb part from the same stack into a new one and only change the network mode to
network_mode: "container:gluetun"
, it works just fine.Edit: This is so weird, sometimes it just works with both containers in one stack. I can't see any difference in the logs, though. I'll start the exact same compose and suddenly it just works. After another restart of the stack, it won't work any more, except sometimes it will. Again, ping always works from within the qb container, which seems even weirder.
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: