Jump to content
binhex

[Support] binhex - DelugeVPN

3923 posts in this topic Last Reply

Recommended Posts

ive been stung by this in the past by other users, thus the ns lookup when the debug flag is set, you live and learn :-)

Share this post


Link to post

Thanks Binhex - BT were in fact hijacking the DNS.

 

I set the DNS in both unRaid and at the router to use Google and it worked a treat :)  

 

One thing of note for any other users who have a similar issue; if you use a BT Hub 4 (like I have), then you can't override the DNS settings. You will need to either use a dynamic DNS site or use another router which will allow you to configure the DNS. You will also need to turn off all the BT Parental controls on your BT account to get this working. If you have a BT Hub 5, i believe you can override the DNS......

 

Luckily, I have a spare Netgear router so all working now.

 

Many thanks for the speedy responses  :)

Share this post


Link to post
6 hours ago, wirenut said:

 


You need to set VPN_REMOTE with a server that supports port forwarding. The one you have set from Texas does not. None of the US server do. Check the list on the PIA website.

Sent from my HTC One M9 using Tapatalk
 

 

 
 

Thanks!!  Using the VPN_REMOTE that came in the original template (nl.privateinternetaccess.com) fixed the issue!

Share this post


Link to post

Anyone know how I can solve for this:

 

 

/usr/bin/nginx: error while loading shared libraries: libdl.so.2: cannot open shared object file: Permission denied

 

If I disable apparmor it does work, so I guess I need to edit a profile maybe?

 

Any help appreciated 

Share this post


Link to post
21 hours ago, Hansel said:

 

 

@BakedPizza That's great, thanks a lot for that. My only issue now is that apparmor seems to be blocking something to do with nginx.

 

/usr/bin/nginx: error while loading shared libraries: libdl.so.2: cannot open shared object file: Permission denied

 

I did disable apparmor temporarily and it worked, so If I can fix that I'm good to go!

Where do you see this? Inside the container or on your Synology NAS? I'm not seeing any AppArmor issues...

Share this post


Link to post
Just now, BakedPizza said:

Where do you see this? Inside the container or on your Synology NAS? I'm not seeing any AppArmor issues...

 

Hmm.  It just shows up in the Log of the container (and the supervisor.log file).  Everything will "boot" up, establish a VPN connection etc, then right at the end it'll give this error and crash out (I assume).

Share this post


Link to post

Here's the revelant log section:

 

2017-03-10 00:01:05,040 DEBG 'rtorrent-script' stdout output:
[info] Waiting for rTorrent and nginx to start...

2017-03-10 00:01:05,546 DEBG 'rutorrent-script' stdout output:
[info] rtorrent started, setting up rutorrent...

2017-03-10 00:01:05,547 DEBG 'rutorrent-script' stdout output:
[info] Setting PHP timezone to Australia/Melbourne...

2017-03-10 00:01:05,832 DEBG 'rutorrent-script' stdout output:
[info] nginx cert files already exists, skipping copy

2017-03-10 00:01:05,866 DEBG 'rutorrent-script' stdout output:
[info] nginx security file already exists, skipping copy

2017-03-10 00:01:05,895 DEBG 'rutorrent-script' stdout output:
[info] nginx config file already exists, skipping copy

2017-03-10 00:01:05,999 DEBG 'rutorrent-script' stdout output:
[info] rutorrent conf folder already exists, skipping copy

2017-03-10 00:01:06,045 DEBG 'rutorrent-script' stdout output:
[info] rutorrent share folder already exists, skipping copy

2017-03-10 00:01:06,134 DEBG 'rutorrent-script' stdout output:
[info] copying rutorrent plugins to container...

2017-03-10 00:01:17,032 DEBG 'rutorrent-script' stdout output:
[info] starting php-fpm...

2017-03-10 00:01:18,402 DEBG 'rutorrent-script' stdout output:
[info] starting nginx...

2017-03-10 00:01:18,546 DEBG 'rutorrent-script' stderr output:
/usr/bin/nginx: error while loading shared libraries: libdl.so.2: cannot open shared object file: Permission denied

