[Support] binhex - SABnzbdVPN


Recommended Posts

39 minutes ago, Drew4 said:

Hello -

 

I am getting the following error....

 

2021-11-22 15:40:04,880 DEBG 'start-script' stdout output:
2021-11-22 15:40:04 Unsupported cipher in --data-ciphers: AES-256-CBC-SHA
Options error: NCP cipher list contains unsupported ciphers or is too long.

 

Any help would be greatly appreciated. Thanks

download the latest openvpn config file and certs from your vpn provider and replace existing then restart the container.

Link to comment
On 11/15/2021 at 1:51 PM, Roudy said:

You can change your name servers on the container to the below and it should fix the issue. You can change them back to what you had after they get whatever is going on sorted.

 

1.1.1.1,1.0.0.1

Thanks for this, fixed it for me too. Will keep an eye on it.

Link to comment
  • 4 weeks later...
  • 4 weeks later...

I'm getting large supervisord.log files filled with entries such as this:

2022-01-16 11:00:26,657 DEBG 'start-script' stdout output:
RwRwRwRwRwrW

image.png.6bcd8c6685e36fc293cb80cfd5fa9c2a.png

This causes problems with Synology's log file reader for Docker. 

Is there a easy way to turn down supervisord log level to info?

 

I did set the DEBUG to false in env.

 

Thanks!

Edited by JasonB
Link to comment
  • 3 weeks later...
  • 2 weeks later...

I set up a new router and now I can't access the web UI for this Docker. Other containers still work -- Plex, Sonarr, and Radarr. But SABnzbd and qBittorrent are both broken at the moment. While watching Docker logs, it looks like it goes through the whole process and says listening on port 8080 at the end. But trying to connect to the web UI just times out and never loads. The only thing I have tried changing is the LAN_NETWORK setting in the config. My network ID changed from 192.168.1 to 192.168.4, so I changed LAN_NETWORK to 192.168.4.0/38 from 192.168.1.0/24. Is there something else I need to look at or change?

Link to comment
1 minute ago, Tiller said:

I set up a new router and now I can't access the web UI for this Docker. Other containers still work -- Plex, Sonarr, and Radarr. But SABnzbd and qBittorrent are both broken at the moment. While watching Docker logs, it looks like it goes through the whole process and says listening on port 8080 at the end. But trying to connect to the web UI just times out and never loads. The only thing I have tried changing is the LAN_NETWORK setting in the config. My network ID changed from 192.168.1 to 192.168.4, so I changed LAN_NETWORK to 192.168.4.0/38 from 192.168.1.0/24. Is there something else I need to look at or change?

Look at the docker logs, it should be fairly clear what the issue is. Did you place your vpn file where required? (Conf/ovpn)

Link to comment
19 minutes ago, dja said:

Look at the docker logs, it should be fairly clear what the issue is. Did you place your vpn file where required? (Conf/ovpn)

 

The only new error I saw was for trying to add the route with the new IP.

image.png.d65f2e307f84685604075a3acffe5853.png

 

I changed the LAN_NETWORK setting to include both with a comma between them -- "192.168.1.0/24,192.168.4.0/38". The 1.0/24 address gets added as a route without issue, but the error for the 4.0/38 is obviously still there. And with both of them in the LAN_NETWORK setting, or either one individually, it doesn't matter. I still can't access the web UI.

 

I don't see any other errors that would explain it. There are some other errors/warnings, but they have seemingly always existed as they also show up in older logs when it was previously working.

Link to comment
1 hour ago, Tiller said:

 

The only new error I saw was for trying to add the route with the new IP.

image.png.d65f2e307f84685604075a3acffe5853.png

 

I changed the LAN_NETWORK setting to include both with a comma between them -- "192.168.1.0/24,192.168.4.0/38". The 1.0/24 address gets added as a route without issue, but the error for the 4.0/38 is obviously still there. And with both of them in the LAN_NETWORK setting, or either one individually, it doesn't matter. I still can't access the web UI.

 

