On 6/5/2025 at 7:53 PM, H2OKing said:

That normally means there's a misconfiguration with the vpn. Does kill switch is kicking in so no traffic leaks

I've been struggling with a similar issue for several weeks, and have not been able to get anything resolved. I've just about given up at this point. No one even replied to the last time I posted my log and compose. :(

2 minutes ago, Elmojo said:

I've been struggling with a similar issue for several weeks, and have not been able to get anything resolved. I've just about given up at this point. No one even replied to the last time I posted my log and compose. :(

Can you bring me up to speed?

What vpn service? what Protocol? and share the Docker go when it prints. Make sure to sanitize credentials and personal info.

16 minutes ago, H2OKing said:

Can you bring me up to speed?

Not easily. lol

If you look back to page 179, about 1/4 down the page, on May 23, you'll see where I asked if we can circle back to my issue please.

After that is what's relevant.

Thanks for looking!

EDIT: Sorry, I was wrong, the latest stuff is towards the bottom of p 179. I sure wish this forum had post #s!

Edited June 7, 20251 yr by Elmojo

6 minutes ago, Elmojo said:

Not easily. lol

If you look back to page 179, about 1/4 down the page, on May 23, you'll see where I asked if we can circle back to my issue please.

After that is what's relevant.

Thanks for looking!

EDIT: Sorry, I was wrong, the latest stuff is towards the bottom of p 179. I sure wish this forum had post #s!

okay so your trying PIA wireguard.
when i was using them all i had to do.

  Key 1:

EditRemove
Container Variable: VPN_ENABLED="yes"



  Key 2:

EditRemove
Container Variable: VPN_USER="<VPN_USERNAME>"



  Key 3:

EditRemove
Container Variable: VPN_PASS="<VPN_PASSWORD>"



  Key 4:

piaairvpncustomEditRemove="pia"
Container Variable: VPN_PROV



  Key 5:

openvpnwireguardEditRemove="wireguard"
Container Variable: VPN_CLIENT

  Key 7:
Container Variable: STRICT_PORT_FORWARD="yes"

then it made this file.

root@UNRAID:~# cat /mnt/cache/appdata/binhex-qbittorrentvpn/wireguard/wg0.conf

[Interface]

PostUp = '/root/wireguardup.sh'

PostDown = '/root/wireguarddown.sh'

Address = 10.161.39.12/32

PrivateKey = Redacted=

MTU = 1440

DNS = 10.128.0.1

[Peer]

PublicKey = Redacted=

PresharedKey = Redacted=

Endpoint = us3.vpn.airdns.org:1637

AllowedIPs = 0.0.0.0/0

PersistentKeepalive = 15

then when qbittorrent starts up it list Available endpoints. i changed the default endpoint And restarted the container. I left pia due to throttling and then tried airvpn.

I agree. That's what it should be doing, but it's not.
When I start the container, it doesn't create the wg0.conf file, so it fails to connect, obviously.

I've tried a wipe and fresh install, and it does the same thing.

I just wiped it clean again and am trying a fresh install with pretty much stock variables...

Yep, same thing. The container starts without issue, and it creates the wireguard folder, but that folder remains empty. There is no wg0.conf file, and the log stalls at "[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'..."

4 minutes ago, Elmojo said:

Yep, same thing. The container starts without issue, and it creates the wireguard folder, but that folder remains empty. There is no wg0.conf file, and the log stalls at "[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'..."

that has me lost then. for airvpn i make config file from there site tool and just drop in the info to wg0.conf

6 minutes ago, Elmojo said:

Yep, same thing. The container starts without issue, and it creates the wireguard folder, but that folder remains empty. There is no wg0.conf file, and the log stalls at "[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'..."

Have you tried using OpenVPN rather than WireGuard?

1 minute ago, wgstarks said:

Have you tried using OpenVPN rather than WireGuard?

I have, but it's been a long time. i think with that you make the file and trop it in as well

27 minutes ago, wgstarks said:

Have you tried using OpenVPN rather than WireGuard?

Not recently. I wanted to use WG because @binhex said it didn't require any additional config, which sounded really good to me! Plus, I like the extra security and performance. :)

7 hours ago, Elmojo said:

it didn't require any additional config,

You just need to download a file from PIA and put it in the OpenVPN folder.

8 hours ago, Elmojo said:

I like the extra security and performance.

Not sure about extra security. AFAIK they both use OpenVPN under the hood.

4 minutes ago, wgstarks said:

AFAIK they both use OpenVPN under the hood.

Nope, Wireguard is its own thing, not linked to OpenVPN.

2 hours ago, wgstarks said:

You just need to download a file from PIA and put it in the OpenVPN folder.

Not sure about extra security. AFAIK they both use OpenVPN under the hood.

This isn't what Binhex said. He said (earlier in this thread) that using WG requires no additional config. PIA has no option for downloading any setup files. That's the whole issue. We've been over this at least 3 times already. Sorry if I sound frustrated, it's because I am. lol

35 minutes ago, Elmojo said:

He said (earlier in this thread) that using WG requires no additional config

correct, i am aware of your issue, in that you cannot connect to the PIA API in order to generate a valid wireguard config, i totally get it.

35 minutes ago, Elmojo said:

PIA has no option for downloading any setup files.

if you want to use openvpn (as wgstarks is reocmmending) then you have to manually download them from the PIA website, Please see Q7 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

6 minutes ago, binhex said:

correct, i am aware of your issue, in that you cannot connect to the PIA API in order to generate a valid wireguard config, i totally get it.

if you want to use openvpn (as wgstarks is reocmmending) then you have to manually download them from the PIA website, Please see Q7 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

I understand, but I do not want to use OpenVPN, I want to use WG. Are you saying that I need to use OpenVPN? I tried that in a previous troubleshooting step, and it didn't work either, though I can't recall right off hand how it failed.
The only way I've been able to get it working is to turn off the VPN entirely, then it works instantly, but that's obviously not an option long-term.

Okay... this is weird... I just went back and turned off the VPN to confirm that what I said above is accurate (it is), but now I see that there's a wg0.conf file in the wireguard directory. I wasn't there last night.
The supervisord.log still doesn't have a list of the available endpoints like it's supposed to, but something created that wg0 file...

However, when I start the container, it still sticks on that line about "trying to connect to the PIA wireguard API..."

Does any of this make any sort of sense to anyone?

EDIT: Does that wg0.conf look correct to you guys? It looks...incomplete to me.

Edited June 7, 20251 yr by Elmojo
added image

14 minutes ago, Elmojo said:

I understand, but I do not want to use OpenVPN, I want to use WG. Are you saying that I need to use OpenVPN? I tried that in a previous troubleshooting step, and it didn't work either, though I can't recall right off hand how it failed.

im saying lets try it as a debug step, right now i cannot replicate your issue (it simply works for me!) so im flying blind here, so lets try openvpn and see whether you get connected, FYI openvpn is NOT less secure, its just slightly slower (10-15% approx) than wireguard, on the plus side openvpn supports multi remote endpoints, so if one endpoint goes down openvpn will switch to the next (wireguard cannot do this).

15 minutes ago, Elmojo said:

EDIT: Does that wg0.conf look correct to you guys? It looks...incomplete to me.

it is not complete, the publickey has not been generated (as is reoported by your logs) so it won't work until you get a public key, and for whatever reason this is blocked on your home network.

Just posting here to say I have the exact same issues as ElMojo after following the reproduction steps outlined earlier. Thank you binhex for your help here, let me know if there is anything I can try to help diagnose the issue.

My wg0.conf file , located at "/mnt/user/appdata/binhex-qbittorrentvpn/wireguard" looks like this. It seems the difference from the above is that I actually get an private and public key generated. I no longer get connection refused on radar/lidarr for the port, but since the webgui is inaccessible, i can't tell if any radarr requested files are actually percolating to the qbittorrent image.

[Interface]

Address = XXXXXXXXXX

PrivateKey = XXXXXXXXX

PostUp = '/root/wireguardup.sh'

PostDown = '/root/wireguarddown.sh'

[Peer]

PublicKey = XXXXXXXXXX

AllowedIPs = 0.0.0.0/0

Endpoint = nl-amsterdam.privacy.network:1337

Edited June 8, 20251 yr by cambrionic
More information added

For testing, I went back and configured OpenVPN. The container will start, but I still can't access the webGUI.
Now that I look closer, I don't see where it's reporting a successful connection. What's the "all good, ready state" message look like?

Ah, it's still working, and taking a loooong time to connect. Maybe there's some issue with the way this container is trying to access the PIA API?
When I use the PIA desktop app (in a VM, for example), it connects almost instantly, so I don't think it's a VPN problem.

The log is posted below. I don't see any obvious errors (other than a few timeouts), but what do I know? ;)

supervisord.log

Edited June 8, 20251 yr by Elmojo
forgot to redact log

7 minutes ago, Elmojo said:

For testing, I went back and configured OpenVPN. The container will start, but I still can't access the webGUI.
Now that I look closer, I don't see where it's reporting a successful connection. What's the "all good, ready state" message look like?

Ah, it's still working, and taking a loooong time to connect. Maybe there's some issue with the way this container is trying to access the PIA API?
When I use the PIA desktop app (in a VM, for example), it connects almost instantly, so I don't think it's a VPN problem.

The log is posted below. I don't see any obvious errors (other than a few timeouts), but what do I know? ;)

supervisord.log

Mine typically takes about 90 seconds to start.

A successful start would show-

qbittorrent process listening on port 8080.

31 minutes ago, wgstarks said:

Mine typically takes about 90 seconds to start.

Really? Mine never did previously when it was working correctly.
In any ase, it's been like 40 minutes now, and it's still on that same line as shown in the log I posted above, so I think it's fair to say that it's not gonna connect.

That PIA endpoint API warning about server list being down seems kinda ominous as well...

Edited June 8, 20251 yr by Elmojo

14 hours ago, Elmojo said:

For testing, I went back and configured OpenVPN. The container will start, but I still can't access the webGUI.
Now that I look closer, I don't see where it's reporting a successful connection. What's the "all good, ready state" message look like?

Ah, it's still working, and taking a loooong time to connect. Maybe there's some issue with the way this container is trying to access the PIA API?
When I use the PIA desktop app (in a VM, for example), it connects almost instantly, so I don't think it's a VPN problem.

The log is posted below. I don't see any obvious errors (other than a few timeouts), but what do I know? ;)

supervisord.log

it appears that something is blocking on your network, from your log:-

2025-06-07 21:56:38 [UNDEF] Inactivity timeout (--ping-restart), restarting

And then eventually after multiple retries it gets connect to the endpoint:

[info] Successfully retrieved external IP address 140.228.21.163

But then fails to connect to PIA API to get a port forward:

PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check

I may of asked this before, excuse me if i have, but is there any pihole/pfsense/opnsense/adguard or similar running on your network that maybe blocking?, if so please do check the logs and configuration, it all points at something blocking to me.

Still not working for me with OpenVPN

But, wg worked fine after I enabled both proxy and shadosocks....Everything enabled.

Then, after a couple of restarts it worked and configured wg0.conf just fine.

Just to mention that I am behind a cgnat with a static ip at the end of my network for me!

And I work with macvlan as well. Recently changed for better dhcp compatibility in my network! I hope at least!

Edited June 8, 20251 yr by kolofotias