SomeDudeUsingDockers

Try "localhost" for Hostname. And possibly only 10.0.0.19 for ignored.

I think it can also happen with .torrents too. Keep an eye on whether AutoAdd has unchecked itself in options, that's the tell tale sign. You can also try this container: binhex/arch-delugevpn:2.0.3-2-01. That was the last one that worked for me before this broke. Only downside is that one in theory can leak IPs in certain rare cases. But if that works, and the latest doesn't, it's the same issue. But the way you described it is exactly how it played out for me, intermittent, hard to pin down, still can manually add torrents fine, but always eventually breaks the watch folder and unchecks the box too (usually).

This sounds like it could be exactly what I posted about a few posts back. If that Chrome plugin relies on using Deluge's watch folder (aka AutoAdd) to watch for magnet links, I'd look at my post and try that fix.

AutoAdd Issue in Deluge First, let me say that I've benefited greatly from this container and the help in this thread, so thank you all. And although I'm running the container on a Synology unit, I thought I'd finally give something back here for anyone who may be having a similar issue. Background Container was running great for me up to binhex/arch-delugevpn:2.0.3-2-01, but any time I upgraded past that I had problems with Deluge's AutoAdd functionality (basically its "watch" directory capability that was formerly an external plugin that is now baked into Deluge itself). Certain elements worked like Radarr/Sonnar integration, but other elements broke, like when I used manual search inside Jackett, which relies on a blackhole watch folder. I ended up just rolling back the container, it worked fine again, and I stopped worrying about it for a while. However, with the new (rare) potential for IP leakage, it's been nagging at me to move to the new container versions. Initially, I wasn't sure if it was the container, the VPN, or Deluge itself, but it always kind of felt like Deluge given the VPN was up, I could download torrents, and Radarr/Sonarr integration worked -- it was only the AutoAdd turning itself off and not behaving itself when using Jackett manual searches that wasn't working. I'm actually surprised I haven't seen more comments about this here because of how AWESOME using Jackett this way is! (Y'all are missing out, LOL). The Fix I finally put my mind to figuring this out once and for all yesterday, and I believe I tracked it down. Turns out the baked-into-Deluge AutoAdd is currently broken for certain applications (like watching for Magnets), and that version is in the current BinHex containers. Even though the fix hasn't been promoted into Deluge yet (so of course not in the container yet either), there is a manual fix available, and it's easy (just drop an updated AutoAdd egg into the Deluge PlugIns folder and it will take precedence over the baked-in version). I will say that I literally just implemented and tested, so it's possible I'll still run into problems, but it's looking promising at the moment. Thanks again for this container and this thread, enjoy! The temporary fix can be found here

Ah ok, my bad. Interestingly, I had it setup for the past year and things seemed to be working well until the new container versions with the security updates. Then my incoming port wouldn't show. I just removed the ENV for this, and the old container still works, and the new version now looks to be working, so THANKS!

Could someone help me with how to properly setup an incoming port down my VPN to be used for Deluge/torrent connections? I used to use ADDITIONAL_PORTS, but now with the new container my incoming port seems closed From the outside world. I have all the other issues in this thread working well with the new version except this, but I see no documentation on it except I think I saw something saying don’t use INCOMING ports? Thanks!

I'm a bit of a docker newb and not particularly network savvy, but I've been using 2.0.3-2-01 successfully for a while now. I've tried to upgrade a few times recently and it didn't go well. I've read this whole thread, the FAQs, etc. I think I have most everything working and talking to each other with the new version (Radarr, Sonnarr, Jackett, Bazzarr all using privproxy via localhost and excluding local IP, and VPN is up and Deluge working). However, my incoming port for Deluge over my Torguard VPN connection seems closed (not using PIA). I was using additional ports successfully previously, but not sure if I should be using input or output port environmental variables now? I'm honestly having a little trouble understanding some of the changes, but otherwise my setup is fairly straight-forward (I'm not sharing same network between dockers, only using privproxy as mentioned above). When I check the port, no one responds. When I roll back to 2.0.3-2-01, works fine. Any tips? And thanks for these awesome dockers/tools!