2017-03-10 00:01:18,547 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 140684505449536for <Subprocess at 140684505606912 with name rutorrent-script in state RUNNING> (stderr)>
2017-03-10 00:01:18,548 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 140684505449608for <Subprocess at 140684505606912 with name rutorrent-script in state RUNNING> (stdout)>
2017-03-10 00:01:18,549 INFO exited: rutorrent-script (exit status 127; not expected)
2017-03-10 00:01:18,550 DEBG received SIGCLD indicating a child quit
2017-03-10 00:05:00,469 WARN received SIGTERM indicating exit request
2017-03-10 00:05:00,470 INFO waiting for start-script, rtorrent-script to die
2017-03-10 00:05:02,477 DEBG killing rtorrent-script (pid 116) with signal SIGTERM
2017-03-10 00:05:02,478 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 140684505451048for <Subprocess at 140684505606408 with name rtorrent-script in state STOPPING> (stdout)>
2017-03-10 00:05:02,479 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 140684505450976for <Subprocess at 140684505606408 with name rtorrent-script in state STOPPING> (stderr)>
2017-03-10 00:05:02,479 INFO stopped: rtorrent-script (terminated by SIGTERM)
2017-03-10 00:05:02,480 DEBG received SIGCLD indicating a child quit
2017-03-10 00:05:02,481 DEBG killing start-script (pid 115) with signal SIGTERM
2017-03-10 00:05:02,482 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 140684505452488for <Subprocess at 140684505606624 with name start-script in state STOPPING> (stderr)>
2017-03-10 00:05:02,483 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 140684505450688for <Subprocess at 140684505606624 with name start-script in state STOPPING> (stdout)>
2017-03-10 00:05:02,483 INFO stopped: start-script (terminated by SIGTERM)
2017-03-10 00:05:02,484 DEBG received SIGCLD indicating a child quit

Share this post


Link to post

@Hansel I think you are posting this in the wrong topic, as it seems you are using rtorrent and not deluge. I've got no experience with the rtorrent container. You should post your issues here:

Or try switching to this container (arch-delugevpn).

Edited by BakedPizza

Share this post


Link to post
Just now, BakedPizza said:

@Hansel I think you are posting this in the wrong topic, as it seems you are using rtorrent and not deluge. I've got no experience with the rtorrent container. You should post your issues here:

 

 

Ah crap.  I am, but I use both so I just follow the support and forget where I am :D

 

Let me see if Deluge works, that'll narrow it down a bit.

Share this post


Link to post

Just for reference, Deluge appears to be fine so it's rtorrent specific.  I'll post over there.

Share this post


Link to post

Hi, I'm getting an error message when trying to send updates via SickRage, regarding No JSON object could be decoded. DelugeVPN is showing this error in supervisors.log

2017-03-11 08:55:52,901 DEBG 'deluge-web-script' stderr output:
[ERROR   ] 08:55:52 json_api:285 Invalid JSON request content-type: None
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 307, in render
    d = self._on_json_request(request)
  File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 267, in _on_json_request
    raise JSONException(message)
JSONException: Invalid JSON request content-type: None

As a relative newbie with unRAID, I'm uncertain how to troubleshoot further. I've recently updated both dockers to their latest and I believe that's likely where this conflict arose.

Share this post


Link to post
13 minutes ago, KungFuCowboy said:

Hi, I'm getting an error message when trying to send updates via SickRage, regarding No JSON object could be decoded. DelugeVPN is showing this error in supervisors.log


2017-03-11 08:55:52,901 DEBG 'deluge-web-script' stderr output:
[ERROR   ] 08:55:52 json_api:285 Invalid JSON request content-type: None
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 307, in render
    d = self._on_json_request(request)
  File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 267, in _on_json_request
    raise JSONException(message)
JSONException: Invalid JSON request content-type: None

As a relative newbie with unRAID, I'm uncertain how to troubleshoot further. I've recently updated both dockers to their latest and I believe that's likely where this conflict arose.

 

 

Look here.

Share this post


Link to post
51 minutes ago, CHBMB said:

 

 

Look here.

 

Thanks CHBMB. I looked in that directory, but I'm not finding the python2.7 folder. I actually don't see any python folder for that matter. Hmm. I'm logged in as the root user via SSH.

Share this post


Link to post
 
Thanks CHBMB. I looked in that directory, but I'm not finding the python2.7 folder. I actually don't see any python folder for that matter. Hmm. I'm logged in as the root user via SSH.

