[Support] binhex - SABnzbdVPN


Recommended Posts

On 4/13/2021 at 10:01 AM, binhex said:

ignore this, its a pia json issue, not related.

 

try switching to another endpoint, pia does have outages, it happens!.

i can not figure out how to change the end point i looked at that q28 but in that file i cant tell what to replace 

 

im getting that same error unable to successfully download pia json to generate token 

Link to comment
  • 2 weeks later...

Newbie question: I want to use SABnzbdVPN but as I don't have PIA VPN but Surfshark, I'm assuming I need to choose the 'custom' option, but no idea what to input from Key 7 onwards. I've found the manual username and password info on Surfshark (i.e. not the regular Surfshark login account username and password), but there's no other guidance specific to unRAID or even docker containers.

Is there a general tutorial on docker VPN's I can apply to my specific VPN?

At the moment the only guidance I can find on the Surfshark site is about general Linux installs,  and installing it into my router - which is an option but I'd prefer to use it on a per PC basis as it's mostly not needed by my family.

I did find a Github https://github.com/ilteoood/docker-surfshark docker but I've no idea how I'd go about installing a docker that isn't part of Community Applications and suspect I'll probably break something if I try. Maybe someone who understands these things can point me at how to take this info and use it with SABnzbdVPN? Thanks

P.S. I have done a support request with Surfshark, but strongly suspect I'll get a much more knowledgeable reply here.

Link to comment

Got an answer from Surfshark:

 

Quote

Here's where you can find the OpenVPN configuration files: https://my.surfshark.com/vpn/manual-setup/main

Also required login and password 'credentials' which is different from the regular username and password

VPN_PROV=custom

VPN_CLIENT=openvpn

STRICT_PORT_FORWARD=no

ENABLE_PRIVOXY=yes

LAN_NETWORK=192.168.1.0/24

NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

DEBUG=false

UMASK=000

PUID=0

PGID=0

That's what they sent me - I had no idea about the need to download the server location .opvn files or what to do with them, but eventually figured out that I could use Krusader to change the folder permissions on appdata/binhex-sabnzbdvpn/openvpn so I could drop the .opvn files from Surfshark into the folder via a rootshare (thanks to SpaceInvader video on setting up root share) and then change the folder permissions back again.

 

I'm not 100% sure it's working as it's supposed to but I did get a SABnzbd connection test as successful.

 

But I also got this in the log file in red:

2021-04-27 23:32:57 Options error: Unrecognized option or missing or extra parameter(s) in [PUSH-OPTIONS]:7: block-outside-dns (2.5.1)

 

Please let me know if I should do something? Or have done anything wrong? Otherwise hope it's useful to someone else using Surfshark

 

Link to comment
On 3/3/2021 at 3:44 PM, ceb0610 said:

Get the following every time I start SABnzbdvpn with wireguard. Container will start up with no internet access.

 


2021-03-03 18:39:49,441 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2021-03-03 18:39:49,444 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2021-03-03 18:39:49,469 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.41.151.89 dev wg0

