[Support] binhex - DelugeVPN


Recommended Posts

2 minutes ago, binhex said:

you realise you are running this with the vpn disabled right?, so no protection, from your log:-
 

2022-04-17 03:28:38.281269 [info] VPN_ENABLED defined as 'no'
2022-04-17 03:28:38.303147 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE

as to the cause of the slowdown, its possible that your isp is throttling your torrent traffic as its visible, and/or you havent setup port forwarding correctly.

Hi binhex - yes I am ware that I am running this without a VPN enable as I have move my VPN settings to my pfsense, as I wanted to protect a few diffferance VLANS, and I was having issues trying to get it, to go through your deluge.

 

regarding the throttling,  to my knowledge my ISP are not doing this, as as stated, that if I am not doing any downloading via the deluge then I have about 100mb connection, but as so as I download anything within deluge, when it drops down to 1mb.

 

Link to comment
27 minutes ago, binhex said:

when you say 'it' im asuming you mean your lan internet connection right?. so everything on your lan suddenly drops to 1Mb/s or there abouts?

that is right.

 

I just did a test, but disabling my VPN on my PFSENSE, and then do a download within deluge - pulling down a Linux ISO and it come down @ 3mbs and my LAN was 100mbs.

 

sorry but it might be my openVPN connection to PIA. to test this I will move my VPN back to deluge and retry

 

UPDATE:

I just did the same test, but with the VPN turn on within Deluge and I got the same results.  I will have a word with PIA

Edited by chris_netsmart
Link to comment

I have a script I'm trying to run on completion of a file (via execute plugin). It basically just runs a curl command but it is timing out. In trying to troubleshoot the issue I've realized that I can curl google.com and get results and of course get my ip with curl ifconfig.co but when I try to curl my unraid IP it times out. I'm actually trying to issue a curl to an API at 192.168.0.5:9393 but regardless just trying to run curl on any internal IP times out. Is this expected behavior or do I have some other issue?

  • Upvote 1
Link to comment
26 minutes ago, Tolete said:

Deluge keeps dropping seeders, torrent stuck at 94%. All other torrents download without problem. -In the peers tab i see it connects to seeders (100%) but quickly drops them. send help!😩

Do any of those seeders show as 100%? If everyone is seeding a torrent that they only have 94% of then that's all you'll get. Its possible that you have all the files complete but one is missing from what the original torrent had.

Link to comment
27 minutes ago, wgstarks said:

Do any of those seeders show as 100%? If everyone is seeding a torrent that they only have 94% of then that's all you'll get. Its possible that you have all the files complete but one is missing from what the original torrent had.

 

 "-In the peers tab i see it connects to seeders (100%) but quickly drops them."

Also, torrent has been 'force re-check' removed, re added. been having this problem for some time with this torrent only. 

Edited by Tolete
Link to comment
22 hours ago, pinion said:

I have a script I'm trying to run on completion of a file (via execute plugin). It basically just runs a curl command but it is timing out. In trying to troubleshoot the issue I've realized that I can curl google.com and get results and of course get my ip with curl ifconfig.co but when I try to curl my unraid IP it times out. I'm actually trying to issue a curl to an API at 192.168.0.5:9393 but regardless just trying to run curl on any internal IP times out. Is this expected behavior or do I have some other issue?

i have the exact same issue, trying to run execute plugin calling another docker container but the request is timing out

Link to comment
22 hours ago, pinion said:

I have a script I'm trying to run on completion of a file (via execute plugin). It basically just runs a curl command but it is timing out. In trying to troubleshoot the issue I've realized that I can curl google.com and get results and of course get my ip with curl ifconfig.co but when I try to curl my unraid IP it times out. I'm actually trying to issue a curl to an API at 192.168.0.5:9393 but regardless just trying to run curl on any internal IP times out. Is this expected behavior or do I have some other issue?

 

14 minutes ago, MammothJerk said:

i have the exact same issue, trying to run execute plugin calling another docker container but the request is timing out

 

I think this would be the applicable fix:

Quote

A27. 

