Jump to content
binhex

[Support] binhex - DelugeVPN

6111 posts in this topic Last Reply

Recommended Posts

Two questions:

 

1. In my Deluge GUI client I get an error notification in the bottom status bar "No incoming connections!", after connecting to the docker deluge daemon running on the same machine. The "test active port"  test for incoming ports in the deluge GUI client settings also results in a yellow exclamation mark, the port here set to 58946. I've opened port 58946 for both TCP and UDP in my router, so is this really an issue, or is it a false indicator?

 

2. How can I make my deluge plugins persistently activated between container launches and shutdowns (I always shut down the container when I'm not using deluge), I use LabelPlus, but every time the container is restarted the plug-in is disabled.

 

Cheers

Share this post


Link to post
Two questions:
 
1. In my Deluge GUI client I get an error notification in the bottom status bar "No incoming connections!", after connecting to the docker deluge daemon running on the same machine. The "test active port"  test for incoming ports in the deluge GUI client settings also results in a yellow exclamation mark, the port here set to 58946. I've opened port 58946 for both TCP and UDP in my router, so is this really an issue, or is it a false indicator?
 
2. How can I make my deluge plugins persistently activated between container launches and shutdowns (I always shut down the container when I'm not using deluge), I use LabelPlus, but every time the container is restarted the plug-in is disabled.
 
Cheers
1- the incoming connection port is a setting that comes from your VPN provider. Read their doc to see what range they let though (if any, some don't). Opening ports on your router doesn't help.

2-check the file permissions in your appdata, the deluge config file may be read only

Sent from my SGH-I337M using Tapatalk

Share this post


Link to post
On 24/12/2017 at 6:07 PM, Duggie264 said:

Hi,

 

Relative n00b here, just setting up Deluge VPN, have installed the docker, and added my VPN providers .opvn file to \\........\appdata\binhex-delugevpn\openvpn

 

it contains the folowing lines:

 

(...)

 

remote REMOTE VPN SERVER DN
proto udp

 

(items in bold altered for privacy)

 

When I attempt to start DVPN, the log states " VPN_PORT not found in /config/openvpn/OPVNFILENAME.ovpn

 

I have tried adding "port 443" after the remote line, but this seems to have no effect. Am I missing something really obvious, before I start deep diving into the issue?

 

Thanks,

 

Duggie

 

For me in the .ovpn the port is on the remote line:

 

remote whatever.vpnprovider.com 1196 udp

 

Edited by Gog

Share this post


Link to post
8 hours ago, Gog said:

 

For me in the .ovpn the port is on the remote line:

 


remote whatever.vpnprovider.com 1196 udp

 

Thanks, that has got me past that hurdle, although for some reason it sill wants the protocol name on a separate line ¬¬

 

OK, so after a little more work, I was able to get it up and running.

 

1. Had to add username and password within the docker settings itself.

 

From the ovpn config file;

 

2. Remove the "proto udp" line

3. Add " 443 udp" to end of remote line.

4. Change "ns-cert-type server" to "--remote-cert-tls server"  [removes warning of deprecated command from log file]

 

Seems to be good at the moment, so thanks again!

Edited by Duggie264
To state resolution.

Share this post


Link to post
18 hours ago, Gog said:

1- the incoming connection port is a setting that comes from your VPN provider. Read their doc to see what range they let though (if any, some don't). Opening ports on your router doesn't help.

2-check the file permissions in your appdata, the deluge config file may be read only

 

Got the port forwarding working perfectly, thanks for that.

 

The file permissions are still troubling me, I'm checking the files in /config in the container, but all files are read/write enabled except perms.txt and auth.
What file(s) contains the settings from the GUI/webUI (they should be the same, since if I enable a plugin in either one, it immediately show up in the other)?

Share this post


Link to post

I'd noticed in @gridrunner updated DelugeVPN video the template had changed a little (no STRICT_PORT_FORWARD option etc) compared to my install which I've had since February.

Instead of guessing what had changed I cleaned house (but retained appdata) and reinstalled.

PIA had updated its OpenVPN pack, so I updated that too.

 

I was quite pleased to see the changes to the docker had boosted performance quite a bit (Up+Down) and seemed to be far better at connecting with peers.

 

Thanks @binhex!

Edited by tjb_altf4

Share this post


Link to post
8 minutes ago, tjb_altf4 said:

STRICT_PORT_FORWARD

 

if this wasn't defined in your template (and it might not of been if it was an older template, as changes don't get pushed out) then this should still of meant port forwarding was enabled, as long as you connect to a endpoint that supports it of course, but my suspicion is that you probably didn't have a working incoming port and now you do your seeing better speeds :-).

Share this post


Link to post
On 27/12/2017 at 4:17 AM, 7thSon said:

The file permissions are still troubling me, I'm checking the files in /config in the container, but all files are read/write enabled except perms.txt and auth.
What file(s) contains the settings from the GUI/webUI (they should be the same, since if I enable a plugin in either one, it immediately show up in the other)?

 

deluge config is in .../appdata/binhex-delugevpn/core.conf

Edited by Gog

Share this post


Link to post

Hi, I'm Having trouble connecting sonarr through the delugevpn proxy I followed spaceinvaderones video multiple times. Everything works as it should except when I try to run sonarr through the 8118 port proxy. any help would be greatly appreciated this has been racking my brain for hours.

unraid.JPG

Edited by omgitstechno215

Share this post


Link to post

I don't use sonarr so I don't know if I can help, but are you using sabnzbdvpn and delugevpn at the same time? If so, are privoxy enabled on both? Why does it say it tries to connect to port 8113 in the logs? Privoxy runs on 8118 by default

Share this post


Link to post
18 minutes ago, strike said:

I don't use sonarr so I don't know if I can help, but are you using sabnzbdvpn and delugevpn at the same time? If so, are privoxy enabled on both? Why does it say it tries to connect to port 8113 in the logs? Privoxy runs on 8118 by default

i tried it through both because i couldnt get the deluge one to work. at first i had the delugevpn as the only one running with sab with vpn disabled and privoxy disabled, then switched and tried sab

Share this post


Link to post

First of all just run one of the containers at least until you get everything to work. And do I understand you correctly that it is just privoxy you have have problems with? You have a working tunnel on the delugevpn container and are able to reach the webui with the vpn enabled? 

 

You didn't answer my question why your sonarr logs say it tries to connect to port 8113? It should be 8118, are you sure you have set up the proxy in sonarr correctly? Screenshot?

Share this post


Link to post
1 minute ago, strike said:

First of all just run one of the containers at least until you get everything to work. And do I understand you correctly that it is just privoxy you have have problems with? You have a working tunnel on the delugevpn container and are able to reach the webui with the vpn enabled? 

 

You didn't answer my question why your sonarr logs say it tries to connect to port 8113? It should be 8118, are you sure you have set up the proxy in sonarr correctly? Screenshot?

yea I have it set as 8118, I was screwing around with different ports to try to get it to work that's why the 8113 was there. I can access each web UI for each container and they all connect and work fine till I try to use the proxy setting in sonarr/radarr.

Share this post


Link to post

So what does the log say with 8118 instead of 8113? Radarr I have, could you post a sreenshot of the proxy settings in the general tab in radarr?

Share this post


Link to post
6 minutes ago, strike said:

So what does the log say with 8118 instead of 8113? Radarr I have, could you post a sreenshot of the proxy settings in the general tab in radarr?

 

radarr.JPG

log.JPG

Share this post


Link to post

You have redacted the part I wanted to see... What do you have as the hostname? And it never says in the log that you have tried to connect to 8118. If 192.168.0.11 is your unraid IP address, then that is what the hostname should say. Do not include http(s) or anything else. If you have a working vpn tunnel then all you need to do in radarr is to enable the proxy and put in the correct hostname /port and of course configure radarr to connect with deluge. I also suggest that you move this to the sonarr / radarr  thread as this is not a delugevpn issue but sonarr / radarr  configuration issue. I have radarr  working fine with privoxy . 

Share this post


Link to post
You have redacted the part I wanted to see... What do you have as the hostname? And it never says in the log that you have tried to connect to 8118. If 192.168.0.11 is your unraid IP address, then that is what the hostname should say. Do not include http(s) or anything else. If you have a working vpn tunnel then all you need to do in radarr is to enable the proxy and put in the correct hostname /port and of course configure radarr to connect with deluge. I also suggest that you move this to the sonarr / radarr  thread as this is not a delugevpn issue but sonarr / radarr  configuration issue. I have radarr  working fine with privoxy . 
192.168.0.11 is what I have. I connected and tested each connection everything worked fine, then I turn the proxy setting on with the settings posted above and retested deluge and sab and they both will not connect

Sent from my SM-G950U using Tapatalk

Share this post


Link to post

If 192.168.0.11 is your unraid IP, then your Lan_Network in the delugevpn container setting is wrong. You have 1.0/24 at the end you have redacted the rest. So you shound't even be able to get to the webui. But maybe you have changed that after, clearly you must have since you say you can get to the webui.

Share this post


Link to post
If 192.168.0.11 is your unraid IP, then your Lan_Network in the delugevpn container setting is wrong. You have 1.0/24 at the end you have redacted the rest. So you shound't even be able to get to the webui. But maybe you have changed that after, clearly you must have since you say you can get to the webui.
I changed the 1.0/24 to the what I assumed was correct 0.0/24 like in the unraid iP and I cannot connect to the deluge web ui. This is why I am so lost on this.

Sent from my SM-G950U using Tapatalk

Share this post


Link to post
If 192.168.0.11 is your unraid IP, then your Lan_Network in the delugevpn container setting is wrong. You have 1.0/24 at the end you have redacted the rest. So you shound't even be able to get to the webui. But maybe you have changed that after, clearly you must have since you say you can get to the webui.
Well got it working thanks for the help strike

Sent from my SM-G950U using Tapatalk

Share this post


Link to post

For the last day or two, my vpn connection has been repeatedly falling to zero transfer rate and returning to maximum rate.  There is nothing in the delugevpn container log.

 

It's not just deluge because, at the times the deluge transfer rate is zero, other connections via privoxy also go down.  Other connections which don't go through the vpn tunnel are unaffected.

 

Is The PIA Netherlands server playing up, or is my ISP messing with my vpn connection?  Any thoughts  how to identify the cause?

Share this post


Link to post
For the last day or two, my vpn connection has been repeatedly falling to zero transfer rate and returning to maximum rate.  There is nothing in the delugevpn container log.
 
It's not just deluge because, at the times the deluge transfer rate is zero, other connections via privoxy also go down.  Other connections which don't go through the vpn tunnel are unaffected.
 
Is The PIA Netherlands server playing up, or is my ISP messing with my vpn connection?  Any thoughts  how to identify the cause?
I rarely notice an outage as it auto reconnects but it is possible pia are having issues. To diagnose it further I would advise turning debug on and trawling the log when it drops

Sent from my SM-G935F using Tapatalk

Share this post


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.