I don't see any other errors that would explain it. There are some other errors/warnings, but they have seemingly always existed as they also show up in older logs when it was previously working.

It looks like you have vpn settings configured without it actually turned on via settings? See key1 in settings. 
image.thumb.png.37d6458af5469bcc0b7cf9c93ccd4b7c.png
Are you running more than one network for Unraid? Can you set the docker to custom bridge for networking and manually assign it a static IP on the same network as your Unraid server? Also, try looking if it is http vs. https in the address. I've attached my config so you can see. 

Link to comment
37 minutes ago, dja said:

It looks like you have vpn settings configured without it actually turned on via settings? See key1 in settings.

 

Are you running more than one network for Unraid? Can you set the docker to custom bridge for networking and manually assign it a static IP on the same network as your Unraid server? Also, try looking if it is http vs. https in the address. I've attached my config so you can see. 

 

I did already have VPN enabled in the settings. However, I was able to fix it thanks to your image. When I changed the network type to custom, for the subnet out to the right it had "192.168.4.0/22". So I changed it back to Bridge and put that value in the LAN_NETWORK field and now it works. So thanks for the help!

  • Like 1
Link to comment
  • 2 weeks later...

  

On 11/18/2021 at 3:41 AM, francishefeng59 said:

Hi, 

After running a day, another problem came up. Once the internet connection was down or it lost connection after being idle for some time , it wouldn't re-establish connection even when the internet was up or tasks were imported waiting for being downloaded. I have to restart them manually. I've tried sabnzbdvpn and nzbgetvpn, all giving me the same issue. Privoxyvpn works ok. But I failed to find how to get them to work on privoxyvpn. Any idea?

 

Part of the log after the internet is up:

2021-11-18 10:44:31,537 DEBG 'start-script' stdout output:
2021-11-18 10:44:31 TCP/UDP: Preserving recently used remote address: [AF_INET]23.19.87.116:1194
2021-11-18 10:44:31 Socket Buffers: R=[212992->212992] S=[212992->212992]
2021-11-18 10:44:31 UDP link local: (not bound)
2021-11-18 10:44:31 UDP link remote: [AF_INET]23.19.87.116:1194

2021-11-18 10:44:31,537 DEBG 'start-script' stdout output:
2021-11-18 10:44:31 write UDP: Network is unreachable (code=101)
2021-11-18 10:44:31 Network unreachable, restarting
2021-11-18 10:44:31 SIGHUP[soft,network-unreachable] received, process restarting

