Jump to content
binhex

[Support] binhex - DelugeVPN

3967 posts in this topic Last Reply

Recommended Posts

15 hours ago, chesh said:

So, after yesterdays update to both SickRage and Deluge, SickRage is no longer able to connect to Deluge.  Both are using binhex's version of the containers.  Anyone else seeing "2017-03-08 15:53:18 Thread-26 :: [41d7d9d] Request failed: No JSON object could be decoded" when SickRage tries to send a torrent over to Deluge since the update?  Was hoping the Deluge container update today would have fixed the issue, but no luck. I've already tried destroying the dockers and then rebuilding them from template.  Haven't gone the full nuclear option yet and blown away all dockers, docker.img file, and rebuild, but I think this is more of an API issue between programs and not the dockers themselves.  Let me know if it's the software or the dockers, or my stuff is just borked. Thanks!

 

I'm seeing something similar when attempting to access deluge webui

 

2017-03-09 17:39:43,751 DEBG 'deluge-web-script' stderr output:
[ERROR ] 17:39:43 json_api:285 Invalid JSON request content-type: application/x-www-form-urlencoded; charset=UTF-8

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: application/x-www-form-urlencoded; charset=UTF-8

2017-03-09 17:39:57,827 DEBG 'deluge-web-script' stderr output:
[ERROR ] 17:39:57 json_api:285 Invalid JSON request content-type: application/json-rpc

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: application/json-rpc

privoxy and other access seems to work fine

Share this post


Link to post
17 hours ago, chesh said:

So, after yesterdays update to both SickRage and Deluge, SickRage is no longer able to connect to Deluge.  Both are using binhex's version of the containers.  Anyone else seeing "2017-03-08 15:53:18 Thread-26 :: [41d7d9d] Request failed: No JSON object could be decoded" when SickRage tries to send a torrent over to Deluge since the update?  Was hoping the Deluge container update today would have fixed the issue, but no luck. I've already tried destroying the dockers and then rebuilding them from template.  Haven't gone the full nuclear option yet and blown away all dockers, docker.img file, and rebuild, but I think this is more of an API issue between programs and not the dockers themselves.  Let me know if it's the software or the dockers, or my stuff is just borked. Thanks!

I have been getting similar errors in Radarr (linuxserver's container) since the latest delugevpn update:

Unable to connect to Deluge, please check your settings: Unable to connect to Deluge, please check your settings    
HttpClient    HTTP Error - Res: [POST] http://192.168.1.10:8112/json: 500.InternalServerError

And in the docker logs of deluge I have many of these errors

[ERROR ] 12:24:38 json_api:285 Invalid JSON request content-type: application/json-rpc 

I have Sonarr (binhex container) setup with the exact same settings for Deluge and it works fine. Everything was working ok before the update.

 

I am also having issues with the extractor and labels plugins since the update. The extractor settings are no longer available, and I cannot re-enable it in the plugins menu. For the labels plugin, I can see the old labels I have added before, but I cannot add labels to any torrents. It also does not seem to stick when I enable it in settings.

Edited by kroovy

Share this post


Link to post

Hi @daemon9th @chesh @kroovy the reason why you are getting the failure to connect from external apps is because Deluge have fixed a security hole in their webui in release 1.3.14 (latest stable), unfortunately that means that all the other developers for apps that link to deluge need to update their code, i would imagine the app devs will catch up with this change quite quickly, but if you just cant wait then there is a hack detailed in the post below:-

 

http://forum.deluge-torrent.org/viewtopic.php?f=7&t=54428

Share this post


Link to post
2017-03-08 12:00:32,759 DEBG 'deluge-web-script' stderr output:
[ERROR ] 12:00:32 pluginmanagerbase:146 Unable to instantiate plugin!

2017-03-08 12:00:32,761 DEBG 'deluge-web-script' stderr output:
[ERROR ] 12:00:32 pluginmanagerbase:147 Can't extract file(s) to egg cache

The following error occurred while trying to extract file(s) to the Python egg
cache:

[Errno 13] Permission denied: '/home/nobody/.cache/Python-Eggs/Label-0.2-py2.7.egg-tmp'

The Python egg cache directory is currently set to:

/home/nobody/.cache/Python-Eggs

Perhaps your account does not have write access to this directory? You can
change the cache directory by setting the PYTHON_EGG_CACHE environment
variable to point to an accessible directory.

Since the last update I've been noticing this showing up in the logs. Do I need to do anything about this? As far as I can tell it seems to be working. I did try changing the directory but regardless of where it is something doesn't seem to have permissions.

Edited by Leondre

Share this post


Link to post

This was fixed in Sonarr on Mar 7, 2017:

 

2.0.0.4645 - Mar 7 2017 Installed

Fixed Deluge 1.3.14 API support due to changed json-rpc checks. (hotfix)
Fixed DownloadStation client stuck in infinite loop in some cases.
Fixed DownloadStation client failing if non-bt/nzb downloads exist.
Fixed NZBGet delete:scan treated as failure

Share this post


Link to post
On 06/03/2017 at 0:09 AM, BakedPizza said:

To get this container to execute in Docker on the latest Synology version (DSM 6.1-15047 Update 1):

  1. The --cap-add=NET_ADMIN parameter isn't supported by the Docker GUI. Without it iptables won't play nice. Instead select 'Execute container using high privilege' under the General settings of the container.
  2. Make sure that mandatory kernel modules are loaded. We got two options (A & B):
    A. This won't survive a reboot. SSH as an user in the administrators group to your Synology NAS and run the following commands:
    
    sudo insmod /lib/modules/tun.ko
    sudo insmod /lib/modules/iptable_mangle.ko

    B. This will recover the loading during the boot. Create a new 'Triggered Task' from the DSM 'Control Panel' -> 'Task Scheduler'. Select user 'root', event 'Boot-up' and check 'Enabled'. As script enter:
    
    insmod /lib/modules/tun.ko
    insmod /lib/modules/iptable_mangle.ko

     

  3. Done.
@binhex:
Could you please consider adding an option to shutdown the container with a non-zero status if these modules are not loaded (if possible)? Currently the container appears to be running, but Deluge will not be loaded because of these missing modules. It took me some time to figure out why I couldn't reach Deluge.
 
Also, Synology Docker contains and option (in the GUI) to auto restart the container on unexpected shutdown (non-zero exit status). I think it will append --restart failure to the docker command. If you add this shutdown we will always have enough time to make sure the loading of the required modules is done during the boot-up (using the Task Scheduler).
 
Thank you so much for the container. :) The most used 3rd packages source for our Synology NAS systems (SynoCommunity) is currently incompatible with the latest version of the operation system (DSM 6+) and it looks like it will be the case for a long time. So containers like these are essential for us.

 

 

