I have a similar problem, but forcing it to update didn't fix it. This is a new setup, so it hasn't worked in the past.
2024-07-07 11:25:36.429516 [info] Host is running unRAID
2024-07-07 11:25:36.479135 [info] System information Linux xxx 6.1.74-Unraid #1 SMP PREEMPT_DYNAMIC Fri Feb 2 11:06:32 PST 2024 x86_64 GNU/Linux
2024-07-07 11:25:36.539109 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-07-07 11:25:36.597376 [info] PUID defined as '99'
2024-07-07 11:25:36.812854 [info] PGID defined as '100'
2024-07-07 11:25:36.965900 [info] UMASK defined as '000'
2024-07-07 11:25:37.023515 [info] Permissions already set for '/config'
2024-07-07 11:25:37.086714 [info] Deleting files in /tmp (non recursive)...
2024-07-07 11:25:37.168026 [info] VPN_ENABLED defined as 'yes'
2024-07-07 11:25:37.228004 [info] VPN_CLIENT defined as 'openvpn'
2024-07-07 11:25:37.285699 [info] VPN_PROV defined as 'pia'
2024-07-07 11:25:37.364695 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/bahamas-aes-256-gcm-udp-ip.ovpn
2024-07-07 11:25:37.486260 [info] VPN remote server(s) defined as 'panama.privacy.network,'
2024-07-07 11:25:37.535332 [info] VPN remote port(s) defined as '1197,'
2024-07-07 11:25:37.588995 [info] VPN remote protcol(s) defined as 'udp,'
2024-07-07 11:25:37.649441 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-07-07 11:25:37.711845 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-07-07 11:25:37.770074 [info] NAME_SERVERS defined as '1.1.1.1'
2024-07-07 11:25:37.828988 [debug] iptables default policies available, setting policy to drop...
2024-07-07 11:25:37.893977 [debug] ip6tables default policies available, setting policy to drop...
Error: error sending query: Could not send or receive, because of network error
2024-07-07 11:25:53.034055 [debug] Having issues resolving name 'panama.privacy.network', sleeping before retry...
Error: error sending query: Could not send or receive, because of network error
2024-07-07 11:26:13.115609 [debug] Having issues resolving name 'panama.privacy.network', sleeping before retry...
I believe the problem is the name servers are not being added to /etc/resolv.conf
sh-5.2# cat /etc/resolv.conf
nameserver 127.0.0.11
options ndots:0
sh-5.2# iptables -S
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -p udp -m udp --sport 53 -j ACCEPT
-A INPUT -p tcp -m tcp --sport 53 -j ACCEPT
-A INPUT -d 127.0.0.11/32 -j ACCEPT
-A INPUT -s 127.0.0.11/32 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 53 -j ACCEPT
-A OUTPUT -d 127.0.0.11/32 -j ACCEPT
-A OUTPUT -s 127.0.0.11/32 -j ACCEPT
I tried to create a script to fix and enabled ENABLE_STARTUP_SCRIPTS, but it doesn't seem to run.
sh-5.2# cat /config/scripts/setdns.sh
#!/bin/bash
# Use resolv.conf for systems without systemd-resolved
sudo echo "nameserver 1.1.1.1" > /etc/resolv.conf
# echo "options ndots:0" >> /etc/resolv.conf
echo "Cloudflare DNS (1.1.1.1) set using resolv.conf."
If I manually run the script, everything works.
2024-07-07 11:31:14.347164 [debug] Having issues resolving name 'panama.privacy.network', sleeping before retry...
Error: error sending query: Could not send or receive, because of network error
2024-07-07 11:31:34.430559 [debug] Having issues resolving name 'panama.privacy.network', sleeping before retry...
2024-07-07 11:31:39.508413 [debug] DNS operational, we can resolve name 'panama.privacy.network' to address '91.90.126.54 91.90.126.85 91.90.126.93'
2024-07-07 11:31:39.604011 [debug] DNS operational, we can resolve name 'www.privateinternetaccess.com' to address '172.64.151.73 104.18.36.183'
2024-07-07 11:31:39.696812 [debug] DNS operational, we can resolve name 'serverlist.piaservers.net' to address '104.18.159.201 104.19.240.167'
2024-07-07 11:31:39.779550 [debug] Showing name servers in '/etc/resolv.conf' before overwrite from NAME_SERVERS...
2024-07-07 11:31:39.830473 [debug] nameserver 1.1.1.1
2024-07-07 11:31:39.890398 [debug] Showing name servers in '/etc/resolv.conf' after overwrite from NAME_SERVERS...
2024-07-07 11:31:39.942423 [debug] nameserver 1.1.1.1
2024-07-07 11:31:40.516230 [debug] Docker interface name, Gateway interface name, Gateway IP, Docker interface IP, Subnet mask and CIDR are defined as 'eth0,eth0,192.168.0.123,192.168.0.102,255.255.255.0,192.168.0.0/24'
2024-07-07 11:31:40.724860 [info] LAN_NETWORK defined as '192.168.0.0/24'
2024-07-07 11:31:40.812496 [info] LAN_NETWORK exported as '192.168.0.0/24'
2024-07-07 11:31:40.877175 [info] VPN_USER defined as 'xxx'
2024-07-07 11:31:40.939152 [info] VPN_PASS defined as 'xxx'
2024-07-07 11:31:40.999706 [info] STRICT_PORT_FORWARD defined as 'no'
2024-07-07 11:31:41.067426 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2024-07-07 11:31:41.125338 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2024-07-07 11:31:41.184590 [info] ENABLE_STARTUP_SCRIPTS defined as 'yes'
2024-07-07 11:31:41.243585 [info] ENABLE_SOCKS defined as 'no'
2024-07-07 11:31:41.303996 [info] ENABLE_PRIVOXY defined as 'no'
2024-07-07 11:31:41.637025 [info] Executing user script '/config/scripts/setdns.sh' in the foreground...
2024-07-07 11:31:41.688619 [script] Cloudflare DNS (1.1.1.1) set using resolv.conf.
2024-07-07 11:31:41.749979 [info] Starting Supervisor...
2024-07-07 11:31:42,330 INFO Included extra file "/etc/supervisor/conf.d/sabnzbdvpn.conf" during parsing
2024-07-07 11:31:42,330 INFO Set uid to user 0 succeeded
2024-07-07 11:31:42,336 INFO supervisord started with pid 7
2024-07-07 11:31:43,340 INFO spawned: 'start-script' with pid 566
2024-07-07 11:31:43,343 INFO spawned: 'watchdog-script' with pid 567
2024-07-07 11:31:43,344 INFO reaped unknown pid 8 (exit status 0)
2024-07-07 11:31:43,355 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
2024-07-07 11:31:43,355 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-07-07 11:31:43,356 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
<snip>
So it seems like it gets stuck trying to resolve, before adding the addresses to /etc/resolv.conf or running the scripts.