[Support] binhex - SABnzbdVPN


Recommended Posts

so I have everything up and running, my VPN creds in everything seems to be configured correctly, the docker runs, and stays running. However when I go to launch the webgui. it just spins on loading. Here is the last bit of the log.. any ideas that could nudge me in the right direction?

 

2019-04-20 08:36:14,551 DEBG 'watchdog-script' stdout output:
[info] SABnzbd not running

2019-04-20 08:36:14,551 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2019-04-20 08:36:44,047 DEBG 'watchdog-script' stdout output:
[warn] Wait for SABnzbd process to start aborted
[info] Waiting for SABnzbd process to start listening on port 8080...

Link to comment
2 hours ago, ruthlessone said:

so I have everything up and running, my VPN creds in everything seems to be configured correctly, the docker runs, and stays running. However when I go to launch the webgui. it just spins on loading. Here is the last bit of the log.. any ideas that could nudge me in the right direction?

 

2019-04-20 08:36:14,551 DEBG 'watchdog-script' stdout output:
[info] SABnzbd not running

2019-04-20 08:36:14,551 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2019-04-20 08:36:44,047 DEBG 'watchdog-script' stdout output:
[warn] Wait for SABnzbd process to start aborted
[info] Waiting for SABnzbd process to start listening on port 8080...

I am Also Experiencing this on 2 Different Servers! 

Link to comment

So I was trying to run my SABnzbd traffic through privoxy. I put everything into Sonarr and Radarr fine. I put the same information into SABnzbd under the "Listening Port" section, and now I get this error:

image.thumb.png.98ba7264c60c78b34cacea38586c8d8b.png

 

How do I revert back to the previous information, and set it up properly?

 

@trurl or @Squid, you guys may know the answer to this too.

 

Thanks in advance.

Link to comment

Hi all,

This is my first post here, nice to meet you :)

 

I’ve been using the SABnzbdVPN docker container for a little while now and it’s been working really well. Thanks so much for creating this!

 

I’ve found that my ISP seems to throttle standard tcp/udp VPN connections including connections from this docker container. I use AirVPN and when I run the standalone AirVPN Eddie client natively on Windows, I can set VPN to run through an SSL connection. When I do this on the native client, my VPN speeds are much higher (around 2.5 time faster download) than when running on tcp/udp VPN ports.

 

I’m trying to replicate the above with OpenVPN in this docker container. I believe the correct way to do this is using stunnel. In the SABnzbdVPN container I’ve installed stunnel, copied the ssl config from AirVPN, copied a new set of VPN config files from AirVPN and put them into the openvpn folder and made sure to reference the full path to all the certs and files.

 

To test things, I kill the openvpn process and try running the stunnel binary which seems to start fine. Then when I run openvpn and reference the new config, it does not start. I get the following error which appears to be from stunnel:

 

TIMEOUTconnect exceeded "no more addresses to connect"

 

My guess is that this address cannot be reached, maybe it’s because this docker container is designed to have VPN connectivity established first before allowing any further connections?

 

I’ve also tried editing /root/openvpn.sh and adding stunnel to start before the eval openvpn command but still get the same error.

 

Any help would be much appreciated. I’m happy to provide more info if needed.

 

Thank you.

Link to comment
On 4/20/2019 at 1:40 PM, ruthlessone said:

so I have everything up and running, my VPN creds in everything seems to be configured correctly, the docker runs, and stays running. However when I go to launch the webgui. it just spins on loading. Here is the last bit of the log.. any ideas that could nudge me in the right direction?

 

2019-04-20 08:36:14,551 DEBG 'watchdog-script' stdout output:
[info] SABnzbd not running

2019-04-20 08:36:14,551 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2019-04-20 08:36:44,047 DEBG 'watchdog-script' stdout output:
[warn] Wait for SABnzbd process to start aborted
[info] Waiting for SABnzbd process to start listening on port 8080...

full log please, follow procedure shown in link below:-

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

 

Link to comment
2 hours ago, binhex said:

this is not configured correctly:-


LAN_NETWORK defined as '192.168.86.1/24'

see here Q4 for how to configure it:-

https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433613

 

