[Support] binhex - DelugeVPN


Recommended Posts

Is it possible to allow two networks to access the containers? I have allowed my LAN network 192.168.1.0/24 but I also have to allow my remote access VPN network 10.1.0.0/24. Is this possible? 

 

Thanks for your containers, they work great. 

Link to comment
17 minutes ago, peeqi said:

Is it possible to allow two networks to access the containers? I have allowed my LAN network 192.168.1.0/24 but I also have to allow my remote access VPN network 10.1.0.0/24. Is this possible? 

 

Thanks for your containers, they work great. 

 

yes, a comma separated list will do it, e.g. 

LAN_NETWORK=92.168.1.0/24,10.1.0.0/24
  • Upvote 1
Link to comment

I just upgraded to the latest version of the docker and the webui doesn't start, I made no changes other than the update.  I'm using PIA.  Seems to get into a loop of restarting and terminating OpenVPN.  Please let me know if you need more of the log to help me figure out what's going on.

 

Thanks!

 

2017-06-23 13:40:48,397 DEBG 'start-script' stdout output:
--------------------

2017-06-23 13:40:48,398 DEBG 'start-script' stdout output:
[debug] OpenVPN command line '/usr/bin/openvpn --cd /config/openvpn --config /config/openvpn/openvpn.ovpn --daemon --dev tun0 --remote us-midwest.privateinternetaccess.com 1198 --proto udp --reneg-sec 0 --mute-replay-warnings --auth-nocache --keepalive 10 60 --setenv VPN_PROV pia --script-security 2 --up /root/openvpnup.sh --up-delay --up-restart --writepid /root/openvpn.pid --auth-user-pass credentials.conf --disable-occ --remap-usr1 SIGHUP --auth-user-pass credentials.conf --log-append /config/supervisord.log'

2017-06-23 13:40:48,398 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2017-06-23 13:40:48,470 DEBG 'start-script' stdout output:
[info] OpenVPN started

2017-06-23 13:40:48,470 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

2017-06-23 13:40:57,209 DEBG 'deluge-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.71.10.6'

2017-06-23 13:40:57,213 DEBG 'start-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.71.10.6'

2017-06-23 13:40:57,238 DEBG 'deluge-script' stdout output:
[info] Deluge not running

2017-06-23 13:40:57,238 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.71.10.6 different, marking for reconfigure
[debug] Waiting for file '/home/nobody/vpn_incoming_port.txt' to be generated (contains PIA API generated incoming port number)...

2017-06-23 13:43:27,255 DEBG 'start-script' stdout output:
[warn] OpenVPN process terminated, restarting OpenVPN...

2017-06-23 13:43:27,259 DEBG 'start-script' stdout output:
[info] OpenVPN restarted

2017-06-23 13:45:57,282 DEBG 'start-script' stdout output:
[warn] OpenVPN process terminated, restarting OpenVPN...

2017-06-23 13:45:57,291 DEBG 'start-script' stdout output:
[info] OpenVPN restarted

2017-06-23 13:48:27,319 DEBG 'start-script' stdout output:
[warn] OpenVPN process terminated, restarting OpenVPN...

2017-06-23 13:48:27,329 DEBG 'start-script' stdout output:
[info] OpenVPN restarted

2017-06-23 13:50:57,355 DEBG 'start-script' stdout output:
[warn] OpenVPN process terminated, restarting OpenVPN...

2017-06-23 13:50:57,365 DEBG 'start-script' stdout output:
[info] OpenVPN restarted

2017-06-23 13:50:57,355 DEBG 'start-script' stdout output:
[warn] OpenVPN process terminated, restarting OpenVPN...

2017-06-23 13:50:57,365 DEBG 'start-script' stdout output:
[info] OpenVPN restarted

 

Link to comment

Hi ! I have an issue on Debian 9 :  

 

# modprobe iptable_mangle
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.33-mod-std-ipv6-64/modules.dep.bin'
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.9.33-mod-std-ipv6-64

I saw the notice about Synology, unRaid and Ubuntu user, but I can't find a way to fix it for Debian 9. Could someone please help me ?

 

Thanks !

