However, the scripts and iptables are adding functionality of restarting deluge and the VPN when the VPN goes down and you can direct only deluge to use the VPN if wanted and use regular connection for everything else.
Post by mhertz » Fri Sep 16, pm Yes indeed, though it also works fine with e. PIA, which the OP uses. I recently gotten PIA also and set it up like described above i,e, only for torrenting and everything else goes through normal connection. I use linux though, where its much easier to setup than windows. I'm trying to figure out if I want VPN or socks5 proxy in the feature. Also, it's a possibility to use a VM only for torrenting, where you run your torrent-client through a sandboxed environment with only the VPN as connection to outside.
Some added overhead indeed, but still a viable solution used by many. This is also very easy for windows users. Just install e. Post by Team » Tue Sep 05, pm This is also very easy for windows users. And actually the upload speed in horrendous. Using PIA nl because it was default. Should be no different if hardware is capable of handling the encryption. What profile do you use with the Windows PIA client? You can post now and register later.
If you have an account, sign in now to post with your account. Note: Your post will require moderator approval before it will be visible. Restore formatting. Only 75 emoji are allowed. Display as a link instead. Clear editor. Upload or insert images from URL.
Sign In. Followers Reply to this topic. Recommended Posts Recommended Posted by binhex , February 25 There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A new image has now been rolled out for all vpn enabled docker images 25th Feb i produce with the fix in place, i would encourage everyone to update to the recently created 'latest' tagged image.
You can force the upgrade by toggling 'basic view' to 'advanced view' and then clicking on. Posted January 21, edited. Overview: Support for Docker image arch-delugevpn in the binhex repo. Link to comment. Replies 9k Created 5 yr Last Reply 2 dy. Top Posters In This Topic Popular Posts binhex February Posted Images.
Posted January 28, Hi Binhex! Posted January 29, Just for clarity. At the end of the day im happy regardless. Thanks for the response. Bjonness Posted January 29, Hi I recently installed Delugevpn but I've been having trouble setting it up. To my knowledge it should say "privoxy process listening to port " at the bottom but it doesn't and I can't access the webui. I'm pretty new to docker and vpns in general so I apologize if the fix is really obvious.
I've looked around and I can't work out what the issue is so any help would be appreciated. I'm on arch-linux by the way. Here's the logs when I start it. I have the same issue. I can ping the container, but nothing on port My container will not start up if I have the VPN enabled, the problem started a week ago.
I am using nordVPN nothing has changed in the past 6 months but all of a sudden it isn't working. What can I do to get this working again?
I have also been having some issues. It's running again for me now but a couple of weeks ago I could only get it to run with the VPN off or oddly with debug logging enabled?! I believe I have finally deciphered how to make this work. However, I cannot access the web gui directly from Unraid's docker menu. If I visit the IP:Port directly in a web browser, it works.
However, the containers seem to communicate fine. Sonarr tests fine when I run the "Test" button for the download clients. I'm still working through getting the Indexers working as well as they don't respond at all from Sonarr, but that's another issue I suspect. Is it intended behavior for the "WebUI" option to disappear from UnRAID's docker menu for any containers directly passed to the binhex-delugevpn network?
Ok no problem. I was just pulling my hair out this past week trying to see why it wasn't working. Totally fine with the bookmark method, that's what I was thinking I had to do. Debug is enabled, credentials are recently changed, have no special characters, and have been verified to work in browser.
Both delugevpn and Unraid are up to date at the time of writing this. Any ideas here? So it was working on Unraid, as was sabnzbdvpn. I was attempting to get a second instance up and running testing with my login, but setting up for a friend , and after running into these same issues, I changed the password, and updated the containers on Unraid.
The only thing changed was the password. It's alphanumeric with no special characters, and 64 characters. Does it maybe need to be shortened a bit? Yep, turns out a 32 character password works just fine. Seems odd that there's a limit here, as the 64 character worked fine in browser. Do you know if there's a limit in your code, whether that's a limitation or artificial, at all, or is this just a weird bug? I am running binhex-nzbget thru binhex-delugevpn.
Up till yesterday no problem, then this error message in binhex-nzbget:. I downloaded a new conf file from PIA, no change. Before I start the Self signed certificate process, is there another way to fix this? I've been using DelugeVPN for a while and things were fine. I just noticed though that torrents do not download. They just sit there doing nothing. If I look under the Peers tab, I don't see anything listed.
So it seems like everything is working but downloading torrents. I'm really not sure where to look to troubleshoot that. If you're a PIA user then please follow this procedure
0コメント