hmmm my google wifi is the gateway, hardwired to my AT&T modem, DMZd. Below are my windows and linux ip configs. I did have the gateway in there, what am I missing here? Feeling pretty dense... I am continuing to read that thread, good info in there. But if this lan_network stopping me, I am not getting it. 

 

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Qualcomm Atheros AR8161 PCI-E Gigabit Ethernet Controller (NDIS 6.30)
   Physical Address. . . . . . . . . : 5C-F9-DD-E1-F9-FE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::542a:4366:a9b7:e8c2%18(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.86.242(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, April 17, 2019 2:21:48 PM
   Lease Expires . . . . . . . . . . : Tuesday, April 23, 2019 1:41:02 PM
   Default Gateway . . . . . . . . . : 192.168.86.1
   DHCP Server . . . . . . . . . . . : 192.168.86.1
   DHCPv6 IAID . . . . . . . . . . . : 89979357
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-04-0A-D6-5C-F9-DD-E1-F9-FE
   DNS Servers . . . . . . . . . . . : 192.168.86.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

 

LINUX

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.86.119  netmask 255.255.255.0  broadcast 192.168.86.255
        inet6 fe80::d250:99ff:fe60:459b  prefixlen 64  scopeid 0x20<link>
        ether d0:50:99:60:45:9b  txqueuelen 1000  (Ethernet)
        RX packets 15231190  bytes 8381314785 (7.8 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 30528174  bytes 41731708780 (38.8 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Capture.JPG

Link to comment
6 minutes ago, ruthlessone said:

hmmm my google wifi is the gateway, hardwired to my AT&T modem, DMZd. Below are my windows and linux ip configs. I did have the gateway in there, what am I missing here? Feeling pretty dense... I am continuing to read that thread, good info in there. But if this lan_network stopping me, I am not getting it. 

 

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Qualcomm Atheros AR8161 PCI-E Gigabit Ethernet Controller (NDIS 6.30)
   Physical Address. . . . . . . . . : 5C-F9-DD-E1-F9-FE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::542a:4366:a9b7:e8c2%18(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.86.242(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, April 17, 2019 2:21:48 PM
   Lease Expires . . . . . . . . . . : Tuesday, April 23, 2019 1:41:02 PM
   Default Gateway . . . . . . . . . : 192.168.86.1
   DHCP Server . . . . . . . . . . . : 192.168.86.1
   DHCPv6 IAID . . . . . . . . . . . : 89979357
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-04-0A-D6-5C-F9-DD-E1-F9-FE
   DNS Servers . . . . . . . . . . . : 192.168.86.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

 

LINUX

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.86.119  netmask 255.255.255.0  broadcast 192.168.86.255
        inet6 fe80::d250:99ff:fe60:459b  prefixlen 64  scopeid 0x20<link>
        ether d0:50:99:60:45:9b  txqueuelen 1000  (Ethernet)
        RX packets 15231190  bytes 8381314785 (7.8 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 30528174  bytes 41731708780 (38.8 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Capture.JPG

I can also confirm my is set correctly 

Screen Shot 2019-04-22 at 6.18.33 PM.png

Link to comment
9 hours ago, rguinn said:

But if this lan_network stopping me, I am not getting it. 

192.168.86.1 is a host ip address NOT a network, a network defines the range of ip addresses for your lan, in your particular case  a /24 means that the last octet will be a 0, thus lan_network should be:-

 

192.168.86.0/24

 

the /24 is shorthand (CIDR) for mask 255.255.255.0

Link to comment
8 hours ago, rguinn said:

I can also confirm my is set correctly 

no its not, a /23 means a network of 172.16.0.0/23 and btw 172.16.x.x is a bit unfortunate as that is the network used by the default bridge for docker, not sure if that may cause a clash.

  • Upvote 1
Link to comment
2 hours ago, binhex said:

192.168.86.1 is a host ip address NOT a network, a network defines the range of ip addresses for your lan, in your particular case  a /24 means that the last octet will be a 0, thus lan_network should be:-

 

192.168.86.0/24

 

the /24 is shorthand (CIDR) for mask 255.255.255.0

Thanks for the lesson Bin! That change worked. I hope helps others! Webgui Popped right up after. Will report other issues if they arise!

Link to comment
3 hours ago, binhex said:

no its not, a /23 means a network of 172.16.0.0/23 and btw 172.16.x.x is a bit unfortunate as that is the network used by the default bridge for docker, not sure if that may cause a clash.

True! My Docker been setup and working for some time so what changed to make this a problem now! also changing to 172.16.0.0/23 also did not work 

Link to comment
4 minutes ago, rguinn said:

My Docker been setup and working for some time so what changed to make this a problem now!

nothing has changed as far as im concerned, but it definitely was configured incorrectly and certainly isnt going to help, you can see it in your log:-

2019-04-22 16:35:51,360 DEBG 'start-script' stdout output:
[info] Adding 172.16.5.0/23 as route via docker eth0

2019-04-22 16:35:51,360 DEBG 'start-script' stderr output:
Error: Invalid prefix for given prefix length.

one other thing i spotted in your log is that you dont have iptable_mangle support so you wont be able to access the web ui outside of your lan, im assuming you are testing whilst connected to your lan directly and not externally right?, snipet from your log:-

019-04-22 16:35:51,339 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2019-04-22 16:35:51,340 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

please generate a new log, preferably with debug turned on, follow the procedure below:-

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&amp;comment=435831

 

Link to comment
1 minute ago, binhex said:

nothing has changed as far as im concerned, but it definitely was configured incorrectly and certainly isnt going to help, you can see it in your log:-


2019-04-22 16:35:51,360 DEBG 'start-script' stdout output:
[info] Adding 172.16.5.0/23 as route via docker eth0

2019-04-22 16:35:51,360 DEBG 'start-script' stderr output:
Error: Invalid prefix for given prefix length.

one other thing i spotted in your log is that you dont have iptable_mangle support so you wont be able to access the web ui outside of your lan, im assuming you are testing whilst connected to your lan directly and not externally right?, snipet from your log:-


019-04-22 16:35:51,339 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2019-04-22 16:35:51,340 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

please generate a new log, preferably with debug turned on, follow the procedure below:-

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&amp;comment=435831

 

Will Do! I uses a VPN so I never attempted to connect to it via the outside world. 

Link to comment
18 minutes ago, rguinn said:

Ok here a new log what am I doing wrong?

my guess at the moment is that you have sabnzbd  configuration corruption or misconfiguration which is preventing sabnzbd from starting, can you try the following:-

 

1. stop the container

2. rename the config folder, say put _old on the end, so /mnt/.../sabnzbd rename to /mnt/.../sabnzbd_old

3. start the container

4. if it starts then the issue is config corruption or bad config, best bet is to reconfigure the app or alternatively restore from backup

5. if it doesnt start then stop the container and delete the newly created config folder and then reverse step 2. 

Link to comment
4 minutes ago, rguinn said:

This was a new install as I originally believed it was a issue with the docker as it broke after a unraid reboot. 

 

Let me try again 

interesting that it broke after a reboot, potentially this could be the cause of corruption (shouldnt do), what path is /config pointing to on your host?, is it /mnt/user/appdata/... by any chance?

Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.