[Support] binhex - DelugeVPN


8725 posts in this topic Last Reply

Recommended Posts

4 minutes ago, glaedr223 said:

So like everyone else I am having issues with PIA port forwarding, decided to be a guinea pig, connected to Austria fine. However I'm still getting the issue in Sonarr and Radarr that is throwing out an error saying they cant connect to any indexers, is this related to this PIA issue or something else? I'm not smart enough to figure this stuff out...

  

depends. have you run them through PIA as well? because the indexers might just block those vpn servers. ;)

Link to post
  • Replies 8.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A n

I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

Posted Images

30 minutes ago, glaedr223 said:

So like everyone else I am having issues with PIA port forwarding, decided to be a guinea pig, connected to Austria fine. However I'm still getting the issue in Sonarr and Radarr that is throwing out an error saying they cant connect to any indexers, is this related to this PIA issue or something else? I'm not smart enough to figure this stuff out...

I have CouchPotato/Jacket working fine through DelugeVPN Privoxy

Edited by PeterB
Link to post

Seems like the :test version is working well. Like everyone else, it takes a while to finally connect, but when it does, I am able to add a torrent to Deluge and it downloads fine. However - I am now having an issue where when the VPN is enabled in the Deluge docker, Sonarr and Radarr are not able to connect to Deluge. When the VPN is off, all works well. It also does not let me use the docker as a proxy server. I have tried Deluge in bridge mode and with it's own IP with no luck.

 

It seems like when the VPN is on, it is not allowing local traffic at all. I've had no luck searching this topic to find a resolution (also having to wait 5-15 minutes for the VPN to connect after every change makes the troubleshooting take forever :) ). Anyone had any experience with this that could point me in the right direction?

Link to post
1 hour ago, MisterOrange said:

Seems like the :test version is working well. Like everyone else, it takes a while to finally connect, but when it does, I am able to add a torrent to Deluge and it downloads fine. However - I am now having an issue where when the VPN is enabled in the Deluge docker, Sonarr and Radarr are not able to connect to Deluge. When the VPN is off, all works well. It also does not let me use the docker as a proxy server. I have tried Deluge in bridge mode and with it's own IP with no luck.

 

It seems like when the VPN is on, it is not allowing local traffic at all. I've had no luck searching this topic to find a resolution (also having to wait 5-15 minutes for the VPN to connect after every change makes the troubleshooting take forever :) ). Anyone had any experience with this that could point me in the right direction?

I am using the test version and Sonarr/Radarr are working.  Yes, it took a while to fully connect, but it did so.

Link to post
10 hours ago, Druiff said:

Might the docker/vpn overwhelm my modem or/and do I have a shitty modem?

most probably yes, this is a fairly common issue with consumer modem/routers, you could try reducing the number of connections ni deluge.

Link to post
1 hour ago, MisterOrange said:

Seems like the :test version is working well. Like everyone else, it takes a while to finally connect, but when it does, I am able to add a torrent to Deluge and it downloads fine. However - I am now having an issue where when the VPN is enabled in the Deluge docker, Sonarr and Radarr are not able to connect to Deluge. When the VPN is off, all works well. It also does not let me use the docker as a proxy server. I have tried Deluge in bridge mode and with it's own IP with no luck.

 

It seems like when the VPN is on, it is not allowing local traffic at all. I've had no luck searching this topic to find a resolution (also having to wait 5-15 minutes for the VPN to connect after every change makes the troubleshooting take forever :) ). Anyone had any experience with this that could point me in the right direction?

most probably badly configured LAN_NETWORK, see here Q4 :- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to post
4 minutes ago, binhex said:

most probably yes, this is a fairly common issue with consumer modem/routers, you could try reducing the number of connections ni deluge.

its only at like 300 connections. but I will try lower.

The low speeds issue has to do with the problems PIA has to fix?

Link to post
1 minute ago, Druiff said:

The low speeds issue has to do with the problems PIA has to fix?

im not aware of any low speed issues with pia, pia issues at present are all around getting an incoming port assigned, both on current and next gen networks

Link to post
1 minute ago, Nimrad said:

Is this supposed to be v 1.3.x and not 2.0.x?

it will be 2.x, if you are running 1.x then you are on a old tagged version, check your tag in the repository and/or do a 'force update' to get the latest image.

Link to post
2 minutes ago, binhex said:

it will be 2.x, if you are running 1.x then you are on a old tagged version, check your tag in the repository and/or do a 'force update' to get the latest image.

Thanks. Is it possible to “force” 2.0.x version? My trackers allow 2.0, but I’d prefer not to update to 2.1 when that becomes available.

Link to post
3 minutes ago, Nimrad said:

Thanks. Is it possible to “force” 2.0.x version? My trackers allow 2.0, but I’d prefer not to update to 2.1 when that becomes available.

nope, either dont update without checking the tag first, or set it to a 2.x tag name and not latest.

Link to post
22 minutes ago, Nimrad said:

