Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - SABnzbdVPN

Featured Replies

  • Author
12 minutes ago, Lonewolf147 said:

Here are my own files, I did not downgrade yet.  And for note, my STRICT_PORT_FORWARD is set to no.

 

supervisord - Copy.log 2.71 kB · 0 downloads Sabnzbd comman execution.txt 1.32 kB · 0 downloads

OK yep this is def not related to STRICT_PORT_FORWARD, your issue looks to be name resolution related, can you try changing NAME_SERVERS to a value of '1.1.1.1', the ones you have listed are the defaults but it is possible one of the lesser known name server was having intermittent issues, or possibly that your router/firewall is blocking.

  • Replies 1.8k
  • Views 423.3k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • i'm aware of the issue guys and i think i have a fix, i shall post back when i have built a fixed image.

  • hi guys, spotted the issue regards dos2unix.sh and corrected it, image now  building, should be done in around an hour.. then pull and you should be back up and running.

  • there are ongoing issues with PIA DNS, you can try setting NAME_SERVERS to the following (removes PIA DNS):- 84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1  

Posted Images

1 hour ago, binhex said:

OK can you check your firewall/router and ensure you are not blocking outbound port 53.

Looked through those, and I still don't see anything specifically blocking them (and I never programmed them to). Running netstat I see lots of references to port 53, with the TIME_WAIT status. 

3 hours ago, binhex said:

So what's the fix?, either connect to an endpoint that does support port forwarding, check your log for details, or simply set STRICT_PORT_FORWARD to 'no'.

Thank you - that did it! Now working fine with 'latest'.

  • Author
10 hours ago, Lonewolf147 said:

Looked through those, and I still don't see anything specifically blocking them (and I never programmed them to). Running netstat I see lots of references to port 53, with the TIME_WAIT status. 

ok lets check iptables isn't blocking, can you do the following:-

  1. start the container
  2. left click container and click on 'console'
  3. type 'iptables -S' and paste the result here.
     

And just for clarity here, i am unable to reproduce your issue so far, i have tried the same image (latest), with the same provider (pia) with the same endpoint (ca-toronto.privacy.network) and i see no name resolution issues, proof:-
 

