Jump to content
binhex

[Support] binhex - SABnzbdVPN

757 posts in this topic Last Reply

Recommended Posts

On 4/20/2019 at 5:21 AM, binhex said:

I would guess whatever is classifying your traffic as OpenVPN failed to detect it correctly, possibly triggered by VPN switching endpoint, confident it isn't a leak.

Sent from my EML-L29 using Tapatalk
 

Thank you Bin.  I've enabled the embedded VPN again and set Radar and Sonar with Privoxy.  Appreciate the amount of time you spend supporting users!  

Share this post


Link to post
Posted (edited)

I've been running sabnzbdvpn successfully for some time now, my topspeed while downloading with openvpn enabled in the docker, was about 10MB/s. Few weeks ago i've replaced my old router with PFSense, running on an UNRAID VM, and i configured openvpn there, so that every connection within my network, now runs over the vpn by default. So i have no need for the vpn in sabnzbdvpn anymore, so i disabled it in the docker config (VPN_ENABLED=no).

 

But now i notice that when i'm downloading, the download speed has tripled, from 10MB/s to almost 30MB/s... and yes, it is over vpn. How is it that openvpn within the docker is so much slower then the same openvpn within PFSense? Both are running on the same hardware...?

Edited by jowi

Share this post


Link to post
20 hours ago, jowi said:

Few weeks ago i've replaced my old router with PFSense

that will most probably be why, user grade routers (and even small business class routers) are crap, pfsense will give you significantly better throughput, i bet if you were to re-enable the container you would find it would perform just as well.

Share this post


Link to post

Jowi could you comfirm this? as i am starting to wonder if i need to get a different router

Share this post


Link to post
5 minutes ago, 08deanr said:

Jowi could you comfirm this? as i am starting to wonder if i need to get a different router

What kind of router are you using today 08deanr?  

 

Share this post


Link to post
2 hours ago, binhex said:

that will most probably be why, user grade routers (and even small business class routers) are crap, pfsense will give you significantly better throughput, i bet if you were to re-enable the container you would find it would perform just as well.

I don't think i made myself clear...

 

In both cases, i'm using pfsense on unraid.... so i'm not talking about the performance of the netgear router, purely the performance of sabnzbdvpn with it's vpn enabled, and sabnzbdvpn with it's vpn disabled, but openvpn on pfsense... so:

 

1. pfsense NO openvpn - sabnzbdvpn docker with vpn ENABLED: 10MB/s download speed

2. pfsense WITH openvpn enabled - sabnzbdvpn docker with vpn DISABLED: 30MB/s

Share this post


Link to post
2 hours ago, BeerEngineer said:

What kind of router are you using today 08deanr?  

 

I have an ASUS R6400 currently doing everything ( Router/Firewall/DHCP)

Share this post


Link to post
14 hours ago, jowi said:

pfsense WITH openvpn enabled - sabnzbdvpn docker with vpn DISABLED: 30MB/s

are you using the exact same ovpn config file in both cases?, as in for pfense and for the container? connecting to different endpoints or using different ciphers can make a difference, take a look at Q6. from the following link, the GCM part might be of interest:-

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

 

Share this post


Link to post
Posted (edited)

I saw there was an update today so i updated.

 

Now Radarr and Sonarr cannot connect to SAB, I have ran the same configuration for more then a year and never had this problem.

 

Any ideas what i might check?

 

Here are logs if this might help

 

2019-05-03 20:00:13,740 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2019-05-03 20:00:13,771 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 22497825666760 for <Subprocess at 22497825703192 with name privoxy-script in state RUNNING> (stdout)>
2019-05-03 20:00:13,771 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 22497825666688 for <Subprocess at 22497825703192 with name privoxy-script in state RUNNING> (stderr)>
2019-05-03 20:00:13,771 INFO exited: privoxy-script (exit status 0; expected)
2019-05-03 20:00:13,772 DEBG received SIGCLD indicating a child quit
2019-05-03 20:00:43,694 DEBG 'watchdog-script' stdout output:
[warn] Wait for SABnzbd process to start aborted, too many retries
[warn] Showing output from command before exit...

2019-05-03 20:00:44,368 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22497825669064 for <Subprocess at 22497825702040 with name watchdog-script in state RUNNING> (stdout)>
2019-05-03 20:00:44,368 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22497825666832 for <Subprocess at 22497825702040 with name watchdog-script in state RUNNING> (stderr)>
2019-05-03 20:00:44,368 INFO exited: watchdog-script (exit status 1; not expected)
2019-05-03 20:00:44,369 DEBG received SIGCLD indicating a child quit

Edited by Viperkc

Share this post


Link to post
1 hour ago, Viperkc said:

I saw there was an update today so i updated.

 

Now Radarr and Sonarr cannot connect to SAB, I have ran the same configuration for more then a year and never had this problem.

 

Any ideas what i might check?

 

Here are logs if this might help

 

2019-05-03 20:00:13,740 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2019-05-03 20:00:13,771 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 22497825666760 for <Subprocess at 22497825703192 with name privoxy-script in state RUNNING> (stdout)>
2019-05-03 20:00:13,771 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 22497825666688 for <Subprocess at 22497825703192 with name privoxy-script in state RUNNING> (stderr)>
2019-05-03 20:00:13,771 INFO exited: privoxy-script (exit status 0; expected)
2019-05-03 20:00:13,772 DEBG received SIGCLD indicating a child quit
2019-05-03 20:00:43,694 DEBG 'watchdog-script' stdout output:
[warn] Wait for SABnzbd process to start aborted, too many retries
[warn] Showing output from command before exit...

