I did a full reinstall recently in another thread here and everything was working fine until it wasnt. I havent really done any big changes aside from whitelisting my plex port and setting up port forwarding. The issue is that I cannot reach qBittorrent anymore. It seems that the container cannot be started as well (see error below when restarting yams). I've checked the logs but nothing really pops out here either. Any ideas what I can do to get it working again?
Hey @tdog!
There's a problem either with your network or your docker install. It's really hard to know without knowing your custom modifications.
Cheers!
Roger.
Hey dude! Thanks for chiming in again.
Do you think I should whitelist gluetun in my firewall as well (and do you know how)? I played around with it when I had to make Plex remotely accessible with port forwarding. I tried enabling the firewall first I think and afterwards installed a GUI so that I could easily create some rules for my Plex port. I imagine there must have been a firewall of some shape or form since without my intervention Plex wasn't remotely accessible but I'm not sure.
I did notice that I didn't have my 'Private Internet Access' credentials in the compose yaml but filling those in didn't change anything either unfortunately. It created a new container it seems and adding all those ports to my firewall exceptions didn't make a difference either I've read online that the network namespace issue most likely refers to the VPN that's malfunctioning.
If that's not it, you think I can easily reinstall qBittorrent without having to do a full reinstall?
qBittorrent goes trough Gluetun, so definitelly allow it in your firewall.