Which container are you logged in to? It's Sickrage that's the problem. I haven't used Sickage since I switched to Sonarr. The file that's the the problem is probably at /app/sickrage/sickrage/sickbeard/clients/deluged_client.py. You could just use the black hole method in sickrage and the label and autoadd plugins in deluge till it's fixed.

Share this post


Link to post

Hey gents, I'm wondering if I'm in the right place.

 

I've installed delugeVPN on my unraid server, and I can't get it to work.  When I go to the webui, all I'm getting is "Unable to connect".

Now I have set it up once w/o vpn capabilities, and it worked, so I'm guessing the problem is somewhere there in the vpn config.

 

I'm trying to use it with an openVPN server of our own that sits in the Amazon cloud.   The openVPN server works well with openVpnConnect from win7 desktop.

Again, this is pointing to a probable error in the configs.

 

Is there any place where a detailed description for each of the configs exist?  The 'help' next to each field in the delugeVPN config is rather frugal in information.

Or otherwise, how can one debug what's happening? 

 

I feel I'm going around in circles in the dark; it's very frustrating.

 

Please bear in mind I'm rather beginner with this whole thing.

Thanks for any  help.

Share this post


Link to post

Is it expected to see this over and over (could just be as I have debug on)?

 

Quote

2017-03-12 06:23:42,604 DEBG 'deluge-script' stdout output:

[debug] Waiting for valid IP address from tunnel...

 

2017-03-12 06:23:42,784 DEBG 'deluge-script' stdout output:

[debug] Valid IP address from tunnel acquired '10.9.10.6'

 

2017-03-12 06:23:45,517 DEBG 'deluge-script' stdout output:

[debug] External IP address from tunnel is '46.166.188.204'

 

2017-03-12 06:23:45,929 DEBG 'deluge-script' stdout output:

[debug] VPN incoming port is 23649

 

2017-03-12 06:23:45,931 DEBG 'deluge-script' stdout output:

[debug] VPN IP is 10.9.10.6

[debug] Deluge incoming port is 23649

[debug] Deluge IP is 10.9.10.6

 

2017-03-12 06:24:15,942 DEBG 'deluge-script' stdout output:

[debug] Waiting for valid IP address from tunnel...

 

2017-03-12 06:24:16,130 DEBG 'deluge-script' stdout output:

[debug] Valid IP address from tunnel acquired '10.9.10.6'

 

2017-03-12 06:24:24,442 DEBG 'deluge-script' stdout output:

[debug] External IP address from tunnel is '46.166.188.204'

 

2017-03-12 06:24:24,817 DEBG 'deluge-script' stdout output:

[debug] VPN incoming port is 23649

[debug] VPN IP is 10.9.10.6

[debug] Deluge incoming port is 23649

 

2017-03-12 06:24:24,818 DEBG 'deluge-script' stdout output:

[debug] Deluge IP is 10.9.10.6

 

2017-03-12 06:24:54,823 DEBG 'deluge-script' stdout output:

[debug] Waiting for valid IP address from tunnel...

 

2017-03-12 06:24:55,010 DEBG 'deluge-script' stdout output:

[debug] Valid IP address from tunnel acquired '10.9.10.6'

 

2017-03-12 06:24:57,321 DEBG 'deluge-script' stdout output:

[debug] External IP address from tunnel is '46.166.188.204'

 

2017-03-12 06:24:57,695 DEBG 'deluge-script' stdout output:

[debug] VPN incoming port is 23649

[debug] VPN IP is 10.9.10.6

[debug] Deluge incoming port is 23649

 

2017-03-12 06:24:57,696 DEBG 'deluge-script' stdout output:

[debug] Deluge IP is 10.9.10.6

 

2017-03-12 06:25:27,699 DEBG 'deluge-script' stdout output:

[debug] Waiting for valid IP address from tunnel...

 

2017-03-12 06:25:27,879 DEBG 'deluge-script' stdout output:

[debug] Valid IP address from tunnel acquired '10.9.10.6'

 

2017-03-12 06:25:30,169 DEBG 'deluge-script' stdout output:

[debug] External IP address from tunnel is '46.166.188.204'

 

2017-03-12 06:25:30,538 DEBG 'deluge-script' stdout output:

[debug] VPN incoming port is 23649

[debug] VPN IP is 10.9.10.6

[debug] Deluge incoming port is 23649

 

2017-03-12 06:25:30,539 DEBG 'deluge-script' stdout output:

[debug] Deluge IP is 10.9.10.6

 

