5 hours ago, binhex said:

Tailscale messes with DNS causing name lookup failure, you cannot use it with this container, Please see Q36 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Ah I see. I indeed have MagicDNS enabled, TAILSCALE_USERSPACE_NETWORKING is already set to FALSE. So MagicDNS is probably my issue then.

 

I have lots of containers like radarr.my-tsname.ts.net, sonarr.my-tsname.ts.net, etc for which I would like to keep using MagicDNS

 

Edit: I see here https://tailscale.com/kb/1235/resolv-conf that:

Quote

you can either disable MagicDNS for all devices in your tailnet or run tailscale set --accept-dns=false to disable MagicDNS on a single device.

So it should be possible to only disable MagicDNS for the qBittorrent container, right? Would I just run this command

tailscale set --accept-dns=false

in the console window of the binhex-qbittorrent container?

 

Edit2: I believe I've done it, by adding the parameter 

--accept-dns=false

 

to the Extra Parameters field:

 

For some reason I can now connect to it using the MagicDNS address, but not the IPv4 address. I was expecting it to be the other way around. Maybe it has to do with the HTTPS certificate I put in place. Anyways, I think this does the job.

Edited April 22, 20251 yr by PaulieW

Ok, I was not sure whats cause and whats just a resulting problem. I'll take a deeper look at that. Thanks

Hey Binhex! I've recently switched from Windscribe to Proton and how I can't get my WebUI to open. I've removed & added the ports per the FAQ on Github, but I'm not getting any success getting the WebUI to open. Are there logs I can gather & share to make this easier?

I recently just swapped over to PIA from Mullvad and I have it set up for the most part in the qbittorrent-vpn container and after watching a video I was able to update the wg0.conf so that I was no longer connecting to nl-amserdam. I was watching a video and they swapped to ca-toronto.privacy.network:1337 which seems to work for me too.

However, my question, is there a convenient list of this endpoint addresses that are available to use with wireguard? Or is the standard "country-city.privacy.network:1337"? Also I see that not all these endpoints support port forwarding but based in the log I can see that the toronto endpoint I am using currently does support it.

 

I tried searching through this long forum post for answers but wasn't having much luck. I really enjoy this container and all the support there is for it.

Any advice is greatly appreciated!

Is anybody having issues with files only saving straight to the array disk one no matter what you do with data location set to?

Hi - 

 

You may or may not be aware that a not insignificant portion of your user base use trackers that heavily restrict the specific versions of clients they allow to connect (applies to any torrent client, not just qbit, so the following feedback applies to all the clients you distribute).  Most that I'm aware of have blanket approvals for qBit 5.0.x, but the recently released 5.1.x remains verboten. 

 

With the information available in the Unraid update UI, I have no idea of accepting the update will break my ability to connect to such trackers.  

 

I would ask at a minimum that you include a changelog that includes the specific version of the given torrent client contained therein.  

 

My personal sanity would ask that you provide a docker tag for at least for each major/minor version (e.g., an update channel each for 5.0.x and 5.1.x in the case of qbit) so that I don't have to ignore an update until all my trackers support that version.  

5 hours ago, dmw_chef said:

With the information available in the Unraid update UI, I have no idea of accepting the update will break my ability to connect to such trackers. 

The tags i use should give you the information you require, the tag format is <app version>--<upstream build number>-<my build number>, so for example '5.1.0-01-01' means app version v5.1.0, upstream build 01,  my build 01.

Tags can be found for every image at docker hub:- https://hub.docker.com/r/binhex/arch-qbittorrentvpn/tags

 

5 hours ago, dmw_chef said:

My personal sanity would ask that you provide a docker tag for at least for each major/minor version (e.g., an update channel each for 5.0.x and 5.1.x in the case of qbit) so that I don't have to ignore an update until all my trackers support that version.  

Or alternatively don't use 'latest' and instead use the specific version tags shown in the link above, adding in automated tagging for major-minor versions is tricky as i would need to cover all different version schemes for all the applications i support (60+), it's possible but its work.

 

p.s. 5.1.0 has literally just been built, so if your tracker has not ok'd that version then do NOT update at this time.

