8 minutes ago, Big Dan T said:

Hi All,

 

Is PIA down for everyone else too ?

 

I keep getting:-

 

 

Yah,  I am getting this also.

10 minutes ago, Big Dan T said:

Hi All,

 

Is PIA down for everyone else too ?

 

I keep getting:-

 

 

Nope.  Working fine for me.  I am using one of the CA endpoints FYI.

12 minutes ago, Big Dan T said:

Hi All,

 

Is PIA down for everyone else too ?

 

I keep getting:-

 

 

Some of @binhex’s other dockers are also suffering from the same issue with PIA. I think that this error will only effect someone trying to start/restart the docker. It does seem to be wide spread though.

I wonder if it is just a wireguard issue. I am going to try using ovpn and see what happens

4 minutes ago, scottc said:

I wonder if it is just a wireguard issue. I am going to try using ovpn and see what happens

It’s an issue with the PIA server that issues the tokens used to validate connections to the servers. It’s either down or has changed urls.

26 minutes ago, Big Dan T said:

Hi All,

 

Is PIA down for everyone else too ?

 

Same here, as soon as I restarted the container this morning, won't finish connecting to https://privateinternetaccess.com/gtoken/generateToken

I just restarted mine again and it is finally fully connected and working  

so there was an issue in the PIA Network

2 minutes ago, reftek said:

so there was an issue in the PIA Network

Yes

Yup, mines just woken up too !!

Hi,

 

I have a VPN setup on my UniFi Dream Machine and I am unable to load DelugeVPN WebUI. When I'm at home, everything works just fine obviously but when connected over the VPN for some reason i cannot access DelugeVPN. I am able to access Sonarr, Radarr and Prowlarr's WebUI no Problem.

 

According to another post i made, a comment was to add my VPN subnet into the list of allowed addresses, how do i do that?

Edited November 15, 20214 yr by JosephStyles

Everything works fine until I attempt to turn on my router NordVPN. I realize that it will be a double VPN situation. Is there a way to allow this container to utilize the WAN interface on PFSense, instead of the NordVPN interface? 

On 11/15/2021 at 9:55 PM, JosephStyles said:

According to another post i made, a comment was to add my VPN subnet into the list of allowed addresses, how do i do that?

https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=1005634

 

I noticed today that deluge had updated and now the web interface won't load. Any thoughts on how I can troubleshoot this? I can't make sense of the logs, but it looks fine to me.

4 minutes ago, LittleMike said:

I noticed today that deluge had updated and now the web interface won't load. Any thoughts on how I can troubleshoot this? I can't make sense of the logs, but it looks fine to me.

Attach your supervisord log to your next post after redacting user/password info.

11 minutes ago, wgstarks said:

Attach your supervisord log to your next post after redacting user/password info.

I don't even see a username or password in that log file. I do see some failed auth errors though. Think it's okay to still post it raw or should I dig deeper?

13 minutes ago, LittleMike said:

I do see some failed auth errors though.

That would be the first thing to fix.

8 minutes ago, JonathanM said:

That would be the first thing to fix.

I would if it gave any indication as to what it's failing auth on:
 

2021-11-17 20:49:21,991 DEBG 'start-script' stdout output:
2021-11-17 20:49:21 AUTH: Received control message: AUTH_FAILED

 

14 minutes ago, LittleMike said:

I would if it gave any indication as to what it's failing auth on:
 

2021-11-17 20:49:21,991 DEBG 'start-script' stdout output:
2021-11-17 20:49:21 AUTH: Received control message: AUTH_FAILED

 

Your VPN login credentials.

5 minutes ago, JonathanM said:

Your VPN login credentials.

Okay, good. That's a starting point. Though I'm at a loss as to how that could be because nothing has changed on my end other than the container updated.

*EDIT* That did it @JonathanM! All I did was go back to the container, put in my username and password (I noticed it was the older style one that PIA used) and then the UI came back up after a couple of minutes. Thank you.

 

So next question is, what does the webui have to do with a wrong username/password for a VPN provider? Technically the container should still start, no?

Edited November 18, 20214 yr by LittleMike

8 hours ago, LittleMike said:

Technically the container should still start, no?

No.

It's the safety system to keep you from leaking sensitive info. No VPN, no app. It's in the container docs, and mentioned countless times in this thread.

On 10/2/2021 at 11:44 AM, frodr said:

Q6A:

Q21. I now see that you support WireGuard, how do i switch from OpenVPN to WireGuard client?

A21. Yes you are correct, all binhex VPN created images now support OpenVPN and WireGuard, for PIA and other VPN providers.

If you're a PIA user then please follow this procedure:-

Change Docker parameter from --cap-add=NET_ADMIN to --privileged=true (WireGuard requires privileged permissions).

 

 

Where in binhex-delugevpn do I find --cap-add=NET_ADMIN? This is what I see:

 

 

 

// Frode

 

Hi, were you able to find the solution? I couldn't find "--cap-add=NET_ADMIN" either, and I have nothing in "Extra Parameters".

All I did was make sure the box for "Privileged" was checked, and then followed the rest of A21 instructions. It's working now. Hope that helps.

Also trying to migrate to Wireguard.  Except when I follow the directions with wg0.conf is not generated at start up.  Just get an empty folder.  

 

 

Edited November 20, 20214 yr by Flyinace2000

2 hours ago, Flyinace2000 said:

Also trying to migrate to Wireguard.  Except when I follow the directions with wg0.conf is not generated at start up.  Just get an empty folder.  

 

 

 

 

Say it with me everyone, it's always DNS.  Removed all the DNS Servers from the docker settings except for cloud flair and (for some reason) my routerIP (not my DNS server).  Restarted and it worked.  

 

My router is an OpenSense box running Adguard.  

 

Either way, up and running.

 
Say it with me everyone, it's always DNS.  Removed all the DNS Servers from the docker settings except for cloud flair and (for some reason) my routerIP (not my DNS server).  Restarted and it worked.  
 
My router is an OpenSense box running Adguard.  
 
Either way, up and running.

Yes the issue was with pia DNS which has sadly stopped working, so removing pia DNS from the list will get you going again.

Sent from my CLT-L09 using Tapatalk