[Support] binhex - SABnzbdVPN


Recommended Posts

Resolved, "iptable_mangle module" was not present on host....but I don't know, how it was working for like a month and then decided to stop working.....anyway great docker, love it, 11/10 :)

 

For the other: I did the following:
on Q2 I scrolled to "Q2. I can't seem to access the webui from outside my LAN, why is this?" and did the descriped steps.

 

echo "# force iptable mangle module to load (required for *vpn dockers)" >> /boot/config/go
echo "/sbin/modprobe iptable_mangle" >> /boot/config/go 

and reboot

 

Original Post:

 

 

Hey,

 

TL;DR: No access to SabNZBD interface when VPN dockersetting is set to "yes", but VPN works.

 

I have the following problem: 2 days or so agao everything worked fine and I could easily access the Webinterface ob sabnzdb, but since today in the morning, I can't access it anymore. I've done some troubleshooting and think it has something to do with my VPN settings, because if i disable the VPN in the Docker settings in Unraid, I can access it, but when I re-enable it, no response from SabNZBD. But the weirdes thing is, when the VPN is activated and I can't reach the Webinterface, the API still works and Radarr/Sonarr etc can send NZB to SabNZBD and it will even download them. Sooooo I'm not sure where the Problem is. 

The only thing I changed since yesterday is adding a new NIC to the system and I'm trying to get Link aggreation to work....but I don't now, if it's related, cause when the VPN settings ist set to "no", I can access the Webinterface.
 

Thanks

 

Edit: I've looked into the Debug log and found out, that SabNZBD itself is not starting.....but I think, thats a false alarm, cause the weirdes thing is, that Sonarr and Radarr still can communicate via the API with Sab.....but the webinterface is not loading

 

Edit 2: Ahh, RTFM....i know....and now I've read the FAQ for VPN=yes and no GUI......the Problem is, that when I use the network br0, then everything works (the VPN also(Sab is reporting the VPN IP)), but not in brige mode....but I will dig further in it

 

Edit 3: Sooo I installed OpenVPN on my personal machine and loaded the exakt same copy from the Sab Folder and the credentails.conf into the config folder of openVPN, startet the connection and connected correctly (myip.is showed the VPN IP). So I think the VPN isn't the problem. I also removed the 2nd NIC (thought this was the issue), but no GUI. I don't how to fix this problem. From one to another day it doesn't work anymore.

 

Edit 4: Yeah, still the same Problem. I've found out, that the VPN is not the Problem, cause I enterd the folllowing in the console and get the VPN IP adress:

curl https://ipinfo.io/ip

I don't know the problem, maybe a broken IPTable? Still looking for a solution.

 

LOG: unimportant!

2019-02-09 18:41:40,798 DEBG 'watchdog-script' stdout output:
[info] Attempting to start SABnzbd...

[...]

2019-02-09 18:41:42,320 DEBG 'watchdog-script' stdout output:
[debug] Waiting for SABnzbd process to start...

2019-02-09 18:41:43,324 DEBG 'watchdog-script' stdout output:
[debug] Waiting for SABnzbd process to start...

2019-02-09 18:41:44,327 DEBG 'watchdog-script' stdout output:
[debug] Waiting for SABnzbd process to start...

[...]

2019-02-09 18:42:11,428 DEBG 'watchdog-script' stdout output:
[warn] Wait for SABnzbd process to start aborted
[info] Waiting for SABnzbd process to start listening on port 8080...

 

Edited by tobix
I didn't RTFM; Still not working after reading, resolved
Link to comment

Greetings community, I have configured the sabnzbdvpn and have configured privoxy for sickchill. I cannot, however access anything on http://sickchill.github.io/ through the privoxy. I have a feeling it is blocking it, I am trying to access a json file as well as a text file and keep getting blocked. It works when not going through the privoxy.


I am fairly new to all of this but does anybody know how to configure the privoxy (and which file/lines to add in configs) to allow this traffic?

 

Thank you in advance for any assistance you can provide.

-Fizz

Link to comment

Apologies if this is the wrong thread , but a support link in CA sent me here.

 