2021-11-18 10:44:31,538 DEBG 'start-script' stdout output:
2021-11-18 10:44:31 OpenVPN 2.5.4 [git:makepkg/3f7a85b9aebe7be0+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct  5 2021
2021-11-18 10:44:31 library versions: OpenSSL 1.1.1l  24 Aug 2021, LZO 2.10

2021-11-18 10:44:31,538 DEBG 'start-script' stdout output:
2021-11-18 10:44:31 Restart pause, 5 second(s)

 

Hi everyone,

i have the exact same problem. This was "fixed" by the user by routing through a privoxy container, but that cant be the only solution, right?

After restarting the container, everything works fine (as long as downloads are active).

If I add items to the queue after some idle time, it never reconnects. Just gets stuck in this restart loop.

Anyone know how to fix this? It was 100% working like a year ago with the same setup.

Thanks!

 

 

Link to comment

Hi,

 

First off all thx to Binhex for his excellent docker containers.

I run most of my containers on a seperate (docker) VLAN.

For example with the qbittorrent docker I have access https://qbittorrent.mydomain.com who points to ip:443 where certificates are installed for my domain

 

However now the problem with Sabnzbd I can enable https and install the certificate however I can't seem to be able to change the port from 8090 to 443, I now I can use ngnix and I use this for my external but internally I like to have an direct connection. Also the http port can't be saved it reverts to the default 8080. Is there any variable I need to add? Or change it manually in a config file?

 

Seems to be the same issue in the Linuxserver version of the container:

https://github.com/linuxserver/docker-sabnzbd/issues/90

 

Thx

Edited by Kopernikus
Link to comment

Can't access GUI today.

I see this error message

2022-03-01 05:59:25 Options error: Unrecognized option or missing or extra parameter(s) in [PUSH-OPTIONS]:5: block-outside-dns (2.5.5)

 

Is this the possible reason or something else easy to fix? Docker is up and performing, I just can't get to it.

 

Thanks

Link to comment

Hi All

 

@binhexThank you so much for your containers. I am definitely buying you a couple of beers.

 

I have a minor issue, I am trying to run both binhex-delugevpn and binhex-sabnzbdvpn. Both are setup to connect to PIA via Wireguard and use the corresponding default wg.conf. However, once I start one of the containers, the other one won't start. Any idea why?

Link to comment
Hi All
 
@binhexThank you so much for your containers. I am definitely buying you a couple of beers.
 
I have a minor issue, I am trying to run both binhex-delugevpn and binhex-sabnzbdvpn. Both are setup to connect to PIA via Wireguard and use the corresponding default wg.conf. However, once I start one of the containers, the other one won't start. Any idea why?
Most probably a port clash on the host side make sure you have unique host ports for each container

Sent from my CLT-L09 using Tapatalk

Link to comment

On installations from CA there should also be a popup showing if there is a port clash on the host side

 

If in doubt, the docker run command for the app which won't start will tell you exactly why (if you see an execution error when trying to start it)

Link to comment
  • 4 weeks later...

I just started having a DNS problem with this container and I've maxed out my limited Linux chops trying to figure it out. I've spent about 2 hours on this and done a lot internet searching, but haven't found anyone having this problem recently. Odds are I'm missing something basic.

 

SABnzbd "Status and Interface Options" screen says "Connection Failed!" for Public IPv4 address and Nameserver / DNS Lookup. I turned Debug logging on, but the logfile doesn't seems to be telling me anything:

 

sabnzbd.log

 

Relevant details:

  • Container has worked flawlessly until yesterday, though I probably hadn't used it in about a week before that
  • My binhex-deluge container has no problems, using the same VPN setup; and I have no problems with any of my other containers or with the host
  • I'm using Mullvad VPN
  • I've always used the Mullvad DNS servers, but have also tried 1.1.1.1,1.0.0.1
  • I've restarted the container at least 20 times in the course of troubleshooting
  • ifconfig inside the container shows I have an IPv4 address from Mullvad, which SABnzbd shows as the local IPv4 address
  • I can ping the Mullvad and Cloudflare DNS server IPs from inside the container
  • Running dig inside the container yields "connection timed out; no servers could be reached"

Anyone have any thoughts on how I can fix this?

Link to comment
On 4/2/2022 at 12:14 PM, naxos said:

I just started having a DNS problem with this container and I've maxed out my limited Linux chops trying to figure it out.

 

Well, and it just started working today, both with Mullvad and Cloudflare DNS servers. I have no idea why. I guess I'll take it.

Link to comment

Anyone would have a list of server to use with Private Internet Access (Wireguard)...  I install the application, that is now working but super slow.  Would like to try a different endpoint.  I search google and contacted the support at PIA (which was not really helpfull).

 

Thank you for your help,

Martin

Link to comment
  • 4 weeks later...
  • 3 weeks later...
Posted (edited)
On 5/4/2022 at 7:59 PM, bumpyclock said:

I was able to fix this, some how permissions had changed on /data/complete to root. chown -R nobody:users /data/complete seems to have fixed this for me

Any more thoughts on what may have caused this? I’m having the same issue. What’s to stop it happening again?

 

Looking at my system it chewed through 50GB of bandwidth over the last few hours trying to download and redownload files that were no longer importing. 

Edited by stridemat
Link to comment
12 hours ago, stridemat said:

Any more thoughts on what may have caused this? I’m having the same issue. What’s to stop it happening again?

 

have you upgraded to unraid 6.10.0 by any chance?, i see on reddit people complaining about random permissions changes to appdata so it maybe related to that.

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.