O_M_R

This is going to be exactly my problem. For some reason I got all caught up in the Gluetun setup I completely overlooked 1 app 1 port and basic networking left my brain. Ironically my next stop when I got in front of the server again tonight was going to be changing the start order to deluge second to see what happened. Thanks for taking the time!

I've been trying to set this up for the past few days and I'm kind of at a loss, I'll explain where I'm at: I have the Gluetun container, it's working with protonvpn over wireguard - all good. I'm using it with download clients (Deluge) without any issue, also threw some other stuff behind there as well using the container network of Gluetun - everything's great. However.... Soulseek I can't get going. I think it's something to do with the script for updating the gluetun port. If Soulseek isn't connected to the container network, the webgui is reachable on 8980 and 8990 If Soulseek IS connected to the Gluetun container network but Gluetun updating the incoming port is set to NO and 8980 and 8990 are exposed on the Gluetun container = GUI Reachable. If Soulseek IS connected to the Gluetun container network and Gluetun updating the incoming port is set to YES and 8980 and 8990 are exposed on the Gluetun container = GUI Unreachable. I have no idea what's going on in the backend causing Gluetun to just... stop working. Deluge updates just fine using the methodology and everything is reachable. Thanks again for all your efforts.