steamedhams

UDP servers work with Deluge, in fact it's much faster than TCP, but privoxy only seems to work when using TCP servers. I wonder what could cause this behavior?

Sorry for the (maybe?) double post. As you were responding I edited my post with the solution. UDP VPN servers aren't working for me. Maybe related to me using docker-compose?

Unfortunately, it's still not working. EDIT: When I was using NordVPN I found that using a UDP server never seemed to work with Privoxy. Changed the PIA server to a TCP one and bam it worked flawlessly. I haven't seen anyone else with this issue as far as I can tell. I'm primarily using docker-compose to build/run my containers. Could this issue be caused by not exposing the DelugeVPN ports over UDP?

I switched from NordVPN to PIA to try to increase Deluge's speed, and it works fine, but for some reason Privoxy doesn't seem to be working. Sonarr and radarr can't connect to any trackers and tests on a browser fail. Pretty strange since obviously Deluge is successfully connecting to the VPN. I've included the logs. Any help would be greatly appreciated. supervisord.log

I'm having significant issues getting DelugeVPN to work. Every fifteen seconds or so it soft resets even though it successfully connects to NordVPN. I can access the deluge webgui no problem, but proxy connections only get a few seconds of uptime between resets. My docker run parameters are here: pastebin link. I've included the full logs with this post. I'm not running in a standard linux distro (using rancherOS), but I've tested in a ubuntu vm and it behaves in the same way. Also I'm using a TCP server from NordVPN because as far as I can tell UDP servers simply don't work at all. Any assistance would be appreciated. EDIT: I had the test VM instance of DelugeVPN running in the background for about five hours and it seems to have stabilized. I don't know if that would continue if I restarted the container though. I'll include the log files for this as well, even though it wasn't running in debug mode. EDIT 2: I just realized that my problems (at least the recent ones) were caused by having two instances running on the same internal network. Every time I would turn one off the other would start working. I suppose this will be useful to anyone in this exact scenario in the future. supervisord.log vm-supervisord1.log vm-supervisord2.log