@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!

Edited by Hansel

Share this post


Link to post
29 minutes ago, mr-hexen said:

This was fixed in Sonarr on Mar 7, 2017:

 

2.0.0.4645 - Mar 7 2017 Installed

Fixed Deluge 1.3.14 API support due to changed json-rpc checks. (hotfix)
Fixed DownloadStation client stuck in infinite loop in some cases.
Fixed DownloadStation client failing if non-bt/nzb downloads exist.
Fixed NZBGet delete:scan treated as failure

Know where to find SickRage's in-depth changelog? All I could seem to find was last updated in February.

Share this post


Link to post
Just now, chesh said:

Know where to find SickRage's in-depth changelog? All I could seem to find was last updated in February.

 

Nope, i moved away from SickRage a year or two ago and never looked back. I think this was the era where their updates / development was stale..Sonarr has been ROCK solid and a pleasure.

Share this post


Link to post

So right now I'm having 2 small issues if you don't count the Transdrone issue reported above.  Thanks for that btw, I was pulling my hair out trying to figure out why it wouldn't connect.  Anyway, I know this is tied to Sonarr (linuxserver image) so I apologize in advance if it's not a Deluge issue. For the record Sonarr is up to date on 2.0.0.4648 (3.9.2017).  Deluge is on 1.3.14.

 

  1. Sonarr adds the torrent to Deluge and labels it properly.  Once the download is done it's not completing the download handling as it does with a nzb by moving and renaming the file.  As a result the show is never moved to the proper TV Show directory that I have defined in Sonarr.  I must be missing a setting on Deluge or Sonarr somewhere.  The downloaded files are located within a directory of the download in my designated /data directory. 
  2. I've added and enabled the Auto Remove Plus plugin for Deluge.  Once the ratio or seed time is met I have it set to remove the torrent.  Instead of removing the torrent it's just pausing the torrent.  I need to go back and manually remove it myself.  Any idea what might be going on here?

Any enlightenment would greatly be appreciated.  Is it wrong that I enjoy playing with setting up these Docker containers more than watching TV Shows or a movie?  Kinda funny actually.

Share this post


Link to post

 

39 minutes ago, clambert said:
  1. Sonarr adds the torrent to Deluge and labels it properly.  Once the download is done it's not completing the download handling as it does with a nzb by moving and renaming the file.  As a result the show is never moved to the proper TV Show directory that I have defined in Sonarr.  I must be missing a setting on Deluge or Sonarr somewhere.  The downloaded files are located within a directory of the download in my designated /data directory. 

 

I haven't had issues with this personnaly but while setting up I read that the path to your downloaded files needs to be the same in both container.  Same path, same container path

 

I haven't looked at the API but I'm guessing that when Deluge talks to sonarr to say the file is ready, the filepath is sent and if it doesn't match sonarr is left swinging in the wind.

 

