Jump to content
binhex

[Support] binhex - DelugeVPN

4108 posts in this topic Last Reply

Recommended Posts

23 hours ago, binhex said:

sorry im out of ideas then, all i can tell you is the container looks to be starting fine, so its something on your network and/or hosts that is the cause.

OK  ..  I believe I have figured it out.  My linux machine was set to dhcp and somehow it assigned the network ip out of the ip range of the unraid docker.  So ...  I assigned a static ip on the linux machine and presto...  i have UI again ..

I suppose if anyone else has exhausted all other avenues .. check your machines ip address.

lesson learned.

Thanks binhex for taking the time to troubleshoot

Share this post


Link to post
44 minutes ago, Gog said:

Hi there, welcome to the forums

iptables are configured to only let traffic out through the VPN IP and the local network (the LAN_NETWORK variable)

Moreover, at init if the VPN is not established, Deluge will not go up

Sooo if i get u right its already configured? I dont need to bother?

Ty for the welcome 😃

Share this post


Link to post
17 minutes ago, gambler3k said:

Sooo if i get u right its already configured? I dont need to bother?

 

Correct.  Somebody else bothered ;)

  • Like 1

Share this post


Link to post

I just wanted to make sure, I just installed this in a new machine, and I just installed the binhex-delugevpn.

I checked the first page, but I wanted to make sure I'm doing it correctly. I just put my username and password for PIA when installing, it seems that I didn't need to change anything else. I downloaded the PIA ovpn zip and unzipped, I picked CA Toronto.ovpn and I replaced the one that was in root/mnt/user/appdata/binhex-delugevpn/openvpn

the file already in there was about 300B and the new is 3.1KB. just wanted to make sure that is all that is needed to ensure it will be safe.

 

much appreciated for the help.

Share this post


Link to post
-e VPN_ENABLED=yes 

Needs to be set, but I'm assuming you probably did that.  

Share this post


Link to post
1 hour ago, THF13 said:

-e VPN_ENABLED=yes 

Needs to be set, but I'm assuming you probably did that.  

Actually I did not, as it was already selected to yes, but I did make sure it was to yes.

But everything sounds good then? Is there a good way to check if it's working well or any leaks? besides putting the wrong login info to PIA

Share this post


Link to post
Actually I did not, as it was already selected to yes, but I did make sure it was to yes.
But everything sounds good then? Is there a good way to check if it's working well or any leaks? besides putting the wrong login info to PIA
sounds good to me in short if you have VPN enabled set to yes and you can access the web UI then you are guaranteed the VPN is established and running

Sent from my EML-L29 using Tapatalk

Share this post


Link to post

just now Deluge-VPN won't start and a reinstall gets this message.

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --cpuset-cpus='2,4,3,5' --privileged=true -e TZ="America/Phoenix" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='******' -e 'VPN_PASS'='*********' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='10.10.10.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/':'/data':'rw' -v '/mnt/disks/KEVINPC_g/':'/KPCG':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 
7287b28e9c3c2b095eac00ca44ca684c0614f4b5d27846d8c9efc2a7710f5360
/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-delugevpn (3481502e83b48702f7d3e7eccf79040bbf5a169cc598454c1eac98ba84cbd6ba): Bind for 0.0.0.0:58946 failed: port is already allocated.

The command failed.

I can't get you a log because it won't even start and gives me an execution error. Any assistance here would be much appreciated. I've had it up and running for literally months and months so it was stable and all I did was restart the server.

Share this post


Link to post

Your post shows that the startup failed because port 58946 is already in use. Is another docker using the same port?

Share this post


Link to post

I double checked and no, no other docker is using that port. However, it is listed twice in the deluge-VPN settings when I go to edit the container. Are both of these necessary? Should I try deleting one?

 

image.thumb.png.0f5dca7b4590ec8234950d3a8691a28d.png

Share this post


Link to post

Somehow, it fixed itself... I had just rebooted the server but this time I went and just turned the docker engine off and back on while the server was still running and automagically it just started working. Literally no clue but I guess I'm happy now. Strange! 🤣

Share this post


Link to post

