[Support] binhex - DelugeVPN


Recommended Posts

Posted (edited)

I seem to have lost access to the docker GUI and not sure how to resolve it.

 

Everything was working OK, but I recently got improved broadband so I was tweaking my preferences in the web GUI to reflect my better download/upload speeds.

I reloaded the page but now the web GUI won't load, and I'm not sure what to do to get it back. I tried restarting the docker and rebooted unraid to see if that resolved it but no dice.

 

The settings I changed in preferences were:

Network extras - just enabled DHT and Peer exchange

Bandwidth - changed max download and upload speeds; changed max hal-open connections

Queue - changed total active, total active downloading and total active seeding, enabled do not count slow torrents

 

That's it. I can't see how changing any of those would break it to the point I can't access the web GUI, so I can only assume it's just a coincidence and something else is afoot.

 

Can anyone help me get the web GUI back? TIA

 

EDIT: Thanks to Idaho121 below I know this is now a VPN issue associated with PIA not working

Edited by be4con
SOLVED
Link to comment

Everything was working fine until a few days ago. Then, Deluge stopped auto-loading/deleting torrent files from the relevant folder. Then, after I restarted to see if that would fix it, I can't get into the WebUI and I'm getting the following errors when loading:

 

2021-05-19 14:24:15 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.

 

[warn] Unable to successfully download PIA json to generate token from URL 'https://privateinternetaccess.com/gtoken/generateToken'
[info] 10 retries left
[info] Retrying in 10 secs...

 

I downloaded new files from PIA and have tried a few different of their endpoints that are on the list and that others who have had this issue noted as working.

 

Any thoughts on what else to try?

 

Thanks!

Link to comment
3 minutes ago, Idaho121 said:

Everything was working fine until a few days ago. Then, Deluge stopped auto-loading/deleting torrent files from the relevant folder. Then, after I restarted to see if that would fix it, I can't get into the WebUI and I'm getting the following errors when loading:

 

2021-05-19 14:24:15 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.

 

[warn] Unable to successfully download PIA json to generate token from URL 'https://privateinternetaccess.com/gtoken/generateToken'
[info] 10 retries left
[info] Retrying in 10 secs...

 

I downloaded new files from PIA and have tried a few different of their endpoints that are on the list and that others who have had this issue noted as working.

 

Any thoughts on what else to try?

 

Thanks!

Thanks! I just checked my log and I have the same error. Turned off the VPN and my web GUI is back - so mine was a PIA issue.

It looks like PIA is borked in the docker at the moment then

Link to comment

Hi, 

I am getting an error while trying to start the docker. 

image.png.674fa910dcc40a3efd84d2d2a6c2382a.png

I got this problem before but a reboot of the docker or even the complete system would restart it. Turning off the vpn starts the dockers. 

 

I use PIA and wireguard. It worked until a few hours ago and after I restarted my dockers it doesn't want to start. 

Starting the VPN client in Windows works just fine. 

Link to comment
On 5/17/2021 at 12:45 PM, Remamian said:

 

To add, the torrents DO show peers connecting, just no bandwidth being used. 

 

Reloaded all the PIA credentials, same thing. I did notice a behavior i had not witnessed before. That top torrent is seeding just fine right now, no issues, but the rest of them do not. I deleted all of those other ones and i am re-downloading but still wont seed

image.thumb.png.daba0c8689d27219c31d45a3d0195be3.png

 

The below info is for Windows 1809 All Versions. As you can see lots of connections but 0 upload, this is the same with all the 0 torrents. These are the top leecher torrents on IPTor so should be constantly being downloaded.

 

image.png.d8e44c53748beee7ba14778b603564b2.png

Link to comment

My delugevpn also seems to be down. Was working fine yesterday and there were no updates for the container either.

 

From the container log:

[warn] Unable to successfully download PIA json to generate token from URL 'https://privateinternetaccess.com/gtoken/generateToken'

 

I tried to hit the same PIA auth endpoint with basic authorization and I think that might be the problem. The endpoint is returning 500:

{
    "status": "ERROR",
    "message": "server error: all APIs down; please report bug"
}

 

I think it's an error on PIA's side. I'll email their support about the issue.

Link to comment
13 minutes ago, acii said:

My delugevpn also seems to be down. Was working fine yesterday and there were no updates for the container either.

 