Due to iptables tightening it is now a requirement that you add the Web UI/API ports for applications on the LAN to the env var key 'VPN_OUTPUT_PORTS', with the ports being the value, this will then permit applications running in the VPN network to access applications on the LAN, if you have multiple ports then please separate the values with a comma, e.g. 'VPN_OUTPUT_PORTS' = 1234,5678

 

An example of this requirement is when having Sonarr/Radarr/Lidarr routed through a VPN container and these apps requiring access to nzbget running on the LAN, in this case you would define VPN_OUTPUT_PORTS = 6789 (default port for nzbget), this would then allow the index app (Sonarr/Radarr/Lidarr) to connect to the download client (nzbget).

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

You may also be hitting the Docker network configuration default security model, where containers on the default network cannot communicate directly with the host (Unraid).

  • Like 1
Link to comment
49 minutes ago, tjb_altf4 said:

 

 

I think this would be the applicable fix:

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

You may also be hitting the Docker network configuration default security model, where containers on the default network cannot communicate directly with the host (Unraid).

Yes that does indeed work!

I only recall having to mess with VPN_INPUT_PORTS and was not aware of the VPN_OUTPUT_PORTS variable as well.

 

Thanks!

Spoiler

this somewhat works but is not the most ideal solution.

the container i'm calling for in the execute script has to be on the "delugevpn" container network with --net=container:delugevpn for this to work.

then be called as localhost:port in the execute script.

this container can then not communicate with anything else outside the "delugevpn" network so even more containers need to be added to the "delugevpn" network.

If this is the only way then that is what i have to do but i was hoping there was another way.

 

Edited by MammothJerk
i cant read
Link to comment

