Jump to content
binhex

[Support] binhex - DelugeVPN

3739 posts in this topic Last Reply

Recommended Posts

8 minutes ago, fc0712 said:

 

I did have some weird web gui problems, where I needed to reboot the server around 2 days ago. Could  that have affected Deluge external connectivity? 

 

100% yes!, if you want to permanently fix the issue then click on my sig for vpn docker faq and follow the steps shown for Q1.

 

i should learn to read my own logs eh :-)

 

2017-03-02 23:41:19,137 DEBG 'start-script' stdout output:
[warn] iptable_mangle module not supported, you will not be able to connect to ruTorrent or Privoxy outside of your LAN
[info] Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle'

the above was shown in your supervisord.log file, so this is def your issue, typo in the log there that should be Deluge not ruTorrent

Edited by binhex

Share this post


Link to post
6 hours ago, binhex said:

100% yes!, if you want to permanently fix the issue then click on my sig for vpn docker faq and follow the steps shown for Q1.

 

Just a note, after this latest upgrade to the forum software here, it turned off "View Signatures" for me. I had to go back in to my profile settings and turn it on. Just an FYI in case anyone says "what sig" to you. :-)

Share this post


Link to post
 
Just a note, after this latest upgrade to the forum software here, it turned off "View Signatures" for me. I had to go back in to my profile settings and turn it on. Just an FYI in case anyone says "what sig" to you. :-)

Thanks yes I did turn my SIG on after the migration :-)

Sent from my SM-G900F using Tapatalk

Share this post


Link to post
2 hours ago, Flick said:

 

Just a note, after this latest upgrade to the forum software here, it turned off "View Signatures" for me. I had to go back in to my profile settings and turn it on. Just an FYI in case anyone says "what sig" to you. :-)

Thanks! I noticed I didn't see any sigs anymore and was lost as to why - didn't realize it was an option in profile to show others sigs!

Edited by jlr2000

Share this post


Link to post
22 hours ago, dmacias said:


As this torrent to deluge. Then under Status/Tracker Status it will tell you your ip.
http://checkmytorrentip.net/torrentip/checkMyTorrentIp.png.torrent

Thank for that. I was able to verify that my docker delugevpn container was indeed using the VPN.

 

Since I'm on that topic, is there any information about what happens when the VPN connection goes down? Does this delugevpn container have any VPN kill switch, where deluge completely stops all torrenting once the VPN interface or VPN server is down. Ideally, when the VPN is down, I don't want deluge to do any torrenting. This is precisely to avoid situation such as the following, 

 

https://www.privateinternetaccess.com/forum/discussion/21609/deluge-with-proxy-still-received-copyright-notice

https://www.privateinternetaccess.com/forum/discussion/20879/ip-address-leak-using-pia-proxy-with-deluge

 

Share this post


Link to post

Delugevpn uses strict iptables rules to block the connection if the vpn tunnel goes down.  There have been no reports of ip leaks afaik, but if you know how to use wireshark you can check for yourself.

Share this post


Link to post

Does this docker version of deluge allow us to specify the file permissions chmod of the downloaded torrents?


Sent from my iPad using Tapatalk

Share this post


Link to post

No, not afaik. You could change the UID so it runs as a specific user instead of the nobody user. If you have only one user this can work fine. On my backup server I have done this, as it has only one user. I then make sure I call the user the same on all my other machines which is going to access the files, works fine.

 

If you use couchpotato or sonarr or something I believe you can set the permissions there.

Share this post


Link to post

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. //EDIT: User reported he needed to reboot. I can't remember anymore.
@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.
Edited by BakedPizza
  • Upvote 2

Share this post


Link to post
2 hours ago, BakedPizza said:

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

 

I'm new to both Synology and Docker.  I guess this explains why I can't get it to run properly. :)  I'll be on the lookout for an updated image if something is released to fix the issue for us.

Share this post


Link to post
7 hours ago, 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.

 

Thanks for laying out the solution so clearly, i am just about check-in some additional code to check for the tun module, and exit if not present, i already have code in place to check for iptable_mangle, i wont be forcing exit if this particular module isnt present as the vpn will still come up, you just wont be able to access the interface outside of the lan.

 

as a side note unraid users also suffer an issue with iptable_mangle, where we have to ensure its loaded prior to starting this container otherwise you cannot access it externally.

  • Upvote 1

Share this post


Link to post
5 hours ago, clambert said:

 

I'm new to both Synology and Docker.  I guess this explains why I can't get it to run properly. :)  I'll be on the lookout for an updated image if something is released to fix the issue for us.

 

just to manage your expectations here, the best "fix" i can do is simply to log the error with a suggested fix and exit, i cannot execute any commands to load kernel modules from inside the container.

Share this post


Link to post

Hello and good day 

 

It looks like I have my settings are correct but I can't seem to open up the web gui get a "this site can't be reached refused to connect error" 

 

I have it set to the default port of 8112 

 

I have my log file attached any insight would be great 

 

delugevpn.txt

Share this post


Link to post
10 hours ago, ween101 said:

Hello and good day 

 

It looks like I have my settings are correct but I can't seem to open up the web gui get a "this site can't be reached refused to connect error" 

 

I have it set to the default port of 8112 

 

I have my log file attached any insight would be great 

 

delugevpn.txt

 

i will need the full log file to see the issue, please repost with the full log (minus username and password)

Share this post


Link to post
12 hours ago, binhex said:

 

