[Support] binhex - SABnzbdVPN


Recommended Posts

Same issue here after auto update of SABnzbdVPN was performed.

 

All I see in the log are the following warnigs (no errors)...

 

Quote

2020-12-03 00:42:11,620 DEBG 'start-script' stdout output:
2020-12-03 00:42:11 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.

Quote

2020-12-03 00:42:11,620 DEBG 'start-script' stdout output:
2020-12-03 00:42:11 WARNING: file 'credentials.conf' is group or others accessible

Quote

2020-12-03 00:42:11,620 DEBG 'start-script' stdout output:
2020-12-03 00:42:11 WARNING: --ping should normally be used with --ping-restart or --ping-exit

 

I am using Unraid 6.8.3 and Sab with custom VPN via openvpn.

Link to comment
19 minutes ago, numblock699 said:

WebUI points to wrong port?

 

Should be no port issue...

 

Quote

2020-12-03 00:42:15,008 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process is listening on port 8080

 

And btw... Sab is still downloading, but not accessible via Web UI.

Edited by Leo007
Link to comment
1 hour ago, shutterbug said:

Thanks, I went ahead and stepped through #19 and restarted the docker.  I still can't load the webpage and the logs still show the same warning I posted above.

 

try switching to wireguard.

 

1.   Right click "Edit" the SABnzbdvpn container.

2.  Add "variable" with the following information.
SAB_Wireguard.jpeg.5758c12e2f079fba027ce375b46472c5.jpeg

 

3.  Click apply to pulldown the container change.  The default PIA endpoint for this container is the Netherlands.  You can also pick any other end point from here.

 

4.  When changing endpoints, shutdown SAB.

5.  Navigate to your /appdata/binhex-sabnzbdvpn/wireguard/wg0.conf .

6.  Open "wg0.conf" in a text editor, like Atom, the open source text editor.

7.  Change underlined part below to the appropriate endpoint from the link above based on country/location.

wireguard_config.jpeg.5dc703b138a8c06a255af3e574d8c2fc.jpeg

 

8.  Click "Save" in your text editor.

9.  Restart SAB.

 

Link to comment
18 minutes ago, DoItMyselfToo said:

try switching to wireguard.

 

1.   Right click "Edit" the SABnzbdvpn container.

2.  Add "variable" with the following information.
SAB_Wireguard.jpeg.5758c12e2f079fba027ce375b46472c5.jpeg

 

3.  Click apply to pulldown the container change.  The default PIA endpoint for this container is the Netherlands.  You can also pick any other end point from here.

 

4.  When changing endpoints, shutdown SAB.

5.  Navigate to your /appdata/binhex-sabnzbdvpn/wireguard/wg0.conf .

6.  Open "wg0.conf" in a text editor, like Atom, the open source text editor.

7.  Change underlined part below to the appropriate endpoint from the link above based on country/location.

wireguard_config.jpeg.5dc703b138a8c06a255af3e574d8c2fc.jpeg

 

8.  Click "Save" in your text editor.

9.  Restart SAB.

 

Thanks for this.  So I went through your steps and it got rid of the warning in the logs, but now I have an error and still can't access the web interface.  The error in the logs is:

2020-12-02 18:00:18,435 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 4, column 0

 

the only thing that differed from your instructions was that the new variable asked for both a VALUE and a DEFAULT VALUE.  I put 'wireguard' in VALUE and left DEFAULT VALUE empty (I also tried just 'wireguard' in the DEFAULT VALUE field, same impact)

 

image.thumb.png.218ff340b5d5c39ad22ef6afe7b12d19.png

Edited by shutterbug
Link to comment
9 minutes ago, shutterbug said:

Thanks for this.  So I went through your steps and it got rid of the warning in the logs, but now I have an error and still can't access the web interface.  The error in the logs is:

2020-12-02 18:00:18,435 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 4, column 0

 

the only thing that differed from your instructions was that the new variable asked for both a VALUE and a DEFAULT VALUE.  I put 'wireguard' in VALUE and left DEFAULT VALUE empty (I also tried just 'wireguard' in the DEFAULT VALUE field, same impact)

you're looking at your "edit" screen in advanced mode, that's why you're seeing the "default value" field.  it doesn't matter.

 

are you seeing "AUTH FAILED" in your logs?

 

also, are you using your main username and password in SAB that you would use to login to the PIA website?  that's the one you want to use.

Edited by DoItMyselfToo
Link to comment
3 minutes ago, DoItMyselfToo said:

you're looking at your "edit" screen in advanced mode, that's why you're seeing the "default value" field.  it doesn't matter.

 

are you seeing "AUTH FAILED" in your logs?

No auth errors, the wireguard interface appears to come up and I receive an IP:

 

2020-12-02 18:12:57,180 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2020-12-02 18:12:57,189 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2020-12-02 18:12:57,194 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2020-12-02 18:12:57,195 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2020-12-02 18:12:57,206 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.x.x.x dev wg0

2020-12-02 18:12:57,210 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2020-12-02 18:12:57,227 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2020-12-02 18:12:57,228 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2020-12-02 18:12:57,229 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2020-12-02 18:12:57,230 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2020-12-02 18:12:57,233 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2020-12-02 18:12:57,234 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2020-12-02 18:12:57,236 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2020-12-02 18:12:58,327 DEBG 'start-script' stdout output:
[info] Application does not require external IP address, skipping external IP address detection

2020-12-02 18:12:58,328 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2020-12-02 18:12:58,329 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2020-12-02 18:12:58,382 DEBG 'watchdog-script' stdout output:
[info] SABnzbd not running