Hi,

Would like to run a second instance of the docker binhex-readarr.  My first one is running happily through the binhex-qbittorrentvpn.  I see in the FAQ for this forum that web interface must have a different port number.  by default its on 8787 from memory.  What do i need to tweak in the docker and also the binhex-qbittorrentvpn to get the web interface to work.

 

Thanks,

Dwarfboysim

 

Seem to have a random issue where my downloading torrents show up for a few seconds after I refresh the browser and then disappear.

They are still there downloading - but just disappear. Whatever filter on the left column I hit nothing shows unless I refresh.

I uninstalled and reinstalled and seems to have fixed it!

@binhex Is it seriously too much to ask that the client version included in the image be in the update changelog?

Edited April 30, 20251 yr by dmw_chef
me fail english, that's unpossible

8 hours ago, leejbarker said:

I uninstalled and reinstalled and seems to have fixed it!

Same issue.

3 hours ago, dmw_chef said:

@binhex Is it seriously too much to ask that the client version included in the image be in the update changelog?

Is it seriously too much to ask for you to click on a single link to view the version before upgrading? if i programmatically generated a changelog it would consist of the same information as the tag, plus any commits (of which the vast majority of the time there will be none), what benefit is that?, do keep in mind I have 60+ repositories to support here, and what you might think is a trivial change is not for me.

EDIT - I will see how tricky it is to create versioned tags as I do see the benefit in this.

On 4/28/2025 at 9:43 AM, Dwarfboysim said:

Hi,

Would like to run a second instance of the docker binhex-readarr.  My first one is running happily through the binhex-qbittorrentvpn.  I see in the FAQ for this forum that web interface must have a different port number.  by default its on 8787 from memory.  What do i need to tweak in the docker and also the binhex-qbittorrentvpn to get the web interface to work.

 

Thanks,

Dwarfboysim

 

You would need to avoid any host port clashes, so yes different ports will be required, you will also need to have a different host path for /config, on top of that you will need to use a different browser for the different containers, this is due to qbittorrent cookies related issues.

After updating I can no longer see torrents listed in the web gui on Firefox. If I switch over to Chrome I can see them. I tried clearing cookies on Firefox and restarting the container, but those didn't seem to work. Any advice?

Edited April 30, 20251 yr by pantsonadog
Typo

10 hours ago, pantsonadog said:

After updating I can no longer see torrents listed in the web gui on Firefox. If I switch over to Chrome I can see them. I tried clearing cookies on Firefox and restarting the container, but those didn't seem to work. Any advice?

Came to ask the same question. Torrents were not showing in Chrome. Tried Edge and Firefox and both working. Was able to get Chrome working by following these steps

To clear the cache for a specific website in Google Chrome, navigate to the website, open Developer Tools (F12), go to the "Application" tab, select "Storage", and then click "Clear site data"

 

In Firefox try (ctrl + shift + i) then "storage" then on the left you can delete Cache Storage for each catagory.

Edited May 1, 20251 yr by Merkas

Is there a way to create a torrent from within this container? It seems to be missing some options that the "normal" version has on my personal computer.

No, the container version doesn't have the torrent creator

7 hours ago, domrego said:

Is there a way to create a torrent from within this container? It seems to be missing some options that the "normal" version has on my personal computer.

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/page/177/#findComment-1546747

 

13 hours ago, binhex said:

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/page/177/#findComment-1546747

 

Essentially, use a different torrent client if I want to do this? Just want to make sure i'm not misunderstanding lol

2 hours ago, domrego said:

Essentially, use a different torrent client if I want to do this? Just want to make sure i'm not misunderstanding lol

I'm dumb, I'm seeing now that this is like a skin, and the alternate UI has the ability to create a torrent

On 4/30/2025 at 8:33 AM, binhex said:

EDIT - I will see how tricky it is to create versioned tags as I do see the benefit in this.

This has now been implemented:- 

 

 

Wanna see if anyone is having an issue using the new feature in 5.1.0 'FEATURE: Display External IP Address in status bar'

