[Support] binhex - DelugeVPN

[SaberTreasures]

Wondering if there is anyone out there that can help me understand why many torrent downloads will get to 90+% downloaded in binhex-delugevpn docker and then it will just stop.  Sometimes, it will start for a few minutes and then just stop forever.  Since it happens so frequently I'm assuming it's something on my part (settings or something) instead of just the seeds are low etc. For example, right now I have 50 stuck at 98%, and 50 stuck between 20-40% but then a new torrent coming on will start up perfectly fine for a while at least.  There are others that finish just fine though.    Any thoughts would be appreciated or if I can elaborate or provide anything to help.  If not, no worries!

[JonathanM]

12 hours ago, SaberTreasures said:

Wondering if there is anyone out there that can help me understand why many torrent downloads will get to 90+% downloaded in binhex-delugevpn docker and then it will just stop.  Sometimes, it will start for a few minutes and then just stop forever.  Since it happens so frequently I'm assuming it's something on my part (settings or something) instead of just the seeds are low etc. For example, right now I have 50 stuck at 98%, and 50 stuck between 20-40% but then a new torrent coming on will start up perfectly fine for a while at least.  There are others that finish just fine though.    Any thoughts would be appreciated or if I can elaborate or provide anything to help.  If not, no worries!

Does your VPN support port forwarding, and is it working properly?

[SaberTreasures]

12 hours ago, JonathanM said:

Does your VPN support port forwarding, and is it working properly?

I am using PIA, I believe it does but am uncertain how to set it up exactly for deluge.

[JonathanM]

26 minutes ago, SaberTreasures said:

I am using PIA, I believe it does but am uncertain how to set it up exactly for deluge.

As long as you specify one of the port forwarding endpoints the setup is automatic.

 

Check the supervisord.log in the appdata folder for more info.

[luca2]

Hi, I am running this docker with PIA (openvpn) and I can download torrents but I cannot upload. I guess it has to do with my router blocking the uploads.

There are ports 58846, 58946, 8112 and 8118 from app to host as shown in the docker tab. Can anyone explain how they actually work?

I guess I need to add some rules to my firewall to let a port be forwarded to the wan (which one?).

Hope someone can help me out.

 

[JonathanM]

1 hour ago, luca2 said:

Hi, I am running this docker with PIA (openvpn) and I can download torrents but I cannot upload. I guess it has to do with my router blocking the uploads.

There are ports 58846, 58946, 8112 and 8118 from app to host as shown in the docker tab. Can anyone explain how they actually work?

I guess I need to add some rules to my firewall to let a port be forwarded to the wan (which one?).

Hope someone can help me out.

 

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

 

First see Q15, then work your way through from top to bottom.

[luca2]

6 hours ago, JonathanM said:

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

 

First see Q15, then work your way through from top to bottom.

Hi, everything seems to be working. I checked the supervisord.log and there is no error message.

How can I check for the upload?

[JonathanM]

2 minutes ago, luca2 said:

Hi, everything seems to be working. I checked the supervisord.log and there is no error message.

How can I check for the upload?

Try a different endpoint from the list of port forwarding addresses.

[SaberTreasures]

On 10/27/2023 at 6:49 PM, JonathanM said:

As long as you specify one of the port forwarding endpoints the setup is automatic.

 

Check the supervisord.log in the appdata folder for more info.

I checked the supervisord.log.  I am seeing alot of "Successfully assigned and bounce incoming port '#####'.  Is that what I should be seeing?  And if this does look like port forwarding is working properly, do you have any other potential suggestions to fix this problem?  Appreciate all of your time!

[Corneloues]

So got DelugeVPN back up and running.

 

I'm looking to route other containers through this one, but confused by the definitions of VPN_INPUT_PORTS and VPN_OUTPUT_PORTS...

 

The container I want to pass through, requires an external port opened. If I connect to PIA on the desktop to Berlin, I get a port back consistently, so assume this would be the same port I get when connecting via delugevpn.

 

I am adding the necessary port to VPN_OUTPUT_PORTS.

 

I've tried testing to see if the port is open as per the PIA FAQ's:
 

nc -l {PORT}
http://{VPN IP}:{PORT}

 

But I don't get the expected output back.

 

I haven't routed the container yet, just looking to make sure I have a port and it's open.

 

Am I missing something?

Edited October 29, 2023 by Corneloues