Just found binhex-privoxyvpn in CA, and from what I can tell it's fairly new.  Is it the "VPN" part of the other binhex containers (ie, binhex-delugevpn without the deluge)?  If so, this might come in handy - I've raised before that I've wanted to stop a container, but couldn't because VPN traffic was going through it.

 

If so, I'm guessing deluge/rtorrent can be set to use a proxy and have VPN turned off?

 

Link to comment
1 hour ago, Cessquill said:

Apologies if this is the wrong thread , but a support link in CA sent me here.

 

Just found binhex-privoxyvpn in CA, and from what I can tell it's fairly new.  Is it the "VPN" part of the other binhex containers (ie, binhex-delugevpn without the deluge)?  If so, this might come in handy - I've raised before that I've wanted to stop a container, but couldn't because VPN traffic was going through it.

 

If so, I'm guessing deluge/rtorrent can be set to use a proxy and have VPN turned off?

 

Wrong thread, but I haven't seen the correct thread get created yet, so this will do.

 

AFAIK, yes this is just the VPN/privoxy piece without the download client, be it nzb or torrent.

 

I don't think torrent clients can be tunnelled through a http proxy, which is what privoxy is.

 

What you can do, is install this as your privoxy gateway, so you can stop your vpn enabled downloader without disturbing the proxy. However, this means that your vpn account will have another constant connection. I don't know the limits on the various VPN providers.

Link to comment
18 minutes ago, jonathanm said:

What you can do, is install this as your privoxy gateway, so you can stop your vpn enabled downloader without disturbing the proxy. However, this means that your vpn account will have another constant connection. I don't know the limits on the various VPN providers.

Thanks - that's what I was thinking.  PIA has a 5 connection limit, so it's not the end of the world using 2 or 3 of those on Unraid.  Would rather use as few as possible though.

 

(the support link in CA currently points to here - assuming a new topic will be created and linked in due course)

Link to comment

Binhex-

I am having an issue with two containers using binhex-sabnzbdvpn privoxy with PIA. For what ever reason binhex-deluge and binhex-hydra seem to ignore proxy settings. Currently I have Radarr, Sonarr, Jackett and even some PC's utilizing SAB's privoxy. Today, I received a warning from my ISP about torrent traffic. It turns out even with Deluge and Hydra having same proxy setup as everything else, they connect to the internet even when sabnzbdvpn is off. In fact even with SAB running they do not seem to use PIA VPN. No other dockers or PC's can do this. No SAB = no internet. Any thoughts? Today I tried the new binhex-privoxy docker, same result. Thank you in advance for all your hard work!

Link to comment
10 minutes ago, spacebender said:

For what ever reason binhex-deluge and binhex-hydra seem to ignore proxy settings.

do not use privoxy to attempt to secure torrent traffic it is not designed to do this, if you want to prevent letters from your ISP then you have to run these as individual application WITH the vpn running for each app, if you want to see what prioxy IS designed to be used for then see Q3 from the following link:-

 

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

 

Link to comment

Hi all,

 

I'm getting some very slow speeds when connected through a VPN (PIA), around 200kbps. If I disconnect the VPN I get upwards of 12-14Mbps.

When connecting to PIA thought the desktop app, I also get 12Mbps, just as a reference. And through delugevpn I can get around 5Mbps.

Tried  connecting using nzbdget, and had the same slow speeds when connected to the VPN.

Tried different servers of PIA with no difference on the speed, tried SSL, no SSL, different encryption.

 

Any ideas of what could be causing this, anyone had this issue?

 

Thanks.

  • Upvote 1
Link to comment

I've set this up using a custom VPN provider, and after some minor issues it looks like it is working. VPN is enabled, i can see in the logging the VPN is set up, and sabnzbd is actually downloading... i'm also using the VPN created here for e.g. sonarr, by setting sonarr's proxy to vpn's ip:8118. Sonarr works as well as it seems.

 

But is there a way to make sure it i actually working as it should? No dns leaking etc? Other tests?

i mean sab is downloading, but i can't really tell if it is actually doing it over the vpn or not?

Link to comment
50 minutes ago, jowi said:

I've set this up using a custom VPN provider, and after some minor issues it looks like it is working. VPN is enabled, i can see in the logging the VPN is set up, and sabnzbd is actually downloading... i'm also using the VPN created here for e.g. sonarr, by setting sonarr's proxy to vpn's ip:8118. Sonarr works as well as it seems.

 