Link to comment
I just upgraded to the latest version of the docker and the webui doesn't start, I made no changes other than the update.  I'm using PIA.  Seems to get into a loop of restarting and terminating OpenVPN.  Please let me know if you need more of the log to help me figure out what's going on.

 

Thanks!

 

2017-06-23 13:40:48,397 DEBG 'start-script' stdout output:--------------------2017-06-23 13:40:48,398 DEBG 'start-script' stdout output:[debug] OpenVPN command line '/usr/bin/openvpn --cd /config/openvpn --config /config/openvpn/openvpn.ovpn --daemon --dev tun0 --remote us-midwest.privateinternetaccess.com 1198 --proto udp --reneg-sec 0 --mute-replay-warnings --auth-nocache --keepalive 10 60 --setenv VPN_PROV pia --script-security 2 --up /root/openvpnup.sh --up-delay --up-restart --writepid /root/openvpn.pid --auth-user-pass credentials.conf --disable-occ --remap-usr1 SIGHUP --auth-user-pass credentials.conf --log-append /config/supervisord.log'2017-06-23 13:40:48,398 DEBG 'start-script' stdout output:[info] Starting OpenVPN...2017-06-23 13:40:48,470 DEBG 'start-script' stdout output:[info] OpenVPN started2017-06-23 13:40:48,470 DEBG 'start-script' stdout output:[debug] Waiting for valid IP address from tunnel...2017-06-23 13:40:57,209 DEBG 'deluge-script' stdout output:[debug] Valid IP address from tunnel acquired '10.71.10.6'2017-06-23 13:40:57,213 DEBG 'start-script' stdout output:[debug] Valid IP address from tunnel acquired '10.71.10.6'2017-06-23 13:40:57,238 DEBG 'deluge-script' stdout output:[info] Deluge not running2017-06-23 13:40:57,238 DEBG 'deluge-script' stdout output:[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.71.10.6 different, marking for reconfigure[debug] Waiting for file '/home/nobody/vpn_incoming_port.txt' to be generated (contains PIA API generated incoming port number)...2017-06-23 13:43:27,255 DEBG 'start-script' stdout output:[warn] OpenVPN process terminated, restarting OpenVPN...2017-06-23 13:43:27,259 DEBG 'start-script' stdout output:[info] OpenVPN restarted2017-06-23 13:45:57,282 DEBG 'start-script' stdout output:[warn] OpenVPN process terminated, restarting OpenVPN...2017-06-23 13:45:57,291 DEBG 'start-script' stdout output:[info] OpenVPN restarted2017-06-23 13:48:27,319 DEBG 'start-script' stdout output:[warn] OpenVPN process terminated, restarting OpenVPN...2017-06-23 13:48:27,329 DEBG 'start-script' stdout output:[info] OpenVPN restarted2017-06-23 13:50:57,355 DEBG 'start-script' stdout output:[warn] OpenVPN process terminated, restarting OpenVPN...2017-06-23 13:50:57,365 DEBG 'start-script' stdout output:[info] OpenVPN restarted2017-06-23 13:50:57,355 DEBG 'start-script' stdout output:[warn] OpenVPN process terminated, restarting OpenVPN...2017-06-23 13:50:57,365 DEBG 'start-script' stdout output:[info] OpenVPN restarted

 

 

 

The endpoint you are using doesn't allow port forwarding, try switching to an endpoint that does support it, your speeds will significantly improve btw

 

Edit - if it really is a problem then I can add logic to allow connection to endpoints that don't allow port forwarding, but I would rather not do that as it's yet another environment var

 

Sent from my SM-G935F using Tapatalk

 

 

 

  • Upvote 1
Link to comment
Thanks, your quick response and a search for PIA port forwarding endpoints got me up and running again.  Switched my endpoint for SabnzbdVpn too while I was at it.

No probs, like I mentioned for torrents your speeds will be a LOT faster now you have an incoming port working

Sent from my SM-G935F using Tapatalk

Link to comment

Updated my docker and now the Webgui not loading for me, I can use privoxy fine. How do you change the PIA port forwarding? Maybe I have the same issue.

 

I've even deleted everything from my /appdata/binhex-delugevpn and re-installed docker still the same issue

Edited by shadowless82
Link to comment
2 minutes ago, shadowless82 said:

Updated my docker and now the Webgui not loading for me, I can use privoxy fine. How do you change the PIA port forwarding? Maybe I have the same issue.

 

Use an endpoint that supports it:  https://helpdesk.privateinternetaccess.com/hc/en-us/articles/219460187-How-do-I-enable-port-forwarding-on-my-VPN-

 

Here's a list of their networks: https://www.privateinternetaccess.com/pages/network/#

 

Edited by jjdunkel
  • Upvote 1
Link to comment
35 minutes ago, shadowless82 said:

Updated my docker and now the Webgui not loading for me, I can use privoxy fine. How do you change the PIA port forwarding? Maybe I have the same issue.

 

I've even deleted everything from my /appdata/binhex-delugevpn and re-installed docker still the same issue

 

Noticed the same thing here as well.  GUI won't start up anymore after the update.  Had to change to one in Canada.  None in the US support port forwarding it seems.

2017-06-23 16:30:53,432 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2017-06-23 16:30:53,441 DEBG 'start-script' stdout output:
[info] OpenVPN started

2017-06-23 16:30:54,816 DEBG 'deluge-script' stdout output:
[info] Deluge not running
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.15.10.6 different, marking for reconfigure

2017-06-23 16:33:24,857 DEBG 'start-script' stdout output:
[warn] OpenVPN process terminated, restarting OpenVPN...

2017-06-23 16:33:24,861 DEBG 'start-script' stdout output:
[info] OpenVPN restarted

2017-06-23 16:35:54,878 DEBG 'start-script' stdout output:
[warn] OpenVPN process terminated, restarting OpenVPN...

2017-06-23 16:35:54,882 DEBG 'start-script' stdout output:
[info] OpenVPN restarted

2017-06-23 16:38:24,897 DEBG 'start-script' stdout output:
[warn] OpenVPN process terminated, restarting OpenVPN...

2017-06-23 16:38:24,901 DEBG 'start-script' stdout output:
[info] OpenVPN restarted

 

Edited by digiblur
Link to comment

Hello, 

 

I was running regular deluge on my desktop, but have I have transitioned to this docker container. I would like to move all of .torrent files over but I am not sure how to do it. The webUI does not allow for adding multiple torrent files at once and since I have 300 of them, I don't want to have to add them one at a time. 

 

I tried connecting the desktop client to the docker container using the connection manager on the desktop so that I could use the desktop UI to drag all of the files at once, however I cannot establish a connection. Any ideas how I can move all of my .torrent files over easily?

Link to comment
17 hours ago, jjdunkel said:

Experienced the same thing this morning after the update. Changed gateway to CA Toronto (ca-toronto.privateinternetaccess.com) and all is well.

Link to comment

so why is it that we have to use the port-forwarding supported locations now? I really know nothing about this, just followed the advice on this thread to get it working again (changing to TO-Canada).

 

Does this mean we won't be able to use US endpoints on delugevpn again?

Link to comment
3 hours ago, theGrok said:

Hello, 

 

I was running regular deluge on my desktop, but have I have transitioned to this docker container. I would like to move all of .torrent files over but I am not sure how to do it. The webUI does not allow for adding multiple torrent files at once and since I have 300 of them, I don't want to have to add them one at a time. 

 

I tried connecting the desktop client to the docker container using the connection manager on the desktop so that I could use the desktop UI to drag all of the files at once, however I cannot establish a connection. Any ideas how I can move all of my .torrent files over easily?

 

 

I was actually able to edit the auth file in appdata and can now make a remote connection. I then used the auto add plugin. Problem solved.

Link to comment
so why is it that we have to use the port-forwarding supported locations now? I really know nothing about this, just followed the advice on this thread to get it working again (changing to TO-Canada).
 
Does this mean we won't be able to use US endpoints on delugevpn again?

So using torrent clients without an incoming port is a really bad idea, not only does it give you cripplingly low download speeds, but also causes problems for the swarm.

Can I ask why you specifically want to connect to a us endpoint?

Sent from my SM-G935F using Tapatalk

  • Upvote 1
Link to comment
3 hours ago, binhex said:


So using torrent clients without an incoming port is a really bad idea, not only does it give you cripplingly low download speeds, but also causes problems for the swarm.

Can I ask why you specifically want to connect to a us endpoint?

Sent from my SM-G935F using Tapatalk
 

Thanks for the input, i really don't know much about how it all works.  

 

Since I'm on the US east coast, I just assumed speeds would be better with a US East endpoint.  I haven't really noticed better speeds as of yet, but that could be the torrents themselves.  Is there a specific endpoint you'd recommend over the others? Currently on the netherlands one.  Also if this is the better route to go through, I will take your word on it. You clearly know what you're doing, and I would be lost without your binhex dockers.

 

Edit:

 

Also, what do you mean problems for the swarm? I'm just curious.

 

I've only changed the endpoint to NL, are there any other changes I need to make to ensure this works as intended?

Edited by pro9c3
Link to comment
12 hours ago, pro9c3 said:

so why is it that we have to use the port-forwarding supported locations now? I really know nothing about this, just followed the advice on this thread to get it working again (changing to TO-Canada).

 

Does this mean we won't be able to use US endpoints on delugevpn again?

 

This change also broke my Deluge-VPN, which I rarely use and only discovered today.

 

For any one using PIA, you'll have to set the server to one of these locations now:

  • CA Toronto
  • CA Montreal
  • Netherlands
  • Switzerland
  • Sweden
  • France
  • Germany
  • Romania
  • Israel
Link to comment

I ran into the same issue today. I can no longer use US-based locations in PIA since updating my client? I was originally using US-EAST and tried changing to Chicago, neither of which worked. Supervisor.conf said the following:

 

2017-06-25 18:21:16,659 DEBG 'rtorrent-script' stdout output:
[warn] Port forwarding is already activated on this connection, has expired, or you are NOT connected to a PIA region that supports port forwarding

 

And generally kept restarting:

 

2017-06-25 18:58:57,457 DEBG 'start-script' stdout output:
[info] OpenVPN restarted

 

I ended up changing to nl.privateinternetaccess.com to get it working again but would prefer to use a US-based location (I am in Canada).

Link to comment
12 minutes ago, noobraider said:

I ended up changing to nl.privateinternetaccess.com to get it working again but would prefer to use a US-based location (I am in Canada).

Why are you using a VPN?

 

Typically people use a VPN to move the apparent endpoint of the data stream to a different jurisdiction for various reasons. US based endpoints are not torrent friendly jurisdiction wise, and for whatever reason PIA does not support port forwarding for those endpoints.

 

If you need a US based VPN endpoint that supports torrents, I suggest contacting support for various other VPN providers to see if you can find one that does. I don't know of any.

Link to comment
On 2017-6-24 at 9:19 PM, pro9c3 said:

Is there a specific endpoint you'd recommend over the others?

 

not really, i tend to go with the endpoints that have the most bandwidth (and of course port forwarding), the netherlands is one of the higher speed endpoints, but the choice is yours.

 

On 2017-6-24 at 9:19 PM, pro9c3 said:

Also, what do you mean problems for the swarm? I'm just curious.

 

connecting to a torrent swarm (that is a collection of seeds and leechers) without a incoming connection will put a strain on the swarm population, having to switch from the native tit-for-tat system for certain peers is not good and is normally frowned upon.

 

On 2017-6-24 at 9:19 PM, pro9c3 said:

I've only changed the endpoint to NL, are there any other changes I need to make to ensure this works as intended?

 

no other changes required, the assignment of the incoming port is done for you.

  • Upvote 1
Link to comment
8 hours ago, noobraider said:

I ended up changing to nl.privateinternetaccess.com to get it working again but would prefer to use a US-based location (I am in Canada).

 

why do you prefer a US based location?, if the answer is dl/ul speed then ironically this is the one thing you wont get as no US based endpoint supports port forwarding, switch over to another endpoint that does support port forwarding and be happy :-).

Link to comment

Join the conversation

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.