2020-12-02 18:12:58,382 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2020-12-02 18:12:59,192 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process started
[info] Waiting for SABnzbd process to start listening on port 8080...

2020-12-02 18:12:59,403 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process is listening on port 8080

Link to comment
6 minutes ago, shutterbug said:

No auth errors, the wireguard interface appears to come up and I receive an IP:

 

2020-12-02 18:12:57,180 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2020-12-02 18:12:57,189 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2020-12-02 18:12:57,194 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2020-12-02 18:12:57,195 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2020-12-02 18:12:57,206 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.x.x.x dev wg0

2020-12-02 18:12:57,210 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2020-12-02 18:12:57,227 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2020-12-02 18:12:57,228 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2020-12-02 18:12:57,229 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2020-12-02 18:12:57,230 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2020-12-02 18:12:57,233 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2020-12-02 18:12:57,234 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2020-12-02 18:12:57,236 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2020-12-02 18:12:58,327 DEBG 'start-script' stdout output:
[info] Application does not require external IP address, skipping external IP address detection

2020-12-02 18:12:58,328 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2020-12-02 18:12:58,329 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2020-12-02 18:12:58,382 DEBG 'watchdog-script' stdout output:
[info] SABnzbd not running

2020-12-02 18:12:58,382 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2020-12-02 18:12:59,192 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process started
[info] Waiting for SABnzbd process to start listening on port 8080...

2020-12-02 18:12:59,403 DEBG 'watchdog-script' stdout output:
[info] SABnzbd process is listening on port 8080

seems like SAB should be running.  in mine after this is indication that privoxy is running.  are you running privoxy?  also have you cleared your browser cache?  and then restarted your entire *arr's stack?

 

Link to comment
1 minute ago, DoItMyselfToo said:

seems like SAB should be running.  in mine after this is indication that privoxy is running.  are you running privoxy?  also have you cleared your browser cache?  and then restarted your entire *arr's stack?

 

both sonarr and radarr show that it is running, the checks from those tools pass. 

 

I've tried to hit the web interface from multiple browsers and incognito mode, all time out.

 

Unraid has been rebooted, problem remains.

Link to comment
37 minutes ago, shutterbug said:

both sonarr and radarr show that it is running, the checks from those tools pass. 

 

I've tried to hit the web interface from multiple browsers and incognito mode, all time out.

 

Unraid has been rebooted, problem remains.

i would go over all your container variables, including the network variable.  comb the logs.

Link to comment
7 hours ago, shutterbug said:

both sonarr and radarr show that it is running, the checks from those tools pass. 

 

I've tried to hit the web interface from multiple browsers and incognito mode, all time out.

 

Unraid has been rebooted, problem remains.

i would suspect LAN_NETWORK is not defined correctly, but without a log im shooting in the dark, see Q4 for help with LAN_NETWORK:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Link to comment
3 hours ago, shutterbug said:

Sure enough, enabling privoxy solved it for me as well.  I've never had this enabled previously, as you noted, worked fine before.

Thanks!

I was having the same issue and enabling Privoxy worked for me too. Never had to have this enabled until the docker pull from today. 

Link to comment
6 hours ago, numblock699 said:

Enabling privoxy seems to have solved it for me, it used to run fine disabled b4.

Yep - I'll add another one to the list.  Was timing out on the web ui and enabling privoxy solved that.  After getting it up and running, I tried the old "turn it off and on again" on privoxy, and having it off results in no web ui.  Funky.

Link to comment
6 hours ago, numblock699 said:

Enabling privoxy seems to have solved it for me, it used to run fine disabled b4.

 

4 hours ago, shutterbug said:

Sure enough, enabling privoxy solved it for me as well.  I've never had this enabled previously, as you noted, worked fine before.

Thanks!

 

1 hour ago, cardo said:

I was having the same issue and enabling Privoxy worked for me too. Never had to have this enabled until the docker pull from today. 

 

1 minute ago, noja said:

Yep - I'll add another one to the list.  Was timing out on the web ui and enabling privoxy solved that.  After getting it up and running, I tried the old "turn it off and on again" on privoxy, and having it off results in no web ui.  Funky.

Hi guys, ive spotted the issue, it was due to a merge removing input lines for iptable rules, this has now been corrected, feel free to disable privoxy and pull latest (just built!) to fix the issue.

  • Thanks 1
Link to comment
1 hour ago, binhex said:

 

 

 

Hi guys, ive spotted the issue, it was due to a merge removing input lines for iptable rules, this has now been corrected, feel free to disable privoxy and pull latest (just built!) to fix the issue.

Thank you very much. Works fine again!

Link to comment
4 hours ago, binhex said:

 

 

 

Hi guys, ive spotted the issue, it was due to a merge removing input lines for iptable rules, this has now been corrected, feel free to disable privoxy and pull latest (just built!) to fix the issue.

I must be an idiot, because I've forced an update to the docker, and still cannot access it.  Log attached, from after turning off VPN option.  Have tried privoxy on/off.  Port should be 8081, not sure why it says 8080

supervisord.log

Edited by columbuscoltsfan
Link to comment

Thank you!

 

Is there any reason I wouldn't want to run privoxy?  I never had it on before, but after enabling it and reading up on it, I reconfigured sonarr and radarr to pull from the privoxy port and this seems like an ideal solution.  Just wondering if there are any cons to running it? (I don't use SABnzbd outside of my LAN)

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.