2019-05-03 20:00:44,368 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22497825669064 for <Subprocess at 22497825702040 with name watchdog-script in state RUNNING> (stdout)>
2019-05-03 20:00:44,368 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22497825666832 for <Subprocess at 22497825702040 with name watchdog-script in state RUNNING> (stderr)>
2019-05-03 20:00:44,368 INFO exited: watchdog-script (exit status 1; not expected)
2019-05-03 20:00:44,369 DEBG received SIGCLD indicating a child quit

I seem to be getting the same errors... IM able to connected to it without the VPN. SAB is able to still download just nothing is getting thou the via the proxy address provided in the setup.

Share this post


Link to post
2 hours ago, Viperkc said:

I saw there was an update today so i updated.

 

Now Radarr and Sonarr cannot connect to SAB, I have ran the same configuration for more then a year and never had this problem.

 

Any ideas what i might check?

 

Here are logs if this might help

 

2019-05-03 20:00:13,740 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

2019-05-03 20:00:13,771 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 22497825666760 for <Subprocess at 22497825703192 with name privoxy-script in state RUNNING> (stdout)>
2019-05-03 20:00:13,771 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 22497825666688 for <Subprocess at 22497825703192 with name privoxy-script in state RUNNING> (stderr)>
2019-05-03 20:00:13,771 INFO exited: privoxy-script (exit status 0; expected)
2019-05-03 20:00:13,772 DEBG received SIGCLD indicating a child quit
2019-05-03 20:00:43,694 DEBG 'watchdog-script' stdout output:
[warn] Wait for SABnzbd process to start aborted, too many retries
[warn] Showing output from command before exit...

2019-05-03 20:00:44,368 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22497825669064 for <Subprocess at 22497825702040 with name watchdog-script in state RUNNING> (stdout)>
2019-05-03 20:00:44,368 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22497825666832 for <Subprocess at 22497825702040 with name watchdog-script in state RUNNING> (stderr)>
2019-05-03 20:00:44,368 INFO exited: watchdog-script (exit status 1; not expected)
2019-05-03 20:00:44,369 DEBG received SIGCLD indicating a child quit

I'm having the exact same issue.  Literally, binhex-SABnzbvpn, binhex-NZBHydra2, and binhex-sonarr were working fine.  After I updated SAB this afternoon, same message as above and no communication between Hydra2, Sonarr, and SAB.  I did not make any configuration changes.  And I checked all settings in each app to confirm.

 

Share this post


Link to post

The same is happening to me. It seems that it's a problem with privoxy/vpn, because using the proxy on the web browser gives the error of connection refused, not accepting requests on port 8118.

Share this post


Link to post

I will take a look tonight guys, if you are desperate then roll back using specific tagged version.

Sent from my EML-L29 using Tapatalk

Share this post


Link to post

OK thanks,  I rolled back one version and all is working fine now. Will check later for an update

Share this post


Link to post

Which update do you guys have issues with? I'm at sabnzbdvpn 2.3.8 [0dd1f64] updated yesterday, no issues at all.

Share this post


Link to post
Posted (edited)

Seeing the same here.  Thanks everyone...thought i was crazy

 

2.3.8 [0dd1f64]

Edited by beaverly72

Share this post


Link to post
4 hours ago, binhex said:

I will take a look tonight guys, if you are desperate then roll back using specific tagged version.

Sent from my EML-L29 using Tapatalk
 

Thanks, Binhex!

Share this post


Link to post
Posted (edited)
3 hours ago, jowi said:

Which update do you guys have issues with? I'm at sabnzbdvpn 2.3.8 [0dd1f64] updated yesterday, no issues at all.

That version is the working version. If you updated yesterday you would be on 2.3.8 (daf9f50) 

 

This is the version we had problems with.

 

I reverted back to 0dd1f64 and it works fine.

Edited by Viperkc

Share this post


Link to post

Hi,

Also had the same issue here, Radarr and Sonarr could't communicate with SABnzbd. Also reverted back to 2.3.8-1-01 and problem is gone.

Share this post


Link to post

I hate to ask...can anyone let me know how to rollback. New to this and I don’t see a version key pointing to latest.  I would attempt to append to the repo url, but not quite sure what I would use for the version?

Share this post


Link to post
58 minutes ago, beaverly72 said:

I hate to ask...can anyone let me know how to rollback. New to this and I don’t see a version key pointing to latest.  I would attempt to append to the repo url, but not quite sure what I would use for the version?

Edit the container and paste this under repository:  binhex/arch-sabnzbdvpn:2.3.8-1-01

 

When he announces the fix for be sure to change it back to binhex/arch-sabnzbdvpn

 

This way you get furture updates

 

 

Share this post


Link to post

ok guys, spotted the issue. it was a legacy bug that the additional logging picked up causing the exit of sabnzbd (even though it was running). sadly i cannot currently build a new image with the fix as docker hub is currently in maintenance mode and looks like it wont back online for approx another 8 hours, so i will have to press the button in the morning.

Share this post


Link to post
18 hours ago, Viperkc said:

Edit the container and paste this under repository:  binhex/arch-sabnzbdvpn:2.3.8-1-01

 

When he announces the fix for be sure to change it back to binhex/arch-sabnzbdvpn

 

This way you get furture updates

 

 

Thanks that worked, but very finicky. If I just updated the container it would fail and break.  This would orphan the container and require me to download sabnzbd again.  Only if I inserted that string during install would it work.  Unfortunately this would cause me to configure all of my settings again. Not a huge deal, but I am assuming that’s not how it went for everyone.

Share this post


Link to post

The new image has built so if you now pull down latest it should work as expected

Sent from my EML-L29 using Tapatalk

Share this post


Link to post

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.