2017-03-12 06:26:00,545 DEBG 'deluge-script' stdout output:

[debug] Waiting for valid IP address from tunnel...

 

2017-03-12 06:26:00,755 DEBG 'deluge-script' stdout output:

[debug] Valid IP address from tunnel acquired '10.9.10.6'

 

2017-03-12 06:26:03,049 DEBG 'deluge-script' stdout output:

[debug] External IP address from tunnel is '46.166.188.204'

 

2017-03-12 06:26:03,440 DEBG 'deluge-script' stdout output:

[debug] VPN incoming port is 23649

[debug] VPN IP is 10.9.10.6

[debug] Deluge incoming port is 23649

 

2017-03-12 06:26:03,441 DEBG 'deluge-script' stdout output:

[debug] Deluge IP is 10.9.10.6

 

 

 

Edited by Hansel

Share this post


Link to post

@HanselI think so. Just turn it off if it's working fine.

/home/nobody/getvpnip.sh

# function to check ip adress is in valid format (used for local tunnel ip and external ip) 
[..]
if [[ "${DEBUG}" == "true" ]]; then                                                                           
        echo "[debug] Valid IP address from tunnel acquired '${current_vpn_ip}'"                              
fi   

@ysu Please post your supervisord log (remove any credentials in the log). Not sure if I'm able to help, but others might.

 

On 5-2-2016 at 11:53 AM, binhex said:

What i would like to do is to separate openvpn into its own container, have that running and then have another container running application X that you want to have tunnelled and simply link the two containers together, this has the really nice advantage that its only a single vpn tunnel, and means with a bit of scripting for each container you could pick and choose which apps you want tunnelled. OK so here is the kicker, unraid webui doesnt support this configuration, so there is no way of linking the containers together other than getting down and dirty with the CLI, so until thats possible we are where we are right now, maybe if i get time i will put in a feature request for this.

Ever found the time to do a request? Synology has a feature to link containers, so I'm very interested in a capability like this.

 

Share this post


Link to post
Is it expected to see this over and over (could just be as I have debug on)?
 
2017-03-12 06:23:42,604 DEBG 'deluge-script' stdout output:
[debug] Waiting for valid IP address from tunnel...
 
2017-03-12 06:23:42,784 DEBG 'deluge-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.9.10.6'
 
2017-03-12 06:23:45,517 DEBG 'deluge-script' stdout output:
[debug] External IP address from tunnel is '46.166.188.204'
 
2017-03-12 06:23:45,929 DEBG 'deluge-script' stdout output:
[debug] VPN incoming port is 23649
 
2017-03-12 06:23:45,931 DEBG 'deluge-script' stdout output:
[debug] VPN IP is 10.9.10.6
[debug] Deluge incoming port is 23649
[debug] Deluge IP is 10.9.10.6
 
2017-03-12 06:24:15,942 DEBG 'deluge-script' stdout output:
[debug] Waiting for valid IP address from tunnel...
 
2017-03-12 06:24:16,130 DEBG 'deluge-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.9.10.6'
 
2017-03-12 06:24:24,442 DEBG 'deluge-script' stdout output:
[debug] External IP address from tunnel is '46.166.188.204'
 
2017-03-12 06:24:24,817 DEBG 'deluge-script' stdout output:
[debug] VPN incoming port is 23649
[debug] VPN IP is 10.9.10.6
[debug] Deluge incoming port is 23649
 
2017-03-12 06:24:24,818 DEBG 'deluge-script' stdout output:
[debug] Deluge IP is 10.9.10.6
 
2017-03-12 06:24:54,823 DEBG 'deluge-script' stdout output:
[debug] Waiting for valid IP address from tunnel...
 
2017-03-12 06:24:55,010 DEBG 'deluge-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.9.10.6'
 
2017-03-12 06:24:57,321 DEBG 'deluge-script' stdout output:
[debug] External IP address from tunnel is '46.166.188.204'
 
2017-03-12 06:24:57,695 DEBG 'deluge-script' stdout output:
[debug] VPN incoming port is 23649
[debug] VPN IP is 10.9.10.6
[debug] Deluge incoming port is 23649
 
2017-03-12 06:24:57,696 DEBG 'deluge-script' stdout output:
[debug] Deluge IP is 10.9.10.6
 
