12 minutes ago, Wouter said:

Also what line in the log is the sensitive information that i need to change? I don't see anything special in it.

2018-07-03 11:17:40.956054 [info] VPN_USER defined as 'redacted'
2018-07-03 11:17:41.034335 [info] VPN_PASS defined as 'redacted'

 

You should change your user name and password right away.

 

If you open the log file in a text editor before posting it you’ll be able to use the find command to locate these.

Edited July 3, 20188 yr by wgstarks
Redaction

I'll change it. I surched with the wrong words to find it.

13 minutes ago, Wouter said:

It is still not working

Where did you get the .ovpn file from? The server listed in your ovpn file is down. Try the one from this zip: https://www.privateinternetaccess.com/openvpn/openvpn.zip

I changed it to the netherlands and it is working. Thanks a lot I have access to the webui. Is the netherlands still an endpoint that supports port forwarding? if not which endpoint would you suggest?

1 minute ago, Wouter said:

Is the netherlands still an endpoint that supports port forwarding? if not which endpoint would you suggest?

No, check this list: https://www.privateinternetaccess.com/helpdesk/kb/articles/how-do-i-enable-port-forwarding-on-my-vpn

I would try Germany, France or Canada

I changed it to Germany and it is not working anymore. Could it be that some old files from my old deluge image (I reinstalled unraid) are still there and are messing things up?

Shouldn't be, but anything is possible I guess. Should be to just stop the container, replace the ovpn file and start the container again. If it's not working you'll need to post a new debug log. Maybe you replaced the ovpn file with another wrong one like you did with Sweden?

I removed the log file again. restart deluge and it is not creating a new log file.

The openvpn file i used is from your link  but for some reason the webui is working but now the torrents give an error and won't download.

permision to the folder denied how can i fix it?

20 minutes ago, Wouter said:

permision to the folder denied how can i fix it?

You are telling the torrents to download to /data, right?

Yes I already tried a different share but i got the same results

14 minutes ago, Wouter said:

Yes I already tried a different share but i got the same results

Please explain what you mean. /data isn't a share.

This is what i ment. Before i used media instead of downloads

1 minute ago, Wouter said:

This is what i ment. Before i used media instead of downloads

That's why it won't work. The screenshot on the left needs to be pointing to /data, like it shows in the orange text on the right.

Like this if i want it to a sub directory?

Still not working

3 minutes ago, Wouter said:

Like this if i want it to a sub directory?

No, you put /Data, it's /data.

Finally it's working Thank you very much for your patience with me.

Now I can eat and sleep again.

Dumb question, sorry if its been answered somewhere else.

When using the flag "STRICT_PORT_FORWARD" is there a way for me to get what the Port its using?

Is it using the ones I defined in Deluge itself or is it getting a random port from PIA?

6 hours ago, strike said:

 

Using blocklist while you're using vpn is pretty useless as @binhex once said:

 

 

 

https://lime-technology.com/forums/topic/44109-support-binhex-delugevpn/?do=findComment&comment=598299

https://lime-technology.com/forums/topic/44109-support-binhex-delugevpn/?do=findComment&comment=598301

 

 

Ah, I see. So I tried unchecking the blocklist plugin, but whenever I restart this docker, it comes back as checked/active. Do you know how I can permanently de-activate the blocklist plugin in my deluge setup?

Dumb question, sorry if its been answered somewhere else.
When using the flag "STRICT_PORT_FORWARD" is there a way for me to get what the Port its using?
Is it using the ones I defined in Deluge itself or is it getting a random port from PIA?

dynamic port from pia.

Sent from my SM-G935F using Tapatalk

8 minutes ago, binhex said:

dynamic port from pia.

Sent from my SM-G935F using Tapatalk
 

 

Hey @binhex just checking, should I do anything to the port settings inside Deluge or is it translating things for me already?

Edited July 4, 20188 yr by AnnabellaRenee87

1 hour ago, AnnabellaRenee87 said:

 
Hey [mention=11148]binhex[/mention] just checking, should I do anything to the port settings inside Deluge or is it translating things for me already?

no you don't need to do anything other than ensuring you're connecting to a VPN Endpoint that allows port forwarding all the port forwarding is done for you in code