just to manage your expectations here, the best "fix" i can do is simply to log the error with a suggested fix and exit, i cannot execute any commands to load kernel modules from inside the container.

LOL! That's fine. I'll just have to man up and follow BakedPizza's lead.  I appreciate you keeping it real. :)

Share this post


Link to post
21 hours ago, binhex said:

 

Thanks for laying out the solution so clearly, i am just about check-in some additional code to check for the tun module, and exit if not present, i already have code in place to check for iptable_mangle, i wont be forcing exit if this particular module isnt present as the vpn will still come up, you just wont be able to access the interface outside of the lan.

Sounds fair enough and thanks for your swift consideration. :)Time to look at your arch-medusa container.

Edited by BakedPizza

Share this post


Link to post

Hello All,

I am new to delugevpn and am having a few issues. I am using the label plugin and it will disable itself and therefore cause an error in both radarr and sonarr. I have to go in and reenable the label plugin for radarr and sonarr to work correctly. I am not sure how to go about getting this issue fixed. If it helps i am running the most up to date version of the docker.

Share this post


Link to post

Recently I have been having an issue with this docker, where on startup of unraid, this docker won't work until I manually restart it.

 

Any ideas what could cause this?

 

The log shows the following:

 

2017-03-07 06:05:36,742 DEBG 'start-script' stdout output:
[crit] 'tun' module not available, you will not be able to connect to Deluge or Privoxy outside of your LAN

Share this post


Link to post
2 hours ago, dvd.collector said:

Recently I have been having an issue with this docker, where on startup of unraid, this docker won't work until I manually restart it.

 

Any ideas what could cause this?

 

The log shows the following:

 

2017-03-07 06:05:36,742 DEBG 'start-script' stdout output:
[crit] 'tun' module not available, you will not be able to connect to Deluge or Privoxy outside of your LAN

 

my sig, vpn docker faq q1.

Share this post


Link to post
5 minutes ago, binhex said:

 

my sig, vpn docker faq q1.

 

I've been running unraid 6.3.0 for ages with this docker though with no problem, but I'll try what is listed in the FAQ.

Share this post


Link to post
Just now, dvd.collector said:

 

I've been running unraid 6.3.0 for ages with this docker though with no problem, but I'll try what is listed in the FAQ.

 

trust me, this is your issue, it MAY just work sometimes if you also run a VM on startup, as this forces the iptable_mangle module to load, however its a race to see which one starts first, if docker gets in there first then your stuffed until you restart the container, the fix detailed in my sig will permanently fix it, ensuring iptable_mangle module is available.

Share this post


Link to post
2 hours ago, dvd.collector said:

Recently I have been having an issue with this docker, where on startup of unraid, this docker won't work until I manually restart it.

 

Any ideas what could cause this?

 

The log shows the following:

 

2017-03-07 06:05:36,742 DEBG 'start-script' stdout output:
[crit] 'tun' module not available, you will not be able to connect to Deluge or Privoxy outside of your LAN

This doesn't help a whole lot but I've been having the same issue since I updated this docker image yesterday. I can't access the webui (even after a restart) and have this note in the logs. I tried a fresh config and still have the same error. I'm not sure what else I can do :/ First time having an issue with this docker and I've been using it for a loooong time with the same settings (bridged network, lan_network set correctly for my network, etc.).

Share this post


Link to post
18 minutes ago, PatchyCactus said:

This doesn't help a whole lot but I've been having the same issue since I updated this docker image yesterday. I can't access the webui (even after a restart) and have this note in the logs. I tried a fresh config and still have the same error. I'm not sure what else I can do :/ First time having an issue with this docker and I've been using it for a loooong time with the same settings (bridged network, lan_network set correctly for my network, etc.).

 

this is a completely separate issue, if you cant access the webui even on your home lan then you have another issue, please post your full supervisord.log file.

 

can you also post the output of command "lsmod" executed on your unraid host.

Edited by binhex

Share this post


Link to post
20 minutes ago, binhex said:

 

trust me, this is your issue, it MAY just work sometimes if you also run a VM on startup, as this forces the iptable_mangle module to load, however its a race to see which one starts first, if docker gets in there first then your stuffed until you restart the container, the fix detailed in my sig will permanently fix it, ensuring iptable_mangle module is available.

 

I've added your fix as per the FAQ and rebooted unraid.  I still see the same error in the log and cannot access deluge or privoxy.  If i restart the container it then works.  I'm sure this has only started happening since updating the docker recently.

 

2017-03-07 11:42:17,422 DEBG 'start-script' stdout output:
[crit] 'tun' module not available, you will not be able to connect to Deluge or Privoxy outside of your LAN
[info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/tun.ko'
 

Share this post


Link to post
Just now, dvd.collector said:

 

I've added your fix as per the FAQ and rebooted unraid.  I still see the same error in the log and cannot access deluge or privoxy.  If i restart the container it then works.  I'm sure this has only started happening since updating the docker recently.

 

2017-03-07 11:42:17,422 DEBG 'start-script' stdout output:
[crit] 'tun' module not available, you will not be able to connect to Deluge or Privoxy outside of your LAN
[info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/tun.ko'
 

 

hmm ok so this could be the same issue, but for the tun module too, right for now i will remove the exit, as it was loading ok even without the module being present, i wouldn't expect it to run without this module tbh, but hey maybe the host is loading it JUST before it requires it, i do have some retries in place so this might be why it works, try a pull down of the image in about 2 hours from now.

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