strike

The Netherlands was dropped from the port forwarding list, try one of the other supported endpoints. If you still have issues please enable debug logging in the container template, and post the complete supervisord.log file (be sure to redact your username/password first) located in your appdata folder.

Are you securing your reverse proxy with basic auth? For some reason ombi doesn't like that. At least I cound't get it to work properly with basic auth, I got weird ui issues last time I tried.

https://forums.unraid.net/topic/46281-unraid-autovmbackup-automate-backup-of-virtual-machines-in-unraid-v04/

There's no reason you can't run both containers simultaneously, you just need to check there are no conflicting ports and that you're not exceeding the number of vpn connections that are allowed. I've never used sabnzb so I don't know which ports it's using other than the privoxy port. Regarding privoxy if you want to use that, you only need to enable it on one of the containers as I mentioned. And it doesn't matter which one it is. Privoxy is just for routing other apps/web browsers through you vpn enabled connection. And there's really no need for 2 proxies. And from the FAQ: For sabnzb:

This can happen if you haven't put a cap on your upload speed, and maybe have a crappy router. Torrenting is very taxing on the router as it opens hundreds of connections. The first thing you need to do is limit your upload speed in the torrent client to 80% of what your connection can handle. If you don't do this, symptoms like what you're seeing can happen. If you still have issues after doing that, it could mean that your router is having trouble with that many connections and you should limit this in the torrent client.

Privoxy is running on port 8118. You'll need to remove the port mapping for that port on one of the containers. Or maybe it works if you just disable privoxy on one of them, I can't really remember. In any case, you only need privoxy running on one of the containers. If you still have issues please enable debug logging and post the complete supervisord.log file located in your appdata folder. And Tyler, (I'm just guessing that's your name) you should also change your PIA password asap. Mods will probably remove the screenshot as I reported your post. Edit: And if you're posting your log file be sure to remove your PIA username/password first.

Not having an open incoming port and trying to download torrents on a private tracker has this "symptom". Or grabbing the torrent from "outside the vpn tunnel" on a private tracker, such as from your laptop which is not connected to the vpn tunnel and adding the torrent in delugevpn. Then the tracker sees the IP from the laptop and expects that same IP to show up when adding the torrent in delugevpn, but since deluge are connected to the vpn tunnel it sees a different IP and are not able to connect.

Not that I know of. I haven't really researched it tho.

Deluge doesn't handle many torrents that well, this is a known issue. You should try rtorrentvpn instead which is reported to handle many torrents better.

Cool, wasn't aware I could do that.

@linuxserver.io @CHBMB Would you be able to add SQLite to this container? I need to run SQLite in the container to try a fix for an issue I have. Please see https://github.com/tidusjar/Ombi/issues/2444 for more information. Would be awesome if I could get this solved, If not I'm afraid I can't use this container.

The only thing you need to do is enable strict port forwarding and connect to a supported endpoint, the rest is done automatically.

There is only one correct combination to reach the webui and it's HostIP:8112 If it doesn't work you need to enable debug logging and post the complete supervisord.log file

@snowfitz Try changing your lan_network to 192.168.0.0/24

You can use the file activity plugin which logs every read/write on the disks so you can figure out what's happening. Knowing that you might also figure out why it's happening. The open files plugin might also be helpful to figure out what processes uses the files in question.