@binhex Any chance of getting a Deluge-2.0 VPN docker? The beta has been out for a year now and is quite stable from my (albeit limited) testing. The biggest current issues before a final 2.0 release seem to be around the Windows version not playing well with Python 3 (from the bug-tracker).

Share this post


Link to post
On 1/27/2017 at 3:58 AM, binhex said:

 

ok so when using DelugeVPN you can set which name servers you wish to use, by default this is set to use Google DNS, you can define which name servers you want my changing the value for key NAME_SERVERS. So to answer your question, no there is no built in "dns leak protection switch" but you can control which name servers you want, the PIA name servers are as follows:-

 

209.222.18.222

209.222.18.218

 

So you could use these for name resolution if you concerned. Just to add a bit more info to this, the risks of DNS leakage are minimised for this docker container, as we aren't routing all of your LAN traffic through this, it is used to purely route torrent traffic and possibly index site hits via privoxy, so information that could be gathered from your name server lookups wouldn't  be very specific to you as a individual, unlike when using the traditional Windows PIA client where ALL traffic is routed through for the host once the VPN is up, including websites you surf such as social sites etc, although even this is small/no risk as PIA do not log anything.

Could someone please tell me where I can find the value for the key "NAME_SERVERS"?  I checked all the files in appdata/binhex-delugevpn and could not find them.  Do I need to somehow create a new "key" on the "Update Container" docker setup page?  If so, could someone please walk me through doing this?  I would like to use the PIA name servers.

 

Thank you and kind regards,

craigr

Share this post


Link to post
54 minutes ago, craigr said:

Could someone please tell me where I can find the value for the key "NAME_SERVERS"? 

Just change it in the docker settings. Docker tab>select the docker>edit the key.

SafariScreenSnapz138.thumb.jpg.423d3a7a405a8aaf19fd9b5dedae044c.jpg

  • Like 1

Share this post


Link to post
18 hours ago, death.hilarious said:

@binhex Any chance of getting a Deluge-2.0 VPN docker? The beta has been out for a year now and is quite stable from my (albeit limited) testing. The biggest current issues before a final 2.0 release seem to be around the Windows version not playing well with Python 3 (from the bug-tracker).

i have a general rule of not targeting non releases unless there is no alternative, so i would prefer to wait for the official release of 2.0 before jumping over, stability is everything in my opinion and whilst i appreciate your experience of using it, there are a lot of users here who have a uncanny way of finding bugs :-).

 

what pro's are there over v1 btw, speed?, ui?

Share this post


Link to post
4 hours ago, binhex said:

i have a general rule of not targeting non releases unless there is no alternative, so i would prefer to wait for the official release of 2.0 before jumping over, stability is everything in my opinion and whilst i appreciate your experience of using it, there are a lot of users here who have a uncanny way of finding bugs :-).

 

what pro's are there over v1 btw, speed?, ui?

The core has been completely rewritten to maintain compatibility with the latest libtorrent versions. The biggest difference is in terms of performance--the new Deluge v.2.0 is a lot more resource efficient especially when seeding a large number of torrents. But there are plenty of cool new features too. For example, Deluge v.2.0 adds multiuser support in the WebUI, so you can have different login usernames and passwords and each user will only see their own torrents.

 

The roadmap suggests that cas was aiming for a Dec. 31 release of 2.0.0, but I'm not so sure he's going to make it because of the Windows issues. Nevertheless, the project is really close to a release and it's probably a good time to start thinking about a docker for it. Plus the Christmas holidays might make a good time for people to play with an experimental docker to find bugs ;).

 

Share this post


Link to post
18 hours ago, craigr said:

....to answer your question, no there is no built in "dns leak protection switch"....

btw just to be clear to anybody here, this is no longer the case, dns is 100% used over the vpn only, the only time its not is for the initial lookup of the endpoint you are connecting to (which is then cached in hosts file). If the vpn goes down name queries do not go over the lan (iptables set not to allow port 53), once the vpn tunnel is re-established (by looking up the endpoint using hosts file) name server queries are then resumed over the vpn tunnel, zero leakage.

Edited by binhex
  • Like 2
  • Upvote 1

Share this post


Link to post
19 hours ago, wgstarks said:

Just change it in the docker settings. Docker tab>select the docker>edit the key.