\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2024-07-03 09:34:48.320018 [info] Host is running unRAID
2024-07-03 09:34:48.350510 [info] System information Linux 49f9190977ff 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux
2024-07-03 09:34:48.387028 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-07-03 09:34:48.423739 [info] PUID defined as '99'
2024-07-03 09:34:48.467732 [info] PGID defined as '100'
2024-07-03 09:34:48.524124 [info] UMASK defined as '000'
2024-07-03 09:34:48.558353 [info] Permissions already set for '/config'
2024-07-03 09:34:48.596441 [info] Deleting files in /tmp (non recursive)...
2024-07-03 09:34:48.647694 [info] VPN_ENABLED defined as 'yes'
2024-07-03 09:34:48.685685 [info] VPN_CLIENT defined as 'openvpn'
2024-07-03 09:34:48.721259 [info] VPN_PROV defined as 'pia'
2024-07-03 09:34:48.763101 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/pia-ng.ovpn
2024-07-03 09:34:48.836984 [info] VPN remote server(s) defined as 'ca-toronto.privacy.network,'
2024-07-03 09:34:48.870104 [info] VPN remote port(s) defined as '1197,'
2024-07-03 09:34:48.900562 [info] VPN remote protcol(s) defined as 'udp,'
2024-07-03 09:34:48.936538 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-07-03 09:34:48.971934 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-07-03 09:34:49.008354 [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'
2024-07-03 09:34:49.044967 [debug] iptables default policies available, setting policy to drop...
2024-07-03 09:34:49.084520 [debug] ip6tables default policies available, setting policy to drop...
2024-07-03 09:34:49.124388 [debug] Adding 84.200.69.80 to /etc/resolv.conf...
2024-07-03 09:34:49.162317 [debug] Adding 37.235.1.174 to /etc/resolv.conf...
2024-07-03 09:34:49.201432 [debug] Adding 1.1.1.1 to /etc/resolv.conf...
2024-07-03 09:34:49.236248 [debug] Adding 37.235.1.177 to /etc/resolv.conf...
2024-07-03 09:34:49.272821 [debug] Adding 84.200.70.40 to /etc/resolv.conf...
2024-07-03 09:34:49.307925 [debug] Adding 1.0.0.1 to /etc/resolv.conf...
2024-07-03 09:35:04.401025 [debug] DNS operational, we can resolve name 'ca-toronto.privacy.network' to address '179.61.197.191 191.96.36.67 191.96.36.71'
2024-07-03 09:35:19.493504 [debug] DNS operational, we can resolve name 'www.privateinternetaccess.com' to address '172.64.151.73 104.18.36.183'
2024-07-03 09:35:19.559160 [debug] DNS operational, we can resolve name 'serverlist.piaservers.net' to address '104.19.240.167 104.18.159.201'

 

EDIT - oh and BTW your openvpn config file is out of date, you should be connecting on port 1198 not port 1197 (as shown in your log), so please update your config files (not related to the name resolution issue).

1 hour ago, binhex said:

EDIT - oh and BTW your openvpn config file is out of date, you should be connecting on port 1198 not port 1197 (as shown in your log), so please update your config files (not related to the name resolution issue).

I'll do the rest of the testing after work today.

As for the openvpn config files, I'm using PIA's strong encryption file which uses port 1197

image.thumb.png.e16a437c0ff1f636cf5fa766c0adeb3d.png

  • Author
4 minutes ago, Lonewolf147 said:

I'll do the rest of the testing after work today.

As for the openvpn config files, I'm using PIA's strong encryption file which uses port 1197

image.thumb.png.e16a437c0ff1f636cf5fa766c0adeb3d.png

Ahh ok fair enough, i hacked my openvpn cofig file to look like yours but did not change AES etc so it failed to start but you should be fine if you downloaded it from PIA.

17 hours ago, binhex said:

ok lets check iptables isn't blocking, can you do the following:-

  1. start the container
  2. left click container and click on 'console'
  3. type 'iptables -S' and paste the result here.

Alright, sorry for the delay. It's been a day...

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 OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 53 -j ACCEPT

Switched back to ver .03 this morning and all is working again.

Upgraded a little while ago and having similar problem as Lonewolf147

 

I created a new pia config file to ensure nothing was screwed up there. 

 

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 OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p tcp -m tcp --dport 53 -j ACCEPT

Command execution.txt supervisord.log.txt

Anyone know if there is a problem with PIA wireguard in the last day or so?

Just woke up this morning and Sab and my privoxyvpn containers are both getting the following error recurring

 

Error: error sending query: Error creating socket

Error: error sending query: Error creating socket

 

I use the same wireguard config file on my rtorrentvpn container and its working just fine. 

 

EDIT

I've tried an updated wg0.conf and i'm getting the same issue. 

Also tried ovpn and same issue. 

 

Edited by tazire

2 hours ago, tazire said:

Anyone know if there is a problem with PIA wireguard in the last day or so?

Just woke up this morning and Sab and my privoxyvpn containers are both getting the following error recurring

 

Error: error sending query: Error creating socket

Error: error sending query: Error creating socket

I've got the same issue with AirVPN today

Having the same problem with binhex-delugevpn, so whatever changed in common between them is probably causing the problem. Rolled both back to previous versions and the problem went away.
 

  • Author

i'm aware of the issue guys and i think i have a fix, i shall post back when i have built a fixed image.

Like others, I'm getting the same issue, but after investigating it a bit (I'm no expert btw), I realised that changing the docker network type from custom (which is what I've using) to bridge resolved the issue. The issue appears to be with resolving DNS using the custom docker network DNS server 127.0.0.11. Not sure if this will help anyone, or assist in fixing the root cause, but I thought it wouldn't hurt to post.

  • Author

Ok guys a new image has been produced, for anybody with the name resolution issue please do the following:-
 

  1. login to unraid web ui
  2. go to docker tab
  3. toggle switch top right to 'advanced view'
  4. click on 'force update' for the container
  5. check logs for errors.

you rock! worked after forced update!

Thanks @binhex - Also working for me after update (and back on my custom docker network). Thank you!

Ahhh you legend 🙂 its all back up and running again!! Thanks for fixing this one so quickly! 💪

Latest version fixed my issues too!  Thanks binhex!

 

Can also confirm everything is working again.

Forced upgrade fixed the problem.

 

Thanks for your work in fixing this.

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.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.