[humble-relocation2501]

Hi,

I have deluge-vpn working with PIA but yesterday at the bottom of the web ui it was showing my real ip instead of the VPN one.

Using  https://www.whatismyip.net/ it shows the VPN ip. Is it leaking traffic?

[binhex]

50 minutes ago, humble-relocation2501 said:

Hi,

I have deluge-vpn working with PIA but yesterday at the bottom of the web ui it was showing my real ip instead of the VPN one.

Using  https://www.whatismyip.net/ it shows the VPN ip. Is it leaking traffic?

do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

[binhex]

On 10/29/2023 at 10:17 PM, Corneloues said:

I'm looking to route other containers through this one, but confused by the definitions of VPN_INPUT_PORTS and VPN_OUTPUT_PORTS...

see here for the keys above:- https://github.com/binhex/documentation/blob/master/docker/guides/vpn.md

 

On 10/29/2023 at 10:17 PM, Corneloues said:

If I connect to PIA on the desktop to Berlin, I get a port back consistently, so assume this would be the same port I get when connecting via delugevpn.

No, the port you are seeing is a temporary incoming port assigned to that particular session, the other thing to note is that VPN_INPUT_PORT is NOT to be configured as an incoming ports for torrent clients, this can lead to ip leakages, see note in link above.

 

 I think what you are trying to achieve is covered in Q24:-https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

[MarianKoniuszko]

Hello @binhex. Today I noticed that my delugevpn dashboard is empty. Yesterday I set shares (smb) on my folder: `/media/videos` and `/media/torrents`.
I don;t change any permissions.
I noticed also that movies in emby don't work. I change ownership of folders to nobody and movies on emby works but delugevpn still empty. My other Deluge shows torrents and work OK. 
When I download torrent file and force recheck it don't see it and try to download again.
How can i fix that?



 

[humble-relocation2501]

10 hours ago, binhex said:

do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

I added the debug in the config and created the log and now it shows the vpn ip and see attached the log.

I also attached the older log and the screenshots from yesterday that you can see how it's showing my real ip but at the same time the torrent ip checker shows the vpn ip.  

both vpn connections are using the same server Montreal but computer and Synology show different vpn ip.

supervisord-backup.log supervisord.log

Edited November 1, 2023 by humble-relocation2501

[humble-relocation2501]

so I added a torrent and started downloading and then I could see how right away the ip changed to my ip.

but in whatsmyip it show the vpn ip.

do you need I add other logs?

[binhex]

6 hours ago, humble-relocation2501 said:

so I added a torrent and started downloading and then I could see how right away the ip changed to my ip.

where do you see this?, in deluge web ui? 

[binhex]

7 hours ago, humble-relocation2501 said:

so I added a torrent and started downloading and then I could see how right away the ip changed to my ip.

but in whatsmyip it show the vpn ip.

do you need I add other logs?

can you also post a screenshot of deluge web ui preferences/network

[humble-relocation2501]

37 minutes ago, binhex said:

can you also post a screenshot of deluge web ui preferences/network

here it is

[humble-relocation2501]

1 hour ago, binhex said:

where do you see this?, in deluge web ui? 

yes web ui ip at the bottom changes to my real ip, like you see in the other screenshots.

But ip in whatismyip.net is the vpn ip.

[binhex]

1 hour ago, humble-relocation2501 said:

yes web ui ip at the bottom changes to my real ip, like you see in the other screenshots.

But ip in whatismyip.net is the vpn ip.

This must be a bug with how deluge detects your external ip address, it is clearly bound to the vpn adapter (as shown in your last screenshot - wg0) and it is advertising your vpn ip, as shown by whatismyip.net, on top of this there are strict ip table rules in place to prevent ip laakage, so there is no way for deluge to connect to peers via your isp connection.

FYI i cannot replicate the bug on my system, are you running the latest image?.

[humble-relocation2501]

19 minutes ago, binhex said:

This must be a bug with how deluge detects your external ip address, it is clearly bound to the vpn adapter (as shown in your last screenshot - wg0) and it is advertising your vpn ip, as shown by whatismyip.net, on top of this there are strict ip table rules in place to prevent ip laakage, so there is no way for deluge to connect to peers via your isp connection.

FYI i cannot replicate the bug on my system, are you running the latest image?.

Yes, I'm using the latest image

[binhex]

11 hours ago, humble-relocation2501 said:

so I added a torrent and started downloading and then I could see how right away the ip changed to my ip.

but in whatsmyip it show the vpn ip.

do you need I add other logs?

If this is repeatable (which by the sound of the above it is), then restart the container, wait for the issue to occur and then docker exec inside the container and issue the following command which will reveal your external ip, it should be your vpn provider assigned ip:-
 

curl http://ifconfig.co

if it is your vpn provider ip then raise a bug with deluge, detail that you have the vpn provider adapter bound in deluge for 'outgoing interface' and the ip address of the vpn adapter defined for 'incoming address' yet the external ip address shown is your isp ip address and see what they say.

[Ginga_Ninge]

Have recently been trying to get DelugeVpn to work. Have run into the trouble of the WebUi not loading. I get the following. 
"ERR_CONNECTION_REFUSED on the webpage.

Have checked the log and im getting "WARNING: file 'credentials.conf' is group or others accessible"   Error. 
Have searched but and tried redoing the container setup. stil always with the same issue. Using PIA for my VPN service.  I just have no idea where its going wrong. Still learning.

 

log is as follows. 

 

2023-11-02 06:33:53,930 DEBG 'start-script' stdout output:
2023-11-02 06:33:53 TCP/UDP: Preserving recently used remote address: [AF_INET]146.70.38.37:1198
2023-11-02 06:33:53 UDPv4 link local: (not bound)
2023-11-02 06:33:53 UDPv4 link remote: [AF_INET]146.70.38.37:1198

2023-11-02 06:33:55,109 DEBG 'start-script' stdout output:
2023-11-02 06:33:55 [buenosaires407] Peer Connection Initiated with [AF_INET]146.70.38.37:1198

2023-11-02 06:33:56,461 DEBG 'start-script' stdout output:
2023-11-02 06:33:56 AUTH: Received control message: AUTH_FAILED

2023-11-02 06:33:56,462 DEBG 'start-script' stdout output:
2023-11-02 06:33:56 SIGTERM[soft,auth-failure] received, process exiting

2023-11-02 06:33:56,464 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2023-11-02 06:33:56,473 DEBG 'start-script' stdout output:
2023-11-02 06:33:56 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 

2023-11-02 06:33:56,473 DEBG 'start-script' stdout output:
2023-11-02 06:33:56 WARNING: file 'credentials.conf' is group or others accessible
2023-11-02 06:33:56 OpenVPN 2.6.6 [git:makepkg/c9540130121bfc21+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Aug 15 2023
2023-11-02 06:33:56 library versions: OpenSSL 3.1.3 19 Sep 2023, LZO 2.10
2023-11-02 06:33:56 DCO version: N/A

2023-11-02 06:33:56,474 DEBG 'start-script' stdout output:
2023-11-02 06:33:56 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-11-02 06:33:56,475 DEBG 'start-script' stdout output:
2023-11-02 06:33:56 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----
MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
-----END X509 CRL-----

2023-11-02 06:33:56,475 DEBG 'start-script' stdout output:
2023-11-02 06:33:56 TCP/UDP: Preserving recently used remote address: [AF_INET]172.64.151.73:1198

2023-11-02 06:33:56,475 DEBG 'start-script' stdout output:
2023-11-02 06:33:56 UDPv4 link local: (not bound)
2023-11-02 06:33:56 UDPv4 link remote: [AF_INET]172.64.151.73:1198
 

Halp please.

Edited November 2, 2023 by Ginga_Ninge
INformation

[humble-relocation2501]

11 hours ago, binhex said:

If this is repeatable (which by the sound of the above it is), then restart the container, wait for the issue to occur and then docker exec inside the container and issue the following command which will reveal your external ip, it should be your vpn provider assigned ip:-
 

curl http://ifconfig.co

if it is your vpn provider ip then raise a bug with deluge, detail that you have the vpn provider adapter bound in deluge for 'outgoing interface' and the ip address of the vpn adapter defined for 'incoming address' yet the external ip address shown is your isp ip address and see what they say.

still showing the private ip on the web ui, but run the command that you suggested inside the container and it shows the vpn ip.

Also checked https://iknowwhatyoudownload.com with vpn ip shows stuff I downloaded and it doesn't show anything with my ip.

So I'm 100% confident that there has not been an ip leak.

Thanks for your help!

I will post in deluge forum and will let you know about what they say.