SafariScreenSnapz138.thumb.jpg.423d3a7a405a8aaf19fd9b5dedae044c.jpg

Don't ask me how I didn't see that.

 

Thanks,

craigr

Share this post


Link to post
7 minutes ago, craigr said:

Don't ask me how I didn't see that.

You probably have a blind spot right in front of your face like me.😁

Share this post


Link to post

So I have suddenly started having an issue... I did update the DD-WRT firmware on my router a few days ago, but I don't think that's it.  I tried resetting the router to defaults today as well.

 

When I launch the docker it opens fine and I start seeding right away.  Then, it seems that deluge keeps losing the connection to my VPN so deluge attempts to reconnect and does.  The PIA connection keeps getting lost and reconnected.  I tried changing the  PIA gateway from Montreal (which had been working fine) to Toronto and I am getting the same results.  Even while I am downloading the PIA connection will get lost, the download will stop, and then reconnect.  I can't understand why this has started seemingly out of the blue.  Attached is my log (supervisord.log).  I can get a longer log if that will help anyone, but I think it shows at least one of the lost connections and then a reconnection.

 

Thanks for any help!  I am so frustrated.

craigr

Share this post


Link to post

There was also an update to Deluge the other day as well... That may have been when the trouble started.

 

craigr

Share this post


Link to post
3 hours ago, craigr said:

So I have suddenly started having an issue... I did update the DD-WRT firmware on my router a few days ago, but I don't think that's it.  I tried resetting the router to defaults today as well.

 

When I launch the docker it opens fine and I start seeding right away.  Then, it seems that deluge keeps losing the connection to my VPN so deluge attempts to reconnect and does.  The PIA connection keeps getting lost and reconnected.  I tried changing the  PIA gateway from Montreal (which had been working fine) to Toronto and I am getting the same results.  Even while I am downloading the PIA connection will get lost, the download will stop, and then reconnect.  I can't understand why this has started seemingly out of the blue.  Attached is my log (supervisord.log).  I can get a longer log if that will help anyone, but I think it shows at least one of the lost connections and then a reconnection.

 

Thanks for any help!  I am so frustrated.

craigr

I'm no expert but it sounds like a local networking issue. Check things like cables and MTU settings. Double check your ddwrt settings to make sure it's not doing anything it's not supposed to be doing (particularly things like QoS or other flow controls and anything that involves packet inspection).

 

Make sure your not doing things like using Wi-Fi for your torrent box or running a VPN client on your router in addition to the VPN client running on the delugeVPN box.

 

Maybe try reverting back to the older ddwrt firmware.

Share this post


Link to post

@binhex Thank you for an awesome container! I've been running this on my unraid server since day one. This may be semi unrelated, but I'm trying to deploy the container on a standard centos 7 install to demonstrate docker to a class. Rhel 7 and Ubuntu 18 label embedded NICs as eno1, eno2, etc, and it appears that the iptables.sh has eth0 hardcoded. The result is that the container deploys, and starts, but the iptables rules don't function. Any advice? Thanks again.

Share this post


Link to post
23 hours ago, death.hilarious said:

I'm no expert but it sounds like a local networking issue. Check things like cables and MTU settings. Double check your ddwrt settings to make sure it's not doing anything it's not supposed to be doing (particularly things like QoS or other flow controls and anything that involves packet inspection).

 

Make sure your not doing things like using Wi-Fi for your torrent box or running a VPN client on your router in addition to the VPN client running on the delugeVPN box.

 

Maybe try reverting back to the older ddwrt firmware.

Something is broken in the newest DD-WRT firmware for my R7000 because the command to renew the DHCP lease from the U-Verse junk hardware no longer was allowing the lease to renew without resetting the WAN connection.  So every 10 minutes my DHCP lease was expiring and forcing a new connection.

 

I really wish ATT would sell just a damn modem and not an entire access point with modem and wifi router... especially one that can't totally be bridged and also requires that the DHCP lease expires every 10 minutes when your real router is in DMZ+... sigh, it's always something.

 

Anyway, old firmware on my DD-WRT router solved the problem.

 

Blah blah blah...

 

Thanks for having me look back that way again when I thought it was already covered ;-)

 

craigr

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now