When I start up the container, it will show the PIA VPN IP address that I'm using but than a few minutes later it will change and show my real External IP address.  That shouldn't be happening, right?

Edited May 6, 20251 yr by ibmsynchronous

somehow i have messed up DNS for this after setting up local DNS in my pihole and nginx. all my other container apps went fine (just added local DNS entry on pihole and proxy hosts in nginx), then i repeated the same thing for this one and after restarting the image initially the wg0 interface would not come up at all.  I tried un-doing all of the DNS changes I made for this container - deleted entries on pihole and nginx, and deleted/reinstalled the image via template. Also have gotten a completely fresh wg0.conf from VPN provider (mullvad). Now the interface comes up and web gui is accessible, but it is not able to resolve www.google.com and there is no external traffic obviously.  If I disable the VPN everything works just fine.

 

Do I need to just undo ALL of the local DNS stuff I did in pihole and nginx?

 

Any help would be greatly appreciated!

 

edit:

 

whelp... after all that i finally realized my mullvad subscription just happened to run out exactly at the wrong time.  so apparently it's NOT always DNS lol.

Edited May 7, 20251 yr by acosmichippo
attached log

Hi all,

Been away for a bit (wife is in the hospital recovering from cancer surgery), and when I came back, I noticed that qBT is inaccessible.  I seem to recall something happening once before where the PIA cert got borked or similar.  I'm sorry I don't have time to do extensive searching, as I have to be back at the hospital shortly.  Can anyone point me to what may be the cause?
I'm using PIA VPN, and when I try to access the qBT web GUI, either with my normal saved bookmark (previously working) or via the "webUI" option from within unraid dashboard, I get the same error: 

This site can’t be reached

192.168.11.XXX refused to connect. 

 

Any help appreciated.  Normally I'd try to track this down myself, but I'm a bit scrambled right now.  I'd like to have things up and running before she gets home, since she will have lots of 'TV time' while she recovers.

 

EDIT:  So I'm back home now, and had time to scan back a few pages.  It seems that several others are having a similar sudden issue of not being able to connect to the UI, but I don't see any solutions.
I pulled my logs, and see what's posted below.  I'm not good at deciphering these, but I definitely see some issues with connecting to WG.  Absolutely nothing has changed with by network or unraid/docker config, since I've been away for 8 days, and it was working before I left. 

I know it's not just a UI issue, since Sonarr is reporting that it's not able to reach qBT either.

 Logs:

text  error  warn  system  array  login  

-A OUTPUT -o eth0 -p tcp -m tcp --sport 45206 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 45206 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o wg0 -j ACCEPT

2025-05-07 16:27:32,566 DEBG 'start-script' stdout output:
--------------------

2025-05-07 16:27:32,572 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2025-05-07 16:27:32,845 DEBG 'start-script' stdout output:
[info] Token generated for PIA wireguard authentication

2025-05-07 16:27:32,854 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'greenland.privacy.network'...