2017-03-12 06:25:27,699 DEBG 'deluge-script' stdout output:
[debug] Waiting for valid IP address from tunnel...
 
2017-03-12 06:25:27,879 DEBG 'deluge-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.9.10.6'
 
2017-03-12 06:25:30,169 DEBG 'deluge-script' stdout output:
[debug] External IP address from tunnel is '46.166.188.204'
 
2017-03-12 06:25:30,538 DEBG 'deluge-script' stdout output:
[debug] VPN incoming port is 23649
[debug] VPN IP is 10.9.10.6
[debug] Deluge incoming port is 23649
 
2017-03-12 06:25:30,539 DEBG 'deluge-script' stdout output:
[debug] Deluge IP is 10.9.10.6
 
2017-03-12 06:26:00,545 DEBG 'deluge-script' stdout output:
[debug] Waiting for valid IP address from tunnel...
 
2017-03-12 06:26:00,755 DEBG 'deluge-script' stdout output:
[debug] Valid IP address from tunnel acquired '10.9.10.6'
 
2017-03-12 06:26:03,049 DEBG 'deluge-script' stdout output:
[debug] External IP address from tunnel is '46.166.188.204'
 
2017-03-12 06:26:03,440 DEBG 'deluge-script' stdout output:
[debug] VPN incoming port is 23649
[debug] VPN IP is 10.9.10.6
[debug] Deluge incoming port is 23649
 
2017-03-12 06:26:03,441 DEBG 'deluge-script' stdout output:
[debug] Deluge IP is 10.9.10.6
 
 
 

Just turn off Debug

Sent from my SM-G900F using Tapatalk

Share this post


Link to post

@ysu take a closer look at the two module warnings in the log.

Sent from my D5503
 

Edited by BakedPizza

Share this post


Link to post

Hi:

 

I successfully installed binhex-delugevpn a few days ago and then used delugesiphon to send the torrent info to the container. Today it stopped working and the Options on delugesiphon does not show ConnectionInfo text boxes (see attached). I removed delugesiphon and loaded another extension for deluge "Darknet" but that too could not communicate with the container which makes me think that there is something on my Linux or UnRAID installation that is causing the breakdown in communication. When I copy and paste a link directly in the binhex-delugevpn WebUI it works successfully.

 

Anyone have any idea what could be going wrong. I have done the obvious (reboot etc) but nothing seems to work.

 

I have searched for this issue but don't see it, please direct me to the thread if I have somehow missed it.

Screenshot from 2017-03-13 11:30:25.png

Share this post


Link to post
9 hours ago, silaha said:

Hi:

 

I successfully installed binhex-delugevpn a few days ago and then used delugesiphon to send the torrent info to the container. Today it stopped working and the Options on delugesiphon does not show ConnectionInfo text boxes (see attached). I removed delugesiphon and loaded another extension for deluge "Darknet" but that too could not communicate with the container which makes me think that there is something on my Linux or UnRAID installation that is causing the breakdown in communication. When I copy and paste a link directly in the binhex-delugevpn WebUI it works successfully.

 

Anyone have any idea what could be going wrong. I have done the obvious (reboot etc) but nothing seems to work.

 

I have searched for this issue but don't see it, please direct me to the thread if I have somehow missed it.

Screenshot from 2017-03-13 11:30:25.png

I use the same setup, same version of delugesiphon and the connection info shows up for mine.  I don't see how your delugeVPN could be responsible for that...

Share this post


Link to post
Hi:
 
I successfully installed binhex-delugevpn a few days ago and then used delugesiphon to send the torrent info to the container. Today it stopped working and the Options on delugesiphon does not show ConnectionInfo text boxes (see attached). I removed delugesiphon and loaded another extension for deluge "Darknet" but that too could not communicate with the container which makes me think that there is something on my Linux or UnRAID installation that is causing the breakdown in communication. When I copy and paste a link directly in the binhex-delugevpn WebUI it works successfully.
 
Anyone have any idea what could be going wrong. I have done the obvious (reboot etc) but nothing seems to work.
 
I have searched for this issue but don't see it, please direct me to the thread if I have somehow missed it.
58c64b7e05e03_Screenshotfrom2017-03-13113025.thumb.png.e88ac979645bcdbfbd03b3563c074729.png

Probably due to deluge api changes. Read back a few pages/posts and is been discussed with reference to sickrage, sonarr and other apps.

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