Sent from my SM-G935F using Tapatalk
 

Edited July 4, 20188 yr by binhex

So will this container only work if the VPN has port forwarding?
I was using ProtonVPN not to long ago and everything was working fine. I then restarted Unraid and every time I try and connect to the web client, I get the Unable to connect.

I tried redownloading, clearing out all configs and trying it again. Still nothing. I added the *.ovpn file in the correct folder. I get my vpn IP back when I run these commands

docker exec -it binhex-delugevpn /bin/bash

dig +short myip.opendns.com @resolver1.opendns.com

I tried digging through the forum and haven't found anything that worked.

 

 	
Network Type: 	
Privileged: 	
ON
Host Port 1: 	 8112
Container Port: 8112
Host Port 2: 	 58846
Container Port: 58846
Host Port 3: 	 58946
Container Port: 58946
Host Port 4: 	 58946
Container Port: 58946
Host Port 5: 	 8118
Container Port: 8118
Host Path 2: 	 /mnt/cache/torrent-completed/
Container Path: /data

Key 1: 	yes
Container Variable: VPN_ENABLED
Key 2: 	 *
Container Variable: VPN_USER
Key 3: 	 *
Container Variable: VPN_PASS
Key 4: 	custom
Container Variable: VPN_PROV
Key 5: 	 
Container Variable: VPN_OPTIONS
Key 6: 	 yes
Container Variable: STRICT_PORT_FORWARD
Key 7: 	yes
Container Variable: ENABLE_PRIVOXY
Key 8: 	 192.168.90.0/24
Container Variable: LAN_NETWORK
Key 9: 	 209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4
Container Variable: NAME_SERVERS
Key 10: 	yes
Container Variable: DEBUG
Key 11: 	 000
Container Variable: UMASK
Key 12: 	 99
Container Variable: PUID
Key 13: 	 100
Container Variable: PGID
downloading: 	 /mnt/user/torrent-downloading/
Container Path: /downloading
completed: 	 /mnt/user/torrent-completed/
Container Path: /completed
	

 

supervisord.log

So will this container only work if the VPN has port forwarding?
I was using ProtonVPN not to long ago and everything was working fine. I then restarted Unraid and every time I try and connect to the web client, I get the Unable to connect.

I tried redownloading, clearing out all configs and trying it again. Still nothing. I added the *.ovpn file in the correct folder. I get my vpn IP back when I run these commands

docker exec -it binhex-delugevpn /bin/bash

dig +short myip.opendns.com @resolver1.opendns.com

I tried digging through the forum and haven't found anything that worked.
 

Network Type: 	Privileged: 	ONHost Port 1: 	 8112Container Port: 8112Host Port 2: 	 58846Container Port: 58846Host Port 3: 	 58946Container Port: 58946Host Port 4: 	 58946Container Port: 58946Host Port 5: 	 8118Container Port: 8118Host Path 2: 	 /mnt/cache/torrent-completed/Container Path: /dataKey 1: 	yesContainer Variable: VPN_ENABLEDKey 2: 	 *Container Variable: VPN_USERKey 3: 	 *Container Variable: VPN_PASSKey 4: 	customContainer Variable: VPN_PROVKey 5: 	 Container Variable: VPN_OPTIONSKey 6: 	 yesContainer Variable: STRICT_PORT_FORWARDKey 7: 	yesContainer Variable: ENABLE_PRIVOXYKey 8: 	 192.168.90.0/24Container Variable: LAN_NETWORKKey 9: 	 209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4Container Variable: NAME_SERVERSKey 10: 	yesContainer Variable: DEBUGKey 11: 	 000Container Variable: UMASKKey 12: 	 99Container Variable: PUIDKey 13: 	 100Container Variable: PGIDdownloading: 	 /mnt/user/torrent-downloading/Container Path: /downloadingcompleted: 	 /mnt/user/torrent-completed/Container Path: /completed

 
supervisord.log

I would suspect that remote endpoint you are attempting to connect to doesn't exist any more, that's the problem with specifying an IP address instead of a hostname.

Sent from my SM-G935F using Tapatalk