I've been having issues since updating to the latest version of unraid (6.10.0-rc5 ) , no issues for months previously. Deluge will only load if the VPN is set to "off". I've confirmed this is currently happening with the binhex-delugevpn & binhex-qbittorrentvpn. I've tried changing server locations but having the same issues. I've confirmed my VPN is working elsewhere (I'm with PIA using OpenVPN)

 

 

Link to comment
2 hours ago, Joz104 said:

I've been having issues since updating to the latest version of unraid (6.10.0-rc5 ) , no issues for months previously. Deluge will only load if the VPN is set to "off". I've confirmed this is currently happening with the binhex-delugevpn & binhex-qbittorrentvpn. I've tried changing server locations but having the same issues. I've confirmed my VPN is working elsewhere (I'm with PIA using OpenVPN)

 

 

Do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md also post your docker run command in your next post

Link to comment
On 4/28/2022 at 7:49 PM, tjb_altf4 said:

 

 

I think this would be the applicable fix:

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

You may also be hitting the Docker network configuration default security model, where containers on the default network cannot communicate directly with the host (Unraid).

Thank you so much. That was the issue. I swear I read through that (probably more like skimmed) and just didn't realize probably because I wasn't trying to make the other container go through the VPN. Looks like for containers that go through the VPN it's a lot easier to add their ports now than it used to be.

Link to comment
1 hour ago, cromwell said:

same here. what's the story here?

Google search shows that xmrig is a cryptominer possibly installed as part of one of your plugins. Possibly delete your plugins and re-install one-at-a-time. A google search for xmrig will give lots of hits.

Link to comment

I've been having a problem lately that eventually it seems the connection will drop and torrents will be auto-added but cannot connect to peers, show availability as 0 and get stuck at 0.  Restarting the container and re-adding torrents manually will get them going again.

 

Using PIA as my vpn provider.  Anyone else experiencing this?

Link to comment

EDIT: FIXED, i got tired and installed qbit, worked like a charm

 

Hi, updated to latest binhex-delugevpn, and i was running deluge fine. But suddenly today deluge shutdown and when i restart the docker it seem to be stopping at "[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2022-05-02 00:07:04,297 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.1.112.220'
[info] Deluge key 'listen_interface' will have a new value '10.1.112.220'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-02 00:07:04,429 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'..."

 

Webgui dont start. And im left guessing what to do as everything should work. i have not changed any config

 

edit: 20 min later "2022-05-02 00:22:03,545 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38349'"

 

but still no webgui.

 

edit again: never mind. Got tired of all the problems with deluge and installed qbit, worked right out of the box.

Edited by orlando500
Link to comment

need help with this one family. On DelugeVPN 2.0.5  dropping seeders/not connecting to seeders on one specific torrent.

torrent stuck at 94%.

 

-force recheck. no joy

-removed re-added. no joy

-delete, redownload, stuck at 88%. no joy

-all other torrents complete with out problem.

 

noticed in the peers tab seeds are found but are quickly dropped. any ideas on how to resolved this?

 

Edited by Tolete
Link to comment

puzzled, been trucking along for a good while with delugevpn with zero issues.  Notice some stuff failed to download the other day so started poking around.  it seems that for some reason it's restarting like every 3-4 minutes.  I hadn't changed any settings, just started going wonky on me.  This is what I see in the logs, any thoughts?

 

2022-05-05 20:36:15,644 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-05-05 20:36:15,640 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2022-05-05 20:36:15,644 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-05-05 20:39:18,305 DEBG 'watchdog-script' stderr output:
malloc(): invalid next size (unsorted)

2022-05-05 20:39:46,523 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2022-05-05 20:39:46,529 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2022-05-05 20:39:46,642 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.3.112.248'
[info] Deluge key 'listen_interface' will have a new value '10.3.112.248'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-05 20:39:46,765 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

 

 

I assume this would be needed to see what settings I had in there, I have no containers running through it just jackett pointing to the privoxy.

 

2022-05-05 20:35:29.055409 [info] Host is running unRAID
2022-05-05 20:35:29.073482 [info] System information Linux 89fafbb21284 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2022-05-05 20:35:29.093973 [info] OS_ARCH defined as 'x86-64'
2022-05-05 20:35:29.115757 [info] PUID defined as '99'
2022-05-05 20:35:29.141012 [info] PGID defined as '100'
2022-05-05 20:35:29.168625 [info] UMASK defined as '000'
2022-05-05 20:35:29.188791 [info] Permissions already set for '/config'
2022-05-05 20:35:29.209963 [info] Deleting files in /tmp (non recursive)...
2022-05-05 20:35:29.235324 [info] VPN_ENABLED defined as 'yes'
2022-05-05 20:35:29.256301 [info] VPN_CLIENT defined as 'openvpn'
2022-05-05 20:35:29.276492 [info] VPN_PROV defined as 'pia'
2022-05-05 20:35:29.515770 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ca_toronto.ovpn
2022-05-05 20:35:29.558620 [info] VPN remote server(s) defined as 'ca-toronto.privacy.network,'
2022-05-05 20:35:29.576503 [info] VPN remote port(s) defined as '1198,'
2022-05-05 20:35:29.594216 [info] VPN remote protcol(s) defined as 'udp,'
2022-05-05 20:35:29.614682 [info] VPN_DEVICE_TYPE defined as 'tun0'
2022-05-05 20:35:29.635062 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2022-05-05 20:35:29.655309 [info] LAN_NETWORK defined as '26.0.1.0/24'
2022-05-05 20:35:29.675496 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2022-05-05 20:35:29.695567 [info] VPN_USER defined as 'REDACTED'
2022-05-05 20:35:29.715717 [info] VPN_PASS defined as 'REDACTED'
2022-05-05 20:35:29.735793 [info] STRICT_PORT_FORWARD defined as 'yes'
2022-05-05 20:35:29.755905 [info] ENABLE_PRIVOXY defined as 'yes'
2022-05-05 20:35:29.778823 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2022-05-05 20:35:29.799234 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2022-05-05 20:35:29.820493 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2022-05-05 20:35:29.841310 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2022-05-05 20:35:29.863208 [info] Starting Supervisor...
2022-05-05 20:35:30,013 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2022-05-05 20:35:30,014 INFO Set uid to user 0 succeeded
2022-05-05 20:35:30,016 INFO supervisord started with pid 7
2022-05-05 20:35:31,018 INFO spawned: 'shutdown-script' with pid 183
2022-05-05 20:35:31,019 INFO spawned: 'start-script' with pid 184
2022-05-05 20:35:31,021 INFO spawned: 'watchdog-script' with pid 185
2022-05-05 20:35:31,021 INFO reaped unknown pid 8 (exit status 0)

 

 

Best Regards,

-Knoxxiv

Link to comment
On 5/5/2022 at 8:56 PM, CBPXXIV said:

puzzled, been trucking along for a good while with delugevpn with zero issues.  Notice some stuff failed to download the other day so started poking around.  it seems that for some reason it's restarting like every 3-4 minutes.  I hadn't changed any settings, just started going wonky on me.  This is what I see in the logs, any thoughts?

 

2022-05-05 20:36:15,644 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-05-05 20:36:15,640 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2022-05-05 20:36:15,644 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2022-05-05 20:39:18,305 DEBG 'watchdog-script' stderr output:
malloc(): invalid next size (unsorted)

2022-05-05 20:39:46,523 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2022-05-05 20:39:46,529 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2022-05-05 20:39:46,642 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.3.112.248'
[info] Deluge key 'listen_interface' will have a new value '10.3.112.248'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-05 20:39:46,765 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

 

 

Best Regards,

-Knoxxiv

 

It appears I'm having this exact same issue.  Hangs at the same point and the WebUI doesn't load.

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...


Sometimes, after leaving it for a few hours, it seems to move to the next step:

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 14:06:11,257 DEBG 'watchdog-script' stdout output:
[warn] Deluge config file /config/web.conf does not contain valid data, exiting Python script config_deluge.py...

2022-05-07 14:06:11,592 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-05-07 14:06:11,802 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started


However, the WebUI is not responsive and won't load.

I've made no changes to my configuration and it was working for many months before yesterday when this issue popped up.

 

Edit:  I was planning to follow the steps listed here today, but it seems to have started on it's own over night and is running fine now.  I'll update if that changes.

Edited by Earendur
  • Like 1
Link to comment

I'm playing around with the console trying to set up some execute scripts and in trying out a couple of commands i keep getting the same error.

 

trying to resume a torrent that is currently paused i'm sending in the console

deluge console resume oertbgoyertboy792345796yg

and

deluge-console resume oertbgoyertboy792345796yg

gibberish being the hash or $torrentid in the execute script

 

both giving me the error message

Could not connect to daemon: 127.0.0.1:58846
   Password does not match

 

am i using the correct commands here or am i missing something?

Link to comment
On 5/7/2022 at 7:09 PM, Earendur said:

 

It appears I'm having this exact same issue.  Hangs at the same point and the WebUI doesn't load.

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...


Sometimes, after leaving it for a few hours, it seems to move to the next step:

 

2022-05-07 11:09:10,133 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.67.228.49'
[info] Deluge key 'listen_interface' will have a new value '10.67.228.49'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 11:09:10,211 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'wg0'
[info] Deluge key 'outgoing_interface' will have a new value 'wg0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2022-05-07 14:06:11,257 DEBG 'watchdog-script' stdout output:
[warn] Deluge config file /config/web.conf does not contain valid data, exiting Python script config_deluge.py...

2022-05-07 14:06:11,592 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2022-05-07 14:06:11,802 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2022-05-07 14:06:13,029 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...
[info] Deluge Web UI started


However, the WebUI is not responsive and won't load.

I've made no changes to my configuration and it was working for many months before yesterday when this issue popped up.

 

Edit:  I was planning to follow the steps listed here today, but it seems to have started on it's own over night and is running fine now.  I'll update if that changes.

 

 

I've just seen exactly this behaviour (takes many minutes to progess from "[info] Writing changes to Deluge config file '/config/core.conf'...", WebUI nonresponsive, and deluge-web pinning one cpu core at 100%), and have found what was causing it for me.

 

'\appdata\binhex-delugevpn\web.conf' had grown to over 40MB causing both the config-parser script and deluge-web to choke trying to parse it. Looking at the file this was because there were thousands of 'session' entries; I'm guessing that it caches active sessions to the webui in the web.conf, but for some reason never clears them, causing the file to grow out of control.

 

Stopping the image, deleting all of these entries (bringing the file down to a much more reasonable 620bytes), and restarting the image made everything start up quickly with the webui working as normal.

 

Hopefully that's helpful to someone!

Edited by technoluddite
  • Like 2
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.