Elmojo

Again? Sure thing, here you go... docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='xxx' -e 'VPN_PASS'='xxx' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='wireguard' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'ENABLE_SOCKS'='no' -e 'SOCKS_USER'='admin' -e 'SOCKS_PASS'='socks' -e 'LAN_NETWORK'='192.168.1.0/24, 100.64.98.0/24' -e 'WEBUI_PORT'='8080' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'VPN_OPTIONS'='' -e 'ENABLE_STARTUP_SCRIPTS'='no' -e 'USERSPACE_WIREGUARD'='no' -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png' -p '8080:8080/tcp' -p '8118:8118/tcp' -p '9118:9118/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' -v '/mnt/user/downloads/':'/data':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn' 4542ef1bedcedbceb49e7138ea62bc011015345aba3cabf586463647620d5539 The command finished successfully! supervisord.log

That's why I'm so baffled as to why my setup isn't working! I've been struggling with this for weeks, with no real progress. I've tried my best to follow the installation guide and FAQs, but I just hit a wall. It's so frustrating. :( I don't know what else to do. What do you need from me to help troubleshoot further?

Does ProtonVPN provide a Wireguard-specific configuration download for you? I'm using PIA, and don't see any option to download a WG config. I think this is my issue as well. Maybe.

Morning all! Can we circle back to this for a moment please? I'm still stuck... So I'm starting over with this container. When I try to follow the initial setup guide, as linked in Post #1 of this thread, it says nothing about WG, only OpenVPN. That's why I was thinking there was no need for the manual config, since I thought I recalled that @binhex said that switching to WG negated the need for all the manual setup. I'm probably remembering that wrong, it's been a while. I've put the ovpn and cert files in the 'openvpn' folder, as directed. When I start the container, it creates an empty 'wireguard' folder, so it's obviosuly looking for the wg0 file, I just don't have one to give it. I don't see any way to manually download any sort of WG config for PIA, and the container doesn't appear to be setting it up automatically for me, so now what do I do....? Thanks in advance for any help! 😁

I edited my post above earlier to clarify what I meant, that I wasn't asking about editing the wg0 file. Regardless, if there is manual setup involved, I have no recollection of it. I may need to just wipe this whole thing and start over again. I've just been dealing with this for so long now that I've honestly about forgotten what I have and haven't tried. lol So I'm starting over, but what's is really getting me is that when I try to follow the initial setup guide, as linked in Post #1 of this thread, it says nothing about WG, only OpenVPN. That's why I was thinking there was no need for the manual config, since I thought I recalled that Binhex said that switching to WG negated the need for all the manual setup. I'm probably remembering that wrong, it's been a while. Anyway, I'm still stuck, since I don't see any way to manually download any sort of WG config for PIA, and the container doesn't appears to be setting it up automatically for me, so now what do I do....? Again, I'm very sorry to be so needy. I normally can suss things out better on my own, but my brain is a little bit fried from caring for a sick wife, so I'll beg for some extra patience, and thank everyone for their help!

I was just asking why replacing the wg0 file was needed, or where that would even come from, since when using PIA with this container, there's not supposed to be any manual configuration involved. That's the main reason why I switched over to PIA. @binhex confirmed that a few posts back, I believe. Thanks for the heads up on the exposed creds. I had obscured them in the previous version, but probably forgot to do it when I uploaded the revised version with the debug info. It kinda baffles me that that info is shown in the logs in cleartext anyway.

Yes, I have a pfsense firewall/router, but its config hasn't changed in many months. I do also use Tailscale, but it also has not had a configuration change in months, and works fine for all my other connections. Checking the FAQ Q36, I see that it's referencing 'MagicDNS', which I don't use. I have it disabled in Tailscale, and always have. It conflicts with the settings I use to connect to my server at work. I notice that part of the workaround is "TAILSCALE_USERSPACE_NETWORKING is set to false - Fix is to set this to true" I don't have that flag in my template for qBitVPN, even in advanced view. Where would I find it? Does it need to be added manually? EDIT: I'm also still seeing this in the log, which seems significant: Line unrecognized: `PublicKey=' Configuration parsing error

Welcome to the club.

No problem, see attached, thanks! EDIT: Docker Run: docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='p0494908' -e 'VPN_PASS'='e74MuKAiVY' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='wireguard' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'ENABLE_SOCKS'='no' -e 'SOCKS_USER'='admin' -e 'SOCKS_PASS'='socks' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'WEBUI_PORT'='8080' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='true' -e 'VPN_OPTIONS'='' -e 'ENABLE_STARTUP_SCRIPTS'='no' -e 'USERSPACE_WIREGUARD'='no' -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png' -p '8080:8080/tcp' -p '8118:8118/tcp' -p '9118:9118/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' -v '/mnt/user/downloads/':'/data':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn' 8e9aaa9fc1bff3fbd4adc8be98b58ee16f050d8d537f82fbe8a9cae0685aceb7 supervisord.log

That's odd, since I don't recall ever having modified the nameservers field, nor the input ports. I was under the impression that using PIA caused all that stuff to be handled automatically. Since it appears that my install may be generally borked, I removed the container (and directory) and reinstalled it. Oddly, the new template looks quite different than the old one. Even though I was fully updated, the fields were in different orders, and some options were added or moved on the new template. After installing fresh (using the default options, and my PIA creds), I'm getting the exact same errors... The log and supervisord both stall at: 2025-05-11 16:51:25,954 DEBG 'start-script' stdout output: [info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'... No idea what to try next...

I've been back through the past 6-7 pages, and I don't see anything that addresses my issue. I apologize if I missed it. PIA isn't supposed to require that sort of manual config. That's the whole point of using them vs others with this container, unless I'm missing something. Also, I've tried changing the endpoint in the config file (as noted above) with no change. I did do as much troubleshooting as I could on my own, but I'll need some assistance at this point.

Glad that worked for you. I'm still dead in the water, and no one appears to be available to help, even the gurus like @binhex or @wgstarks, who are normally so quick to respond. When you say you replaced the wg0 file, where did you get the file or info for the replacement? This may be my issue as well. I can't access the GUI at all, unless I disable the VPN.

Ok, so I've done more hunting and digging, and I can maybe narrow this down a little. After deleting the supervisord.log file and letting it regen, I was able to watch it during a container startup, to see what's happening. It appears that all goes okay, until it gets to the line "[info] Trying to connect to the PIA WireGuard API on 'ca-ontario.privacy.network'...", where it just hangs for several minutes. During this time, checking the docker log shows a recurring loop of: 2025-05-08 11:09:58,617 DEBG 'start-script' stdout output: [info] Configuring WireGuard... 2025-05-08 11:09:58,865 DEBG 'start-script' stdout output: [info] Token generated for PIA wireguard authentication 2025-05-08 11:09:58,874 DEBG 'start-script' stdout output: [info] Trying to connect to the PIA WireGuard API on 'ca-ontario.privacy.network'... 2025-05-08 11:14:59,318 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2025-05-08 11:14:59,343 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2025-05-08 11:14:59,365 DEBG 'start-script' stderr output: [#] ip link add wg0 type wireguard 2025-05-08 11:14:59,371 DEBG 'start-script' stderr output: [#] wg setconf wg0 /dev/fd/63 2025-05-08 11:14:59,374 DEBG 'start-script' stderr output: Line unrecognized: `PublicKey=' Configuration parsing error 2025-05-08 11:14:59,380 DEBG 'start-script' stderr output: [#] ip link delete dev wg0 2025-05-08 11:14:59,431 DEBG 'start-script' stdout output: [warn] WireGuard interface failed to come 'up', exit code is '1' This appears to be the issue, but I don't see any obvious way to address it. Flipping the VPN_ENABLED flag to 'no' causes the container to start immediately and work perfectly (and downloads FAST, like it never was with the VPN on!), but of course that defeats the whole purpose. lol I also notice that there's a port number listed in the VPN_INPUT_PORTS field of the template. Is that correct? Doesn't PIA auto-assign ports? I'm wondering if that's something I did way back when I was setting this up about a year ago that's now causing an issue or something. Any help greatly appreciated. Sorry for the hot mess that is the previous post. I was trying to piece it all together while hopping back and forth to the hospital.

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?

Is the Deemix docker dead? Mine seems to be updated, and is running fine, but I'm unable to download. It says I need to login, but I'm unable to do so. I've logged in at the Deezer site with no problems, but the instructions on the docker help page about how to obtain an ARL seem to be outdated. For example, Chrome no longer displays a 'lock' icon next to URLs. Anyone got this working?

Yeah, me too. Wait, why do I even still have this docker installed? lol

Is this still being maintained? When I try to update, it returns the error: "no matching manifest for linux/amd64 in the manifest list entries"

Found the problem, right there. Sorry, couldn't resist. Carry on. 😅

Turned off where, exactly? Is this the "Use Tailscale DNS settings" in the Settings screen for the TS plugin, or elsewhere?

Mine is not. The files being backed up all have incorrect timestamps. I will add the variable and see if that helps, thanks. EDIT: Well....crap. Anyone have some ketchup to go with this crow I'm about to eat? lol It turns out that the Timezone was set wrong on the whole dang server. I must have forgotten that I needed to set that when I configured this new machine. Doh. All is well, obviously.

Thanks, I'll try disabling both and see if that helps. I don't really have anything in the home that would require uPnP anyway, so let's see what happens with it off entirely in pfSense. Yes. My wife connects to her home desktop from work, so she can have access to files on our home server.

It's a desktop PC, it's always on my LAN. lol

Yes, TS subnets are enable on her desktop. How would I go about resolving NAT-PMP/TS collisions, or whatever you're seeing? My router is pfsense, if that helps. What sort of nginx messages? Errors? I have no idea how to read a log, so I'm relying on you for this one.

Any thoughts on this? I think it may have gotten lost in the stack.

Ok, got a weird one... TS is working great, except on 1 machine - My wife's desktop. The only thing different about her machine is that it connects wirelessly to my home LAN. Otherwise, it's a typical Windows 10 desktop PC. Anyway, here's the deal... She can browse the internet, and can see other devices on our LAN (including the server GUI, and VMs on the server), but cannot see shares on our unraid server if TS is enabled. If I turn it off, then it will usually work. I can even turn TS off, then back on, and it will often allow share access. I did have to enable NetBIOS on the server (plugin) side, because it was killing the scan to file on my copier, but this doesn't seem to have affected any of the other devices in the home. Can anyone think of a reason why her machine specifically would be having intermittent loss of shares access? It's maddening. Diags package attached, if it's helpful. Tower-tailscale-diag-20241001-094150.zip