2021-03-03 18:39:49,479 DEBG 'start-script' stderr output:
[#] ip link set mtu 8920 up dev wg0

2021-03-03 18:39:49,500 DEBG 'start-script' stderr output:
[#] ip -4 route add 10.0.0.0/8 dev wg0

2021-03-03 18:39:49,501 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2021-03-03 18:40:45,435 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2021-03-03 18:40:45,435 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2021-03-03 18:40:45,604 DEBG 'start-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2021-03-03 18:40:45,606 DEBG 'start-script' stdout output:
[info] Application does not require external IP address, skipping external IP address detection

2021-03-03 18:40:45,608 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2021-03-03 18:40:45,609 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

 Any help would be appreciated.

Did you ever find a solution to this issue?  I am experiencing the same issue here using Mullvad and Wireguard.  The strange thing is that the binhex-qbittorrentvpn docker works perfectly even using the same server.  Any insight on what could cause this @binhex?  The supervisord.log just shows the dns errors, the container starts without a hitch.

Link to comment
40 minutes ago, cardo said:

The strange thing is that the binhex-qbittorrentvpn docker works perfectly even using the same server. 

check the value you have defined for 'NAME_SERVERS' for both containers, are they different?, also the working container 'binhex-qbittorrentvpn' have you tried a restart recently, this may then fail, the two should be consistent as both are built from the same code base, just different apps, although again you could still be connecting to a different mullvad server even if you use the same hostname due to round-robin dns.

Link to comment
20 minutes ago, binhex said:

check the value you have defined for 'NAME_SERVERS' for both containers, are they different?, also the working container 'binhex-qbittorrentvpn' have you tried a restart recently, this may then fail, the two should be consistent as both are built from the same code base, just different apps, although again you could still be connecting to a different mullvad server even if you use the same hostname due to round-robin dns.

Yeah, restarting. broke the qbittorrent container as well.  As a test I dropped all of the DNS servers except for cloudflare's 1.1.1.1 and 1.0.0.1 and it still fails, but I can ping each from an unRAID shell.

Link to comment
Just now, cardo said:

Yeah, restarting. broke the qbittorrent container as well.  As a test I dropped all of the DNS servers except for cloudflare's 1.1.1.1 and 1.0.0.1 and it still fails, but I can ping each from an unRAID shell.

ok thats good its now consistent, then i would assume a vpn provider issue, try another mullvad endpoint.

Link to comment
1 minute ago, binhex said:

ok thats good its now consistent, then i would assume a vpn provider issue, try another mullvad endpoint.

Do you think the recent port forwarding change by Mullvad could cause this issue?  I had port forwarding before I recreated the containers (switched from unassigned devices to multiple cache pools) and when I downloaded the wireguard config files again, it still is including the port forward which now they've taken away.  I may be way off, but that's the only change on their end that I'm aware of.

Link to comment
2 minutes ago, cardo said:

Do you think the recent port forwarding change by Mullvad could cause this issue?  I had port forwarding before I recreated the containers (switched from unassigned devices to multiple cache pools) and when I downloaded the wireguard config files again, it still is including the port forward which now they've taken away.  I may be way off, but that's the only change on their end that I'm aware of.

i guess its possible, you dont of course require port forwarding at all for sabnzbd, worth investigating i think.

  • Like 1
Link to comment
19 hours ago, binhex said:

i guess its possible, you dont of course require port forwarding at all for sabnzbd, worth investigating i think.

It could be circumstantial, but going to Mullvad's site, deleting the port forward I had and downloading the Wireguard config files again resolved the issue for both containers.

  • Like 1
Link to comment

New user here, but fairly experienced with sabnzbd, openvpn & docker... just not assembled together before.

 

Just starting to get this set up using docker-compose.

 

I'm running docker rootless on linux (ubuntu 20.10) and when I set the PGID to the media (8675309) group, the container blows up with a chown error for every file created:

 

Attaching to ..., media_sabnzbdvpn
media_sabnzbdvpn | Created by...
media_sabnzbdvpn | ___.   .__       .__                   
media_sabnzbdvpn | \_ |__ |__| ____ |  |__   ____ ___  ___
media_sabnzbdvpn |  | __ \|  |/    \|  |  \_/ __ \\  \/  /
media_sabnzbdvpn |  | \_\ \  |   |  \   Y  \  ___/ >    < 
media_sabnzbdvpn |  |___  /__|___|  /___|  /\___  >__/\_ \
media_sabnzbdvpn |      \/        \/     \/     \/      \/
media_sabnzbdvpn |    https://hub.docker.com/u/binhex/
media_sabnzbdvpn | 
media_sabnzbdvpn | 2021-05-09 14:51:21.636822 [info] System information Linux ubuntu02_sabnzb 5.11.13-051113-generic #202104101231 SMP Sat Apr 10 12:34:46 UTC 2021 x86_64 GNU/Linux
media_sabnzbdvpn | 2021-05-09 14:51:21.652536 [info] OS_ARCH defined as 'x86-64'
media_sabnzbdvpn | 2021-05-09 14:51:21.668201 [info] PUID defined as '1000'
media_sabnzbdvpn | 2021-05-09 14:51:21.695671 [info] PGID defined as '8675309'
media_sabnzbdvpn | 2021-05-09 14:51:21.716406 [info] UMASK defined as '002'
media_sabnzbdvpn | 2021-05-09 14:51:21.731788 [info] Permissions already set for volume mappings
media_sabnzbdvpn | 2021-05-09 14:51:21.748578 [info] Deleting files in /tmp (non recursive)...
media_sabnzbdvpn | 2021-05-09 14:51:21.766758 [info] VPN_ENABLED defined as 'no'
media_sabnzbdvpn | 2021-05-09 14:51:21.780726 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
media_sabnzbdvpn | chown: changing ownership of '/usr/lib/sabnzbd/GPL2.txt': Invalid argument
media_sabnzbdvpn | chown: changing ownership of '/usr/lib/sabnzbd/ISSUES.txt': Invalid argument
media_sabnzbdvpn | chown: changing ownership of '/usr/lib/sabnzbd/tests/test_encoding.py': Invalid argument
media_sabnzbdvpn | chown: changing ownership of '/usr/lib/sabnzbd/tests/test_newsunpack.py': Invalid argument
media_sabnzbdvpn | chown: changing ownership of '/usr/lib/sabnzbd/tests/testhelper.py': Invalid argument


Here's my docker-compose.yml:

 

version: '3'

services:  
  sabnzb:
    image: binhex/arch-sabnzbdvpn
    container_name: media_sabnzbdvpn
    hostname: ubuntu02_sabnzb
    ports:
      - 8080:8080
      - 8090:8090
      - 8118:8118
        #restart: unless-stopped
    labels: 
      - diun.enable=true
    environment: 
      - VPN_ENABLED=no
      - VPN_USER=X
      - VPN_PASS=Y
      - VPN_PROV=custom
      - VPN_CLIENT=openvpn
      - VPN_OPTIONS=x
      - STRICT_PORT_FORWARD=no
      - ENABLE_PRIVOXY=yes
      - LAN_NETWORK=172.16.1.0/24
      - NAME_SERVERS=1.1.1.1
      - DEBUG=true
      - UMASK=002
      - PUID=1000
      - PGID=8675309

    volumes:
      - ./sab/data:/data
      - ./sab/config:/config
      - /etc/localtime:/etc/localtime:ro

 

I assume this is a noob config mistake; can someone suggest what the error is?

 

thanks much... 

Link to comment
  • 2 weeks later...
Posted (edited)

Something's broken my SAB after months of flawless running tonight i get 'insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory'

 

Anyone any ideas?

 

I have no torrenting, pure usenet discussions for me.

 

Nothing has changed and i've no idea how to sort this iptable_mango.ko out .... it's preventing anything from moving on in the setup chain.

 

Edit ... I called the fix command shown in the San log and managed to get past the operable missing problem but am now seeing the same problems as others in that my pia JSON file is unobtainable so San won't start with wireguard. I suppose I have to sit this out for someone to identify the problem. 

Edited by superloopy1
Update
Link to comment

Hi Everyone,

 

This noob could use a little help.  I was able to get the binhex-sabnzbdvpn setup and have it working as expected with wireguard.  I tried to set up binhex-privoxy but the docker won't download the json to generate the wireguard token:


 

2021-05-19 16:09:03,674 DEBG 'start-script' stdout output:
[crit] Unable to successfully download PIA json to generate token for wireguard, exiting script...

2021-05-19 16:09:03,674 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23174333001936 for <Subprocess at 23174333003664 with name start-script in state RUNNING> (stdout)>
2021-05-19 16:09:03,674 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23174332630112 for <Subprocess at 23174333003664 with name start-script in state RUNNING> (stderr)>
2021-05-19 16:09:03,674 INFO exited: start-script (exit status 1; not expected)
2021-05-19 16:09:03,674 DEBG received SIGCHLD indicating a child quit
2021-05-19 16:26:48,764 WARN received SIGTERM indicating exit request
2021-05-19 16:26:48,764 DEBG killing watchdog-script (pid 152) with signal SIGTERM
2021-05-19 16:26:48,764 INFO waiting for watchdog-script to die
2021-05-19 16:26:48,802 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23174332630880 for <Subprocess at 23174332630208 with name watchdog-script in state STOPPING> (stdout)>
2021-05-19 16:26:48,803 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23174332665136 for <Subprocess at 23174332630208 with name watchdog-script in state STOPPING> (stderr)>
2021-05-19 16:26:48,803 INFO stopped: watchdog-script (terminated by SIGTERM)
2021-05-19 16:26:48,803 DEBG received SIGCHLD indicating a child quit

 

It performs the 12 attempts and ends with the info above. Appreciate the help!

Link to comment
7 minutes ago, Twinkie0101 said:

Hi Everyone,

 

This noob could use a little help.  I was able to get the binhex-sabnzbdvpn setup and have it working as expected with wireguard.  I tried to set up binhex-privoxy but the docker won't download the json to generate the wireguard token:


 


2021-05-19 16:09:03,674 DEBG 'start-script' stdout output:
[crit] Unable to successfully download PIA json to generate token for wireguard, exiting script...

2021-05-19 16:09:03,674 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23174333001936 for <Subprocess at 23174333003664 with name start-script in state RUNNING> (stdout)>
2021-05-19 16:09:03,674 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23174332630112 for <Subprocess at 23174333003664 with name start-script in state RUNNING> (stderr)>
2021-05-19 16:09:03,674 INFO exited: start-script (exit status 1; not expected)
2021-05-19 16:09:03,674 DEBG received SIGCHLD indicating a child quit
2021-05-19 16:26:48,764 WARN received SIGTERM indicating exit request
2021-05-19 16:26:48,764 DEBG killing watchdog-script (pid 152) with signal SIGTERM
2021-05-19 16:26:48,764 INFO waiting for watchdog-script to die
2021-05-19 16:26:48,802 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23174332630880 for <Subprocess at 23174332630208 with name watchdog-script in state STOPPING> (stdout)>
2021-05-19 16:26:48,803 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23174332665136 for <Subprocess at 23174332630208 with name watchdog-script in state STOPPING> (stderr)>
2021-05-19 16:26:48,803 INFO stopped: watchdog-script (terminated by SIGTERM)
2021-05-19 16:26:48,803 DEBG received SIGCHLD indicating a child quit

 

It performs the 12 attempts and ends with the info above. Appreciate the help!

 

I'm also experiencing this issue. I suspect it's related to PIA's WireGuard API, as my OpenVPN clients are working fine. Guess the only thing we can do is wait it out...?

Link to comment
9 minutes ago, goose_ws said:

 

I'm also experiencing this issue. I suspect it's related to PIA's WireGuard API, as my OpenVPN clients are working fine. Guess the only thing we can do is wait it out...?

The weird thing is my sab instance is working fine with wireguard with the default endpoint.

Link to comment
5 minutes ago, Twinkie0101 said:

The weird thing is my sab instance is working fine with wireguard with the default endpoint.

What endpoint are you using?

 

Does it continue to work if you restart your container?

Link to comment

this morning SAB w/ wireguard would not connect even though it has been working fine for months.  so then changed back to OVPN and worked flawlessly but slower.  kept getting this error:  "Unable to successfully download PIA json to generate token..."  will retest tomorrow.  suspect PIA was messing server side.

Link to comment
4 hours ago, DoItMyselfToo said:

this morning SAB w/ wireguard would not connect even though it has been working fine for months.  so then changed back to OVPN and worked flawlessly but slower.  kept getting this error:  "Unable to successfully download PIA json to generate token..."  will retest tomorrow.  suspect PIA was messing server side.

Same here ....

Link to comment
11 hours ago, superloopy1 said:

Something's broken my SAB after months of flawless running tonight i get 'insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory'

 

Anyone any ideas?

 

I have no torrenting, pure usenet discussions for me.

 

Nothing has changed and i've no idea how to sort this iptable_mango.ko out .... it's preventing anything from moving on in the setup chain.

 

Edit ... I called the fix command shown in the San log and managed to get past the operable missing problem but am now seeing the same problems as others in that my pia JSON file is unobtainable so San won't start with wireguard. I suppose I have to sit this out for someone to identify the problem. 

Just checked and it's working aok again. I don't have any Privoxy routing at all. That's new to me. Should I be using Privoxy, what protection over and above using binhexs app does it provide?

Link to comment

Hello -

 

I want to start by saying I am new to all of this fun stuff Unraid has to offer. I recently download this docker and had everything running smoothly. I did the ultimate no no and was messing around with the settings. Without knowing exactly what I did I am no longer allowed to open the WEBUI. Its telling me "access denied". I looked around in console but I am afraid I will mess something up worse. Can anyone help me out?

 

Thanks!!!

Link to comment
4 hours ago, Drew4 said:

Hello -

 

I want to start by saying I am new to all of this fun stuff Unraid has to offer. I recently download this docker and had everything running smoothly. I did the ultimate no no and was messing around with the settings. Without knowing exactly what I did I am no longer allowed to open the WEBUI. Its telling me "access denied". I looked around in console but I am afraid I will mess something up worse. Can anyone help me out?

 

Thanks!!!

it will depend on what you 'messed with' as to the solution, you can see your set options in the file /config/sabnzbd.ini (where /config is a mapping to a host path location), if you cant work out what it is you set then you can simply delete all files and folder for /config for this container and restart it to get you back to a clean state.

Link to comment

Hi Binhex.

 

Recently, the sabnzbd container started griping about unrar version 0.00.

I noticed that the options to unpack + delete no longer work and downloads are not be extracted.

 

I've validated that the container has `par2cmdline` as well as `unrar`.

 

Do you know what this issue is?

I can run unrar from inside the container no issue, but sab seems to think I have version 0.00 and it wont extract.

 

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.