From the container log:


[warn] Unable to successfully download PIA json to generate token from URL 'https://privateinternetaccess.com/gtoken/generateToken'

 

I tried to hit the same PIA auth endpoint with basic authorization and I think that might be the problem. The endpoint is returning 500:


{
    "status": "ERROR",
    "message": "server error: all APIs down; please report bug"
}

 

I think it's an error on PIA's side. I'll email their support about the issue.

I get that if i have STRICT_PORT_FORWARDING on, try turning if off?

Link to comment
2 hours ago, Remamian said:

I get that if i have STRICT_PORT_FORWARDING on, try turning if off?

Yup, turning off the STRICT_PORT_FORWARDING gets rid of that problem. However, I'd like to run the vpn with port forwarding. For now, I'll leave it off and check it later

Link to comment
13 hours ago, workermaster said:

Hi, 

I am getting an error while trying to start the docker. 

image.png.674fa910dcc40a3efd84d2d2a6c2382a.png

I got this problem before but a reboot of the docker or even the complete system would restart it. Turning off the vpn starts the dockers. 

 

I use PIA and wireguard. It worked until a few hours ago and after I restarted my dockers it doesn't want to start. 

Starting the VPN client in Windows works just fine. 

 

12 hours ago, Dees said:

Same error for me.  Following thread for a solution.  

 

12 hours ago, Marlat said:

Same error for me!

 

11 hours ago, acii said:

My delugevpn also seems to be down. Was working fine yesterday and there were no updates for the container either.

 

From the container log:



[warn] Unable to successfully download PIA json to generate token from URL 'https://privateinternetaccess.com/gtoken/generateToken'

 

I tried to hit the same PIA auth endpoint with basic authorization and I think that might be the problem. The endpoint is returning 500:



{
    "status": "ERROR",
    "message": "server error: all APIs down; please report bug"
}

 

I think it's an error on PIA's side. I'll email their support about the issue.

this is 100% a PIA issue, people on the SABnzbdvpn thread have JUST tried it again and confirmed its now working, so give the container a restart and see what you get now.

 

edit - works for me on a restart, connected to netherlands via wireguard.

  • Like 1
Link to comment
Posted (edited)

Working for me now.

 

Does anyone know of a port checker plugin/dockerfor checking to see if the forwarded port is open?

 

EDIT - answer to my question for anyone else that's interested - ipleak.net has a magnet link which checks the deluge client for the IP address and port, so there is no need for an Unraid based solution.

Edited by be4con
SOLVED
  • Like 1
Link to comment
Posted (edited)
On 5/19/2021 at 4:24 PM, Remamian said:

 

Reloaded all the PIA credentials, same thing. I did notice a behavior i had not witnessed before. That top torrent is seeding just fine right now, no issues, but the rest of them do not. I deleted all of those other ones and i am re-downloading but still wont seed

image.thumb.png.daba0c8689d27219c31d45a3d0195be3.png

 

The below info is for Windows 1809 All Versions. As you can see lots of connections but 0 upload, this is the same with all the 0 torrents. These are the top leecher torrents on IPTor so should be constantly being downloaded.

 

image.png.d8e44c53748beee7ba14778b603564b2.png

 

So i grabbed a new top seeded thing that i have not downloaded in the past and its also seeding properly. Maybe there is a cached thing with these old ones thats keeping them from seeding properly. Is there some way to i dunno 'clear cache' of deluge?

 

EDIT: I completely uninstalled deluge, deleted app data and reinstalled from scratch. Redownloaded the above torrents and they are doing the same thing. Peers will connect but uploading is not happening... 

Edited by Remamian
Link to comment
22 hours ago, binhex said:

this is 100% a PIA issue, people on the SABnzbdvpn thread have JUST tried it again and confirmed its now working, so give the container a restart and see what you get now.

 

edit - works for me on a restart, connected to netherlands via wireguard.

I'm having no luck whatsoever. I know there's been PIA issues in the past so I even gave AirVPN a shot, to no avail.

Setting port forwarding to 'no' also hasn't helped me to getting the Web UI working.
For now I guess I'm not downloading torrents or using my VPN through any containers.
 

Link to comment

Does anyone know of a way I can propagate port changes in the docker back to my router so I don't have to do it manually to maintain port forwarding with PIA?

 

