strike

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.

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:

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

Wow, no wonder you find that off-putting. But you know goggle is the most powerful search engine out there, more people should really spend more time learning what googles search commands can do for you in a search. There's a bunch of helpful powerful commands you can put in your google search. The number one command all should learn is the "site:" command. Which does exactly what you want, it searches the site you want and not all the internet. I never use the search function on any web page, I always use google.. If you want to search this thread for key words you just put "site:https://lime-technology.com/forums/topic/70511-search-within-a-forumtopicthread what you want to search for" whitout quotes and that's the equivalent of "search within a forum/topic/theard If you use google for your standard search engine it's really simple to copy the webadress in the adress bar, hit ctrl+t for a new tab, type site:"hit ctrl+v" to paste then type what you want to search for. It litteraly takes 2 seconds.. I bet it would take that 2 seconds or even more to use a built in search on any web page. Most bulit-in search functions on sites are just crap anyway. Google FTW, I mean, search is what they bulit their emperium on... If you have used the internet in the last 10+ years you should really know how to search the internet.. So for all you out there saying you need a search function to not sit for hours to search every page of a site, I suggest you search google for "useful google search commands" or "how to use google search". This will not only help you, but the whole internet! Thank you!

As I said in my previous post all the port forwarding is done automatically for you if you're using PIA. So you should NOT try to set an incoming port yourself. There's a script in place to change the port if you get a new port form PIA. So just make sure you have "strict port forwarding" enabled in the container settings and connect to an endpoint that supports port forwarding, thats' it. Have you followed the other tips? Set a limit on your upload speed or try another endpoint etc..

Yes, first of all, close all the ports you have opened on your router. You are connected to a server on PIA, think of it as you're sitting physically on a machine in PIA's network. So opening ports on your own router won't do anything (apart for decreasing security). You have to open a port on the VPN provider side. Luckily for you, this is done automatically for you in this container (if using PIA). All you have to do is connect to an endpoint that supports it and enable "strict port forwarding" in the container settings. For a list of endpoints that supports port forwarding see this list: https://www.privateinternetaccess.com/helpdesk/kb/articles/how-do-i-enable-port-forwarding-on-my-vpn And for more tips on what can cause slow speed see Q5: https://lime-technology.com/forums/topic/44108-support-binhex-general/?tab=comments#comment-433613

Ok, so I deleted the appdata for this container, nuked my docker image and downloaded all my containers again, still the same issue with a fresh container. Nobody else is having this issue?

Yeah,I thought so. Thanks for confirming :)

Anyone seeing very high disk IO with this container? I have an issue with constant writes to the cache drive. In 13 days my cache drive has over 81 million writes.. I'm afraid my cache disk will die on me long before it's supposed to if this keeps going on. I used the file activity plugin to log whats happening and I've included the output in the txt file. Keep in mind this is just 1 hour worth. So Imagine this all day, every day, 24/7... This started when I replaced my cache disk one month ago, at least that's when I started noticing the very high write count. Before I nuke my docker Image and try again I thought I ask here if anyone else is seeing this? ombi.txt

Shouldn't be, but anything is possible I guess. Should be to just stop the container, replace the ovpn file and start the container again. If it's not working you'll need to post a new debug log. Maybe you replaced the ovpn file with another wrong one like you did with Sweden?

No, check this list: https://www.privateinternetaccess.com/helpdesk/kb/articles/how-do-i-enable-port-forwarding-on-my-vpn I would try Germany, France or Canada

Where did you get the .ovpn file from? The server listed in your ovpn file is down. Try the one from this zip: https://www.privateinternetaccess.com/openvpn/openvpn.zip

Using blocklist while you're using vpn is pretty useless as @binhex once said: https://lime-technology.com/forums/topic/44109-support-binhex-delugevpn/?do=findComment&comment=598299 https://lime-technology.com/forums/topic/44109-support-binhex-delugevpn/?do=findComment&comment=598301

It's in the log, so you should change it asap. If you still can't get it to work after doing what @jonathanm said, please edit the container and set the DEBUG variable to "true", delete the supervisord.log, then start the container and let it run a few min before you post a new log

Ok. Early on in your log you were having authentication issues possibly due to the special characters in your password. It looks fine at the end of the log though (no more authentication issues), but these things with special characters can be unpredictable. It doesn't look like you have to have an e-mail address as your login, you can have a username, but it doesn't say how to change it. If they were offering a trial period you could simply just create a new account and try with another username, but it doesn't look like that they offer that? Maybe you can contact support about changing the login? Other than that I'm not sure what could be causing the issue. Maybe you can try a different browser if you haven't tried it. And as I mentioned earlier you can try to nuke the docker image and re-download all your containers using CA's previous apps. You don't have to configure anything and you won't lose any settings/data. If you don't know how to do it just ask I'm not sure it will have any effect in this case, but you said it has been working for months and then suddenly it stops so it could be worth a try. Recreating the docker image has helped me more than once.

And to be clear, you're not reaching the webui at all or do you reach the webui but it's blank? The warning about special characters in your password is gone, but it still complains about your username, you're sure it does not contain any special characters? Everything else seems to be ok.

I can't see anything wrong in that log, but you need to post a debug log. Edit the container and set the debug variable to "true", start the container and let it run for a few min. Then post the entire suprervisord.log file (remove username/password. Also, is your unraid server IP 10.10.10.x? Do you have any special characters in your username/password? This container only supports characters 0-9, a-z,A-Z any other characters can cause issues.