But is there a way to make sure it i actually working as it should? No dns leaking etc? Other tests?

i mean sab is downloading, but i can't really tell if it is actually doing it over the vpn or not?

see Q2 under the SABnzbdVPN Docker FAQ heading in the following link:-

 

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

 

also see Q1 under the heading VPN Docker FAQ for details about kill switch (or lack of) from the link above.

 

 

Link to comment

Thanks. I tried the method of checking the ip address under Q2, if i do this for the sabnzbd-vpn docker, i get the ip address my VPN provider gave me, so that seems ok. But if i do the same for the Sonarr docker, where i've setup sonarr to use the sabnzbd-vpn as proxy, it gives me the ip adress of my original ISP... or is this correct?

Link to comment
4 minutes ago, jowi said:

But if i do the same for the Sonarr docker, where i've setup sonarr to use the sabnzbd-vpn as proxy, it gives me the ip adress of my original ISP... or is this correct?

completely expected, remember configuring sonarr to use a proxy will mean only sonarr will use the proxy, not the operating system, so using curl (or any other tool) on sonarr will just use your isp connection and show your isp ip address.

 

in contrast using curl for sabnzbdvpn its forced to use the tunnel and only the tunnel, this is at an os level, so ALL applications running inside that container use the vpn tunnel and thus report your vpn providers ip address.

 

if you want to test sonarr to ensure its using the proxy then simply stop the sabnzbdvpn container, then get sonarr to attempt to search for a tv series, if it fails then it using the proxy correctly.

Edited by binhex
  • Like 2
Link to comment

Thanks, i'll try that. 

 

Another thing i noticed; i'm using a python postprocessing script in sabnzbd that renames the downloaded file, adds some info from thetvdb, and moves it to the right place in the array, refreshes sonarr's history so sonarr knows the new name i gave it, and last but not least, i'm sending myself an email that episode x from series y is downloaded. Everything seems to work, except for sending the email... it looks like it gets sent without errors or exceptions, using smtp, ssl (port 587, with correct credentials etc) but it is not getting delivered, i never get the email? Is there something i need to change in my code now i'm sending from inside this vpn?

 

*edit* seems to be a provider issue... i've been using a fake email adres as sender, e.g. [email protected]. I think the ISP changed something so you can't do that anymore; if i'm using my actual, real email address it works... probably an anti spam countermeasure or something.

Edited by jowi
Link to comment
  • 2 weeks later...

Hello

 

I restarted my server today and ever since then i cannot get sbnzbvpn or delugevpn (binhex builds) to run they both stop in the logs at this line

2019-03-12 15:19:25,362 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf
then a few minutes later is get a red error line

2019-03-12 15:21:25,481 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

 

If i turn off vpn they both work fine any info would be appreciated i guessing this might not just be me ? I have tried different locations which also did not help

 

Also just wanted to take this chance to say thanks to binhex for his great work on these dockers

 

Thanks

Edited by vapingzombie
Link to comment

Hello binhex

thanks for your reply i have done as you requested with the sabnzdvpn supervisord.log just to give a little more info i am using PIA i usually use france as the location but i also tried Switzerland.ovpn today both gave same results

 

supervisord.log

 

I also have the deluge log if you need that as well but not sure i should post it in the thread so tell me if you want it :)

 

Thank you

 

 

Link to comment
3 minutes ago, vapingzombie said:

Hello binhex

thanks for your reply i have done as you requested with the sabnzdvpn supervisord.log just to give a little more info i am using PIA i usually use france as the location but i also tried Switzerland.ovpn today both gave same results

 

supervisord.log

 

I also have the deluge log if you need that as well but not sure i should post it in the thread so tell me if you want it :)

 

Thank you

 

 

ok from the logs:-

 

2019-03-12 17:12:52,769 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error

2019-03-12 17:12:52,771 DEBG 'start-script' stdout output:
[crit] swiss.privateinternetaccess.com cannot be resolved, possible DNS issues

so def name resolution issue, if you ssh to your unraid host (not the container) and type:-

 

ping www.google.com

what do you get back? (ctrl+x to exit that command) i am guessing it will say it cant resolve it.