I'm running an ASUS AC86U with Merlin firmware. TIA

Link to comment
7 minutes ago, be4con said:

Does anyone know of a way I can propagate port changes in the docker back to my router so I don't have to do it manually to maintain port forwarding with PIA?

 

I'm running an ASUS AC86U with Merlin firmware. TIA

If you are correctly using a VPN tunnel, the WAN IP and ports on your router don't apply. They simply aren't used. At all.

 

This container if working properly does all the needed port forwarding and updating that is needed.

Link to comment
Posted (edited)
26 minutes ago, jonathanm said:

If you are correctly using a VPN tunnel, the WAN IP and ports on your router don't apply. They simply aren't used. At all.

 

This container if working properly does all the needed port forwarding and updating that is needed.

That's interesting, because unless I manually forward the port on my router it shows as closed.


What do you mean by 'correctly using'?

 

The container works fine, the log shows connected to PIA and gives a port which it maintains. As far as I can tell the VPN function is working OK - how else would I check it?

Edited by be4con
further question
Link to comment
On 5/20/2021 at 10:06 AM, binhex said:

 

 

 

this is 100% a PIA issue, people on the SABnzbdvpn thread have JUST tried it again and confirmed its now working, so give the container a restart and see what you get now.

 

edit - works for me on a restart, connected to netherlands via wireguard.

Worked again after a few hours. I have no idea why. Thanks for your reply. 

Link to comment
Posted (edited)

Hey! So recently I just started having issues with my Deluge container running on a Synology DS918+, it just keeps restarting and I cant' access the web gui.

I'm using Torguard as VPN-provider.


My Enviroment settings look like this.

Could be that it started when I updated my Synology, perhaps it changed something?


I've tried deleting the container and recreated it, didn't help.

 

image.thumb.png.6a73fb7686d3d9c535848bf82eafc314.png

 

image.thumb.png.7ee4bb42ae0321b9b5cfce9bb17c2b7f.png 

Edited by e2zippo
Link to comment

I've just set up a trial for PIA and wondering if I should be using OPENVPN 2.4 or '2.3 and earlier'. Also curious about the fact that OPENVPN files are TCP but the app (running in KALI) uses UDP. Not an expert on protocols but wondering why this might be ?

Link to comment
On 5/23/2021 at 6:01 PM, e2zippo said:

Hey! So recently I just started having issues with my Deluge container running on a Synology DS918+, it just keeps restarting and I cant' access the web gui.

I'm using Torguard as VPN-provider.


My Enviroment settings look like this.

Could be that it started when I updated my Synology, perhaps it changed something?


I've tried deleting the container and recreated it, didn't help.

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

Link to comment
22 hours ago, Philby1975 said:

I've just set up a trial for PIA and wondering if I should be using OPENVPN 2.4 or '2.3 and earlier'. Also curious about the fact that OPENVPN files are TCP but the app (running in KALI) uses UDP. Not an expert on protocols but wondering why this might be ?

Been years since I was using PIA, but maybe I can answer you anyway. Always use the most recent version of any software unless it for some reason gives you issues. PIA have .ovpn files for both TCP and UDP (at least they used to when I was using them). Use UDP if you can, as that is the fastest protocol.

  • Thanks 1
Link to comment

So I am not able to get torguard working via wireguard.

I have generated a known good config that works on my phone via lte and on my desktop.

 

It does not work with this docker however.

Watching the log in debug mode it reads "Having issues resolving name 'www.google.com'"

Keeps trying for x times then just fails.

Connecting to the console of this docker, I cannot ping the dns and thus cant get any name resolution.

At this point it attempts to get the vpn public IP but fails as it can resolve any address.

 

Thus far I've completely removed docker and reinstalled it, completely removed deluge and reinstalled it...

Any ideas of what I can try?

Link to comment
On 5/21/2021 at 9:02 PM, be4con said:

That's interesting, because unless I manually forward the port on my router it shows as closed.


What do you mean by 'correctly using'?

 

The container works fine, the log shows connected to PIA and gives a port which it maintains. As far as I can tell the VPN function is working OK - how else would I check it?

Just bumping this as I am still confused by this an hoping someone can help.

If I don't port forward on my router then the port shows as closed and I am not connectable on the tracker. What am I doing wrong if port forwarding on my router isn't needed?

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.