As for the remove, I just use the label option -> remove at ratio but I'm not sure that really works yet

 

  • Upvote 1

Share this post


Link to post
1 hour ago, Gog said:

 

 

I haven't had issues with this personnaly but while setting up I read that the path to your downloaded files needs to be the same in both container.  Same path, same container path

 

I haven't looked at the API but I'm guessing that when Deluge talks to sonarr to say the file is ready, the filepath is sent and if it doesn't match sonarr is left swinging in the wind.

 

As for the remove, I just use the label option -> remove at ratio but I'm not sure that really works yet

 

 

Once I added /data to the Sonarr Docker, exactly as it was setup in Deluge, it worked just fine.  I also added the label option so we'll see if that works for removing the torrent.  Regardless, I'm happy.  Thank you very much for the help!

 

 

Share this post


Link to post
On 2/12/2017 at 4:13 PM, binhex said:

thanks to death.hilarious for the heads up on the pia api change, i have now included the switch over to the shiny new pia api used to assign a port forward, if any issues then please let me know.

 

link for anybody interested;- https://www.privateinternetaccess.com/forum/discussion/23431/new-pia-port-forwarding-api

6
 

 

In the DelugeVPN log, I found that the following message shows up every 30-60 seconds:

2017-03-09 22:29:18,516 DEBG 'deluge-script' stdout output:
Setting listen_ports to (6890, 6890)..
Configuration value successfully updated.

2017-03-09 22:29:18,542 DEBG 'deluge-script' stdout output:
[info] Deluge started

2017-03-09 22:29:48,672 DEBG 'deluge-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

 

It seems like this is the same issue but I'm not completely sure.  My best guess is there is a setting I'm missing or a step I missed to fix this issue.  

 

I use PIA and have attached the log file from tonight.

 

Thanks in advance for any help!!

Scott

supervisord.log

Share this post


Link to post

Starting with a couple of updates ago, I'm getting a permissions error for the plugins, which prevents any of them from loading. Attached relevant part of the log.

 

The /home/nobody/.cache folder is owned by root:root. Changing this to nobody:users and restarting the container fixes things, but it would be great if you could have a look and see what's causing it.

deluge.log

Share this post


Link to post
 
In the DelugeVPN log, I found that the following message shows up every 30-60 seconds:
2017-03-09 22:29:18,516 DEBG 'deluge-script' stdout output:
Setting listen_ports to (6890, 6890)..
Configuration value successfully updated.

2017-03-09 22:29:18,542 DEBG 'deluge-script' stdout output:
[info] Deluge started

2017-03-09 22:29:48,672 DEBG 'deluge-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
 
It seems like this is the same issue but I'm not completely sure.  My best guess is there is a setting I'm missing or a step I missed to fix this issue.  
 
I use PIA and have attached the log file from tonight.
 
Thanks in advance for any help!!
Scott
supervisord.log


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

Share this post


Link to post

I am relatively new to UnRaid and Binhex's wonderful DelugeVPN but I am experiencing a problem which has left me stumped but I just know it's going to be a simple fix !

 

I have Binhex's Deluge VPN set-up on UnRaid 6.3.2 and when I try and start the WebUI it comes up with a "page not found" message. If I set the VPN_ENABLED=NO it works fine. All indications suggest a problem with my PIA user / password but I have triple checked these and they are fine.

 

I have checked my default gateway, which sits at 192.168.1.254 so the LAN_NETWORK looks ok, so I am stumped for now......the logs show it seems to be stuck with :

 

2017-03-10 09:49:44,091 DEBG 'start-script' stdout output:
[debug] Waiting for valid IP address from tunnel...

Fri Mar 10 09:49:44 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]213.120.234.114:1198
Fri Mar 10 09:49:44 2017 UDP link local: (not bound)
Fri Mar 10 09:49:44 2017 UDP link remote: [AF_INET]213.120.234.114:1198

 

The deployed ports shows :

deployed host ports ...
  crashplan4242 4243 4280 4239
  plexmediaserver
  netdata
  binhex-delugevpn8112 58846 58946 58946 8118

 

I have attached logs and hope that someone can point out the glaring obvious mistake I have made :)

 

Cheers!

delugevpn-log.txt

ifconfig.txt

Supervisord.log.txt

Share this post


Link to post

Show a screen shot of your docker config for the deluge docker.. wipe out the username / pass.

Share this post


Link to post

@watsoma if you have set your LAN_NETWORK to 192.168.1.254, which is kinda implied by your quote below, then this is incorrect, click on link in my sig to vpn docker faq, its in there as to how to identify and set it correctly.

 

Quote

which sits at 192.168.1.254 so the LAN_NETWORK 

 

hmm just seen your screenshot it looks ok.

Edited by binhex

Share this post


