qBit is showing and acting as firewalled but setup is correct in Gluetun (sh.itjust.works)

submitted 8 months ago* (last edited 8 months ago) by jws_shadotak@sh.itjust.works to c/piracy@lemmy.dbzer0.com

14 comments fedilink hide all child comments

Setup:

Debian running podman. Containers and compose files are managed with Dockge. qBit and Gluetun are on a single compose file and all qBit traffic is routed through Gluetun.

qBit seems to starts first before Gluetun is fully set up and qBit doesn't see the open port. Every time I start them together, I have to manually restart qBit again once Gluetun is ready. Once it's restarted, it shows as open and connected again.

I tried looking for ways to delay startup in a compose file but I didn't get any results.

Is there a solution to this?

https://pastebin.com/kgqt8aJ7

you are viewing a single comment's thread
view the rest of the comments

[-] jws_shadotak@sh.itjust.works 1 points 8 months ago

Torrents are stalling and it's only seeding about 600 KB/s. The icon at the bottom shows a little flame and the hover text says "firewalled".

Restarting qBit through the Dockge web terminal turns that flame icon into a globe and it starts finding hundreds of DHT networks. Uploads nearly max out my upload bandwidth.