2025-05-07 16:32:33,286 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2025-05-07 16:32:33,315 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2025-05-07 16:32:33,338 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2025-05-07 16:32:33,344 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2025-05-07 16:32:33,346 DEBG 'start-script' stderr output:
Line unrecognized: `PublicKey='
Configuration parsing error

2025-05-07 16:32:33,352 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2025-05-07 16:32:33,410 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

2025-05-07 16:33:03,418 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2025-05-07 16:33:03,646 DEBG 'start-script' stdout output:
[info] Token generated for PIA wireguard authentication

2025-05-07 16:33:03,655 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'greenland.privacy.network'...

2025-05-07 16:37:40,993 INFO reaped unknown pid 54 (terminated by SIGTERM)
2025-05-07 16:37:40,993 WARN received SIGTERM indicating exit request
2025-05-07 16:37:40,994 DEBG killing watchdog-script (pid 362) with signal SIGTERM
2025-05-07 16:37:40,994 INFO waiting for start-script, watchdog-script to die
2025-05-07 16:37:40,996 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22626366230672 for <Subprocess at 22626381006160 with name watchdog-script in state STOPPING> (stdout)>
2025-05-07 16:37:40,996 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22626365868192 for <Subprocess at 22626381006160 with name watchdog-script in state STOPPING> (stderr)>
2025-05-07 16:37:40,996 WARN stopped: watchdog-script (exit status 143)
2025-05-07 16:37:40,997 DEBG received SIGCHLD indicating a child quit
2025-05-07 16:37:40,997 DEBG killing start-script (pid 361) with signal SIGTERM
2025-05-07 16:37:40,998 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22626367780048 for <Subprocess at 22626367776016 with name start-script in state STOPPING> (stdout)>
2025-05-07 16:37:40,999 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22626366229712 for <Subprocess at 22626367776016 with name start-script in state STOPPING> (stderr)>
2025-05-07 16:37:40,999 WARN stopped: start-script (terminated by SIGTERM)
2025-05-07 16:37:41,000 DEBG received SIGCHLD indicating a child quit
Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2025-05-07 16:37:46.494736 [info] Host is running unRAID
2025-05-07 16:37:46.564660 [info] System information: Linux a7bf00c800fa 6.1.74-Unraid #1 SMP PREEMPT_DYNAMIC Fri Feb  2 11:06:32 PST 2024 x86_64 GNU/Linux
2025-05-07 16:37:46.645853 [info] Image tags: BASE_RELEASE_TAG=2025042801,INT_RELEASE_TAG=2025042801,IMAGE_RELEASE_TAG=5.1.0-1-01
2025-05-07 16:37:46.727980 [info] PUID defined as '1001'
2025-05-07 16:37:46.811201 [info] PGID defined as '100'
2025-05-07 16:37:46.938133 [info] UMASK defined as '000'
2025-05-07 16:37:47.013407 [info] Permissions already set for '/config'
2025-05-07 16:37:47.095606 [info] Deleting files in /tmp (non recursive)...
2025-05-07 16:37:47.187587 [info] VPN_ENABLED defined as 'yes'
2025-05-07 16:37:47.271169 [info] VPN_CLIENT defined as 'wireguard'
2025-05-07 16:37:47.351913 [info] VPN_PROV defined as 'pia'
2025-05-07 16:37:47.448677 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2025-05-07 16:37:47.550783 [info] VPN_REMOTE_SERVER defined as 'greenland.privacy.network'
2025-05-07 16:37:47.627768 [info] VPN_REMOTE_PORT defined as '1337'
2025-05-07 16:37:47.702727 [info] VPN_DEVICE_TYPE defined as 'wg0'
2025-05-07 16:37:47.771075 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2025-05-07 16:37:47.849975 [info] USERSPACE_WIREGUARD not defined (via -e USERSPACE_WIREGUARD), defaulting to 'no'
2025-05-07 16:37:47.925217 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
2025-05-07 16:37:49.093089 [info] LAN_NETWORK defined as '192.168.11.0/24'
2025-05-07 16:37:49.184215 [info] LAN_NETWORK exported as '192.168.11.0/24'
2025-05-07 16:37:49.261568 [info] VPN_USER defined as 'xxx'
2025-05-07 16:37:49.340011 [info] VPN_PASS defined as 'xxx'
2025-05-07 16:37:49.422404 [info] STRICT_PORT_FORWARD defined as 'yes'
2025-05-07 16:37:49.504381 [info] VPN_INPUT_PORTS defined as 'xxxxxx'
2025-05-07 16:37:49.584865 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2025-05-07 16:37:49.659966 [info] ENABLE_STARTUP_SCRIPTS not defined (via -e ENABLE_STARTUP_SCRIPTS), defaulting to 'no'
2025-05-07 16:37:49.739527 [warn] ENABLE_SOCKS not defined (via -e ENABLE_SOCKS), defaulting to 'no'
2025-05-07 16:37:49.816178 [info] ENABLE_PRIVOXY defined as 'no'
2025-05-07 16:37:49.901452 [info] WEBUI_PORT defined as '8080'
2025-05-07 16:37:49.996279 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2025-05-07 16:37:50.071687 [info] Starting Supervisor...
2025-05-07 16:37:50,584 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2025-05-07 16:37:50,585 INFO Set uid to user 0 succeeded
2025-05-07 16:37:50,593 INFO supervisord started with pid 7
2025-05-07 16:37:51,598 INFO spawned: 'start-script' with pid 361
2025-05-07 16:37:51,602 INFO spawned: 'watchdog-script' with pid 362
2025-05-07 16:37:51,604 INFO reaped unknown pid 8 (exit status 0)
2025-05-07 16:37:51,608 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2025-05-07 16:37:51,609 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-05-07 16:37:51,609 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-05-07 16:37:52,145 DEBG 'start-script' stdout output:
[info] Adding 192.168.11.0/24 as route via adapter eth0

2025-05-07 16:37:52,149 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2025-05-07 16:37:52,153 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0 
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7 
192.168.11.0/24 via 172.17.0.1 dev eth0 

2025-05-07 16:37:52,153 DEBG 'start-script' stdout output:
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 
local 172.17.0.7 dev eth0 table local proto kernel scope host src 172.17.0.7 
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.7 

2025-05-07 16:37:52,154 DEBG 'start-script' stdout output:
--------------------

2025-05-07 16:37:52,166 DEBG 'start-script' stdout output:
iptable_mangle         16384  2
ip_tables              28672  6 iptable_filter,iptable_raw,iptable_nat,iptable_mangle
x_tables               45056  19 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,xt_comment,ip6_tables,ipt_REJECT,xt_connmark,iptable_raw,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2025-05-07 16:37:52,167 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2025-05-07 16:37:52,450 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2025-05-07 16:37:52,454 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 91.90.120.144/32 -i eth0 -j ACCEPT
-A INPUT -s 91.90.120.138/32 -i eth0 -j ACCEPT
-A INPUT -s 91.90.120.136/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.40.93/32 -i eth0 -j ACCEPT
-A INPUT -s 172.64.147.163/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.159.201/32 -i eth0 -j ACCEPT
-A INPUT -s 104.19.240.167/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 91.90.120.144/32 -i eth0 -j ACCEPT
-A INPUT -s 91.90.120.138/32 -i eth0 -j ACCEPT
-A INPUT -s 91.90.120.136/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.40.93/32 -i eth0 -j ACCEPT
-A INPUT -s 172.64.147.163/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.159.201/32 -i eth0 -j ACCEPT
-A INPUT -s 104.19.240.167/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 45206 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 45206 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -j ACCEPT
-A OUTPUT -d 91.90.120.144/32 -o eth0 -j ACCEPT
-A OUTPUT -d 91.90.120.138/32 -o eth0 -j ACCEPT
-A OUTPUT -d 91.90.120.136/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.40.93/32 -o eth0 -j ACCEPT
-A OUTPUT -d 172.64.147.163/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.159.201/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 91.90.120.144/32 -o eth0 -j ACCEPT
-A OUTPUT -d 91.90.120.138/32 -o eth0 -j ACCEPT
-A OUTPUT -d 91.90.120.136/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.40.93/32 -o eth0 -j ACCEPT
-A OUTPUT -d 172.64.147.163/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.159.201/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.19.240.167/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 45206 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 45206 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o wg0 -j ACCEPT

2025-05-07 16:37:52,457 DEBG 'start-script' stdout output:
--------------------

2025-05-07 16:37:52,461 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2025-05-07 16:37:52,692 DEBG 'start-script' stdout output:
[info] Token generated for PIA wireguard authentication

2025-05-07 16:37:52,702 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'greenland.privacy.network'...

 

In the logs, I see multiple entries of "Line unrecognized:  `PublicKey=' Configuration parsing error".
When I check wg.conf, the "Publickey" entry is indeed blank.  In the example on the github FAQ page, it's populated.  Could this be the issue?
The FAQ page also mentions in A28 that "/config/supervisord.log" should contain a full list of enpoints.  This is incorrect in my case.  My supervisord.log is only a repeating set of logs that look very much like what you see posted above, including that error about the Publickey being missing.
Any of this help?

Edited May 7, 20251 yr by Elmojo
Updates and logs