Link to post
4 minutes ago, binhex said:

@watsoma if you have set your LAN_NETWORK to 192.168.1.254, which is kinda implied by your quote below, then this is incorrect, click on link in my sig to vpn docker faq, its in there as to how to identify and set it correctly.

 

 

sorry, I should have clarified :

 

The router sits at 192.168.1.254 and the UnRaid server is static at 192.168.1.75. The netmask according to the ifconfig from UnRaid is 255.255.255.0 so I have the LAN_NETWORK set to 192.168.1.0/24.

Share this post


Link to post
Just now, watsoma said:

sorry, I should have clarified :

 

The router sits at 192.168.1.254 and the UnRaid server is static at 192.168.1.75. The netmask according to the ifconfig from UnRaid is 255.255.255.0 so I have the LAN_NETWORK set to 192.168.1.0/24.

 

yep thats fine, that is correctly configured, still going through your logs...

Share this post


Link to post
2 minutes ago, binhex said:

 

yep thats fine, that is correctly configured, still going through your logs...

 

Ya nothing is jumping out from the logs for me either...do you have any special characters or spaces in your username / password? Verify the username / password on the pia website too.

 

The log's saying using previous IP, never seen that message before.

Edited by mr-hexen

Share this post


Link to post
Just now, mr-hexen said:

 

Ya nothing is jumping out from the logs for me either...do you have any special characters or spaces in your username / password?

 

The log's saying using previous IP, never seen that message before.

 

The username is standard from PIA (i.e. P followed by 7 numbers) and the password just contains standard A-Z (mixed case) and 0-9. I had noted that special characters can sometimes cause issues so I avoided them....

Share this post


Link to post
13 minutes ago, watsoma said:

 

The username is standard from PIA (i.e. P followed by 7 numbers) and the password just contains standard A-Z (mixed case) and 0-9. I had noted that special characters can sometimes cause issues so I avoided them....

 

it looks like you have dns hijacking going on (prbably your ISP), here is name resolution output from your log:-

 

Quote

2017-03-10 09:49:43,919 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 51772
;; flags: qr rd ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; nl.privateinternetaccess.com.        IN      A

;; ANSWER SECTION:
nl.privateinternetaccess.com.   30      IN      A       213.120.234.114
nl.privateinternetaccess.com.   30      IN      A       213.120.234.150

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 21 msec
;; SERVER: 8.8.8.8
;; WHEN: Fri Mar 10 09:49:43 2017
;; MSG SIZE  rcvd: 78
 

 

and here is what it should look like:-

 

Quote

2017-03-09 21:15:09,216 DEBG 'start-script' stdout output:
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 11197
;; flags: qr rd ra ; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; nl.privateinternetaccess.com.    IN    A

;; ANSWER SECTION:
nl.privateinternetaccess.com.    299    IN    A    46.166.138.130
nl.privateinternetaccess.com.    299    IN    A    109.201.154.148
nl.privateinternetaccess.com.    299    IN    A    109.201.154.153
nl.privateinternetaccess.com.    299    IN    A    46.166.138.137
nl.privateinternetaccess.com.    299    IN    A    46.166.188.198
nl.privateinternetaccess.com.    299    IN    A    46.166.138.142
nl.privateinternetaccess.com.    299    IN    A    109.201.138.247
nl.privateinternetaccess.com.    299    IN    A    46.166.188.223
nl.privateinternetaccess.com.    299    IN    A    46.166.138.168
nl.privateinternetaccess.com.    299    IN    A    46.166.186.214
nl.privateinternetaccess.com.    299    IN    A    185.107.44.38
nl.privateinternetaccess.com.    299    IN    A    46.166.190.214
nl.privateinternetaccess.com.    299    IN    A    109.201.152.240

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 33 msec
;; SERVER: 8.8.8.8
;; WHEN: Thu Mar  9 21:15:09 2017
;; MSG SIZE  rcvd: 254
 

 

notice the ip's returned in your case is significantly shorter, i think you will find the two ip's your seeing listed are most probably your ISP's name servers. 

 

confirmed ip address 213.120.234.114 is owned by BT.

 

so you can try switching your dns from BT to say google, you will need to do this for unraid (if defined) and on your router.

Edited by binhex
  • Upvote 1

Share this post


Link to post
31 minutes ago, binhex said:

 

it looks like you have dns hijacking going on (prbably your ISP), here is name resolution output from your log:-

 

 

and here is what it should look like:-

 

 

notice the ip's returned is significantly shorter, i think you will find the two ip's your seeing listed are most probably your ISP's name servers. 

 

confirmed ip address 213.120.234.114 is owned by BT.

 

so you can try switching your dns from BT to say google, you will need to do this for unraid (if defined) and on your router.

 

Thanks - I'll give this a shot and see if that resolves it.

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