I updated to 2.0 recently, but the AutoRemovePlus plugin is suddenly gone. I’ve tried re-adding it both by uploading the .egg to the plugin folder in the docker appdata and by installing through the webUI. Is this a known issue? It should support 2.x according to the plugin page: https://dev.deluge-torrent.org/wiki/Plugins

I got it to work by removing the py version from the file name and then adding it directly to the plugins folder.

 

FinderScreenSnapz022.jpg.4c5ade98e6e444377ec5e1682197c621.jpg

Link to post
6 hours ago, wgstarks said:

I got it to work by removing the py version from the file name and then adding it directly to the plugins folder.

Thanks for the tip. It only kind of worked for me though. It now shows in my Plugins-list, but wont activate when I try to enable it. All other plugins will activate the UI menu item, but this doesn't. And if I apply/reopen the preferences it's unchecked again. Any idea?

deluge.gif.e7f7131949c22b83b81f65dbc3de584b.gif

 

Edited by Nimrad
Link to post

Had to re-install the docker from scratch today and currently re-adding all the torrents. Can't get thin client to re-connect though. Not sure what I'm missing? Remote connections are enabled on the server. Port 58846 is set in the container. Thin client is set to connect to <serverIP>:58846 with user admin.

 

DelugeScreenSnapz007.jpg.185a3c53cb8ea5cb7d653972b9d3fa80.jpg

Link to post
On 9/26/2020 at 9:57 PM, binhex said:

it will be 2.x, if you are running 1.x then you are on a old tagged version, check your tag in the repository and/or do a 'force update' to get the latest image.

Will you also update PIA VPN connection with older versions of deluge? I prefer to stick with Deluge 1.3 because of the Windows Thin Client and some plugins not working in 2.0.

Link to post

For anyone trying to find PIA legacy servers that currently work with port forwarding I can confirm both Berlin and Spain will connect. You may have to allow several retries but once connected they do appear to be stable. I'm on the east coast and these are the closes servers I've been able to connect to.

Link to post
Will you also update PIA VPN connection with older versions of deluge? I prefer to stick with Deluge 1.3 because of the Windows Thin Client and some plugins not working in 2.0.
No I'm afraid that is not going to happen.

Sent from my CLT-L09 using Tapatalk

Link to post

Sooo... I've been trying to figure this out on my own since two days but as I'm just failing at that, I'm asking for your help.

 

Until last week, the docker was running without problem using Mullvad VPN. I think that the only thing that I changed on my system was to update the docker.

My problem is that I can't access the GUI (connexion failed) because the app does not completely sarts... It gets into a loop :

 

2020-09-28 10:50:20,362 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2020-09-28 10:50:20,401 DEBG 'start-script' stdout output:
Mon Sep 28 10:50:20 2020 WARNING: file 'credentials.conf' is group or others accessible
Mon Sep 28 10:50:20 2020 OpenVPN 2.4.9 [git:makepkg/9b0dafca6c50b8bb+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Mon Sep 28 10:50:20 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10

2020-09-28 10:50:20,401 DEBG 'start-script' stdout output:
Mon Sep 28 10:50:20 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2020-09-28 10:50:20,404 DEBG 'start-script' stdout output:
Mon Sep 28 10:50:20 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]XXX.XXX.XXX.XXX:1302
Mon Sep 28 10:50:20 2020 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
Mon Sep 28 10:50:20 2020 UDP link local: (not bound)
Mon Sep 28 10:50:20 2020 UDP link remote: [AF_INET]XXX.XXX.XXX.XXX:1302

2020-09-28 10:51:20,044 DEBG 'start-script' stdout output:
Mon Sep 28 10:51:20 2020 [UNDEF] Inactivity timeout (--ping-restart), restarting

2020-09-28 10:51:20,044 DEBG 'start-script' stdout output:
Mon Sep 28 10:51:20 2020 SIGHUP[soft,ping-restart] received, process restarting

2020-09-28 10:51:20,045 DEBG 'start-script' stdout output:
Mon Sep 28 10:51:20 2020 WARNING: file 'credentials.conf' is group or others accessible
Mon Sep 28 10:51:20 2020 OpenVPN 2.4.9 [git:makepkg/9b0dafca6c50b8bb+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Mon Sep 28 10:51:20 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10

2020-09-28 10:51:20,045 DEBG 'start-script' stdout output:
Mon Sep 28 10:51:20 2020 Restart pause, 5 second(s)

2020-09-28 10:51:20,044 DEBG 'start-script' stdout output:
Mon Sep 28 10:51:20 2020 [UNDEF] Inactivity timeout (--ping-restart), restarting

2020-09-28 10:51:20,044 DEBG 'start-script' stdout output:
Mon Sep 28 10:51:20 2020 SIGHUP[soft,ping-restart] received, process restarting

2020-09-28 10:51:20,045 DEBG 'start-script' stdout output:
Mon Sep 28 10:51:20 2020 WARNING: file 'credentials.conf' is group or others accessible

supervisord.log 

 

I think, one hint is "UDP link local: (not bound)", but I could not figure out how to solve this... As I said I haven't changed anything on my system. At least not consciously ^^

 

 

Edited by bjornatic
Link to post

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.