strike

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.

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