Link to comment

hi i got this



 



PING www.google.com (216.58.213.100) 56(84) bytes of data.
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=1 ttl=51 time=48.0 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=2 ttl=51 time=61.3 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=3 ttl=51 time=45.6 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=4 ttl=51 time=62.3 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=5 ttl=51 time=62.9 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=6 ttl=51 time=41.1 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=7 ttl=51 time=40.3 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=8 ttl=51 time=52.8 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=9 ttl=51 time=47.1 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=10 ttl=51 time=46.1 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=11 ttl=51 time=61.0 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=12 ttl=51 time=44.1 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=13 ttl=51 time=40.5 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=14 ttl=51 time=51.1 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=15 ttl=51 time=60.1 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=16 ttl=51 time=52.4 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=17 ttl=51 time=55.9 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=18 ttl=51 time=54.7 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=19 ttl=51 time=55.3 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=20 ttl=51 time=64.3 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=21 ttl=51 time=42.8 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=22 ttl=51 time=58.8 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=23 ttl=51 time=42.7 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=24 ttl=51 time=40.4 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=25 ttl=51 time=62.9 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=26 ttl=51 time=50.0 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=27 ttl=51 time=42.8 ms



 



i then exited like you said :) its seem strange every other docker works fine and it was working well before i restarted unraid also just to add if i turn vpn to no then deluge and sabnzd work fine im not overally concerned about sab but i wont use torrents without a vpn



i was really hoping this was happening to everyone setups !! lol last time i had a problem was when pia stopped port forwarding at netherlands.

i also deleted my docker.img and reinstall my templates which did not work



 

Edited by vapingzombie
add a bit more info
Link to comment

while reading thru BINHEX's general page i came across something that i thought was interesting. 

 

I am using SABnzbdVPN, along with Radarr, Sonarr and Lidarr all processing through it. I also have PIA as my VPN. 

 

I came across the the STRICT_PORT_FORWARD option and BINHEX suggests that it should be turned on ( set to yes) when you have a PIA VPN. 

 

However when i turned it on everything started to bounce. I would get great speeds and then nothing. 

 

with it turned off i am getting on average anywhere from 10MB/s to 15MB/s downloads, however i was getting almost 30MB/s until it went out again with the STRICT_PORT_FORWARD turned on. 

 

Any Ideas?

Link to comment

I just tried beets and musicbrainz local mirror they now refuse to talk to each and musicbrainz says there's an internal server error

 

looks like i may have to reinstall its strange as i havent added anymore plugins for a few months something happened on restart ?

 

thanks for trying binhex :)

Edited by vapingzombie
Link to comment
15 hours ago, vapingzombie said:

I just tried beets and musicbrainz local mirror they now refuse to talk to each and musicbrainz says there's an internal server error

 

looks like i may have to reinstall its strange as i havent added anymore plugins for a few months something happened on restart ?

 

thanks for trying binhex :)

tbh there could me a multitude of reasons why name resolution isnt workking, i have seen some nazi isp's dont allow you to use anything other than their name servers, so they maybe blocking google dns (8.8.8.8 and 8.8.4.4) you could try changing the NAME_SERVERS value so that it doesnt have the google name servers in there, perhaps you might get lucky and your isp may let through other name servers instead.

Link to comment
16 hours ago, 08deanr said:

while reading thru BINHEX's general page i came across something that i thought was interesting. 

 

I am using SABnzbdVPN, along with Radarr, Sonarr and Lidarr all processing through it. I also have PIA as my VPN. 

 

I came across the the STRICT_PORT_FORWARD option and BINHEX suggests that it should be turned on ( set to yes) when you have a PIA VPN. 

 

However when i turned it on everything started to bounce. I would get great speeds and then nothing. 

 

with it turned off i am getting on average anywhere from 10MB/s to 15MB/s downloads, however i was getting almost 30MB/s until it went out again with the STRICT_PORT_FORWARD turned on. 

 

Any Ideas?

STRICT_PORT_FORWARD is only useful if you need an incoming port, as usenet is client to server there is no requirement for this (used for torrent clients), and thus that option does absolutely nothing, in fact the code has been removed from this image, so any slowdowns you are seeing are nothing to do with this option being set.

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.