[Support] binhex - SABnzbdVPN

[newoski]

Sorry for the confusion, I combined my response with a previous user who reported the same issue. On my network, IP addresses are all in the 10.0.0.X format. So in my log, the message is an error about opening http://10.0.0.X:8081/home/postprocess...

 

Thanks and sorry for the delayed reply here:

 

The SickBeard script for SABnzbd errors out when trying to post-process the download:

Loading config from /mnt/cache/docker/apps/sabnzbdvpn/scripts/autoProcessTV.cfg

Opening URL: http://192.168.1.5:8081/home/postprocess/processEpisode?nzbName="Random_TV_Show"'>http://192.168.1.5:8081/home/postprocess/processEpisode?nzbName="Random_TV_Show"

Unable to open URL:  [Errno socket error] [Errno 110] Connection timed out

 

Essentially, SABnzbvpn and SickBeard can't talk to each other, because one is behind the VPN and the other is not.

 

Here's the SickBeard config:

http://i66.tinypic.com/33a6xrn.png

 

Let me know if you need anything else. A solution here would be amazing!

 

 

THANKS! That confirmed that everything is working fine, it's just an outdated disconnect message that doesn't go away.

 

Any idea if it's possible to get SickBeard communicating with SABnzbdvpn behind the VPN? It errors out when it tries to run the script

 

excellent, always nice to hear that it is working as expected :-), umm yeah that should be possible, depends how SB talks to sab though, can you post some screenshots of the SB config section?. its late over here so i will have to take a look at this tomorrow.

 

that sickbeard screenshot looks a bit wrong, the url you have for sabnzbd is http://10.0.0.9:8079 if the ip is correct for the script then shouldnt it be http://192.168.1.5:8081 ? i know the script is seperate but it might be calling the sickbeard api to get certain info about sab.

Checking back in here. Can I do anything else to help get this addressed?

 

Sent from my HTC6535LVW using Tapatalk

 

 

[morreale]

still nothing on this?  just reinstalled to see if it had been corrected (with no success) seems others are also having the issue and no one has found a solution.

[newoski]

still nothing on this?  just reinstalled to see if it had been corrected (with no success) seems others are also having the issue and no one has found a solution.

 

assume you're referring to the same issue I am? SickBeard post processing?

[morreale]

still nothing on this?  just reinstalled to see if it had been corrected (with no success) seems others are also having the issue and no one has found a solution.

 

assume you're referring to the same issue I am? SickBeard post processing?

 

yes I was the one who posted this a while back in this thread.  Sorry you are having the issue but also glad I am not the only one.  It was driving me crazy.

[newoski]

still nothing on this?  just reinstalled to see if it had been corrected (with no success) seems others are also having the issue and no one has found a solution.

 

assume you're referring to the same issue I am? SickBeard post processing?

 

yes I was the one who posted this a while back in this thread.  Sorry you are having the issue but also glad I am not the only one.  It was driving me crazy.

Ah, Roger. Thanks for the original post. I thought I was the only one. Fingers crossed we can get this addressed. It's near perfect

 

Sent from my HTC6535LVW using Tapatalk

 

 

[morreale]

still nothing on this?  just reinstalled to see if it had been corrected (with no success) seems others are also having the issue and no one has found a solution.

 

assume you're referring to the same issue I am? SickBeard post processing?

 

yes I was the one who posted this a while back in this thread.  Sorry you are having the issue but also glad I am not the only one.  It was driving me crazy.

Ah, Roger. Thanks for the original post. I thought I was the only one. Fingers crossed we can get this addressed. It's near perfect

 

 

the only thing i can think of is we need to configure the ports/iptables to allow traffic to pass over the port (8081 in my case) from sab to sickbeard

[MyKroFt]

Did you add

 

 

variable LAN_NETWORK

which in my case is set to 192.168.0.0/24

 

 

to allow interlan communications?

 

 

Myk

 

 

[morreale]

Did you add

 

 

variable LAN_NETWORK

which in my case is set to 192.168.0.0/24

 

 

to allow interlan communications?

 

 

Myk

 

yes

[morreale]

pretty sure this is where the problem lies...  this shows the only ports allowing traffic are 443 (vpn) and 8080/8090 (sab)

i need to add 8081 to this table to allow this container to communicate out to my sickbeard container. (or some translations on both containers)

playing around with adding a port to the docker config.

 

 

2016-06-29 20:00:44,151 DEBG 'start-script' stdout output:

[info] iptables defined as follows...

--------------------

 

2016-06-29 20:00:44,154 DEBG 'start-script' stdout output:

-P INPUT DROP

-P FORWARD ACCEPT

-P OUTPUT DROP

-A INPUT -i tun0 -j ACCEPT

-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

-A INPUT -i eth0 -p udp -m udp --sport 443 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --dport 8090 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8090 -j ACCEPT

-A INPUT -p udp -m udp --sport 53 -j ACCEPT

-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT

-A INPUT -i lo -j ACCEPT

-A OUTPUT -o tun0 -j ACCEPT

-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

-A OUTPUT -o eth0 -p udp -m udp --dport 443 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --dport 8090 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 8090 -j ACCEPT

-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT

-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT

-A OUTPUT -o lo -j ACCEPT

[MyKroFt]

whats weird is rutorrentVPN has the same setup and I am able to have SickbeardVPN and sickrage talk to my rutorrentVPN just fine when searching and it finds a .torrent

 

 

and its using the local 192.168.0.x ip

 

 

Myk

 

 

 

 

 

 

[binhex]

I am going to look at this guys, just got a couple of urgent issues to sort and then I will be right on this.

 

Sent from my SM-G900F using Tapatalk

 

 

[morreale]

whats weird is rutorrentVPN has the same setup and I am able to have SickbeardVPN and sickrage talk to my rutorrentVPN just fine when searching and it finds a .torrent

 

 

and its using the local 192.168.0.x ip

 

 

Myk

 

that functionality works fine.  the piece that doesn't work is a post processing task that tries to hit a URL on a certain (user defined) port inside the sickbeard container.

[morreale]

I am going to look at this guys, just got a couple of urgent issues to sort and then I will be right on this.

 

Sent from my SM-G900F using Tapatalk

 

Thanks binhex.  Is there a guide or something you can point me to that explains how to edit the IPTables inside the container?

 

something like this?  https://lime-technology.com/forum/index.php?topic=40290.0

[binhex]

ok so ive had a quick poke at the problem where sickbeard cannot talk to sabnzbd when the tunnel is established, and well i cant get it to not work  so i plugged in the url for sabnzbd into sickbeard hit the test connection button and i get "Success. Connected and authenticated" what am i missing guys?

 

 

Just to be clear here the url you should be using is http://<your unraid servers ip>:<the host port NOT the container port>/

[newoski]

ok so ive had a quick poke at the problem where sickbeard cannot talk to sabnzbd when the tunnel is established, and well i cant get it to not work  so i plugged in the url for sabnzbd into sickbeard hit the test connection button and i get "Success. Connected and authenticated" what am i missing guys?

 

 

Just to be clear here the url you should be using is http://<your unraid servers ip>:<the host port NOT the container port>/

 

Testing it this way works fine. SickBeard can also send SABnzbdvpn snatched episodes without problems. The issue occurs when trying to use the SickBeard post processing script. It errors out every time

[binhex]

The issue occurs when trying to use the SickBeard post processing script. It errors out every time

 

ok so im not that familiar with sickbeard, and thus i havent a clue which script your on about im afriad, any chance you can post some steps i can follow to replicate the issue?.

[newoski]

The issue occurs when trying to use the SickBeard post processing script. It errors out every time

 

ok so im not that familiar with sickbeard, and thus i havent a clue which script your on about im afriad, any chance you can post some steps i can follow to replicate the issue?.

 

https://jetshred.com/2012/07/31/configuring-sickbeard-to-work-with-sabnzbd-plus/

 

This should walk you through it. Make sure to follow the last setup, editing the cfg. Instead of monitoring the download folder, it immediately processes downloaded episodes. Let me know if you have any questions.

[newoski]

The issue occurs when trying to use the SickBeard post processing script. It errors out every time

 

ok so im not that familiar with sickbeard, and thus i havent a clue which script your on about im afriad, any chance you can post some steps i can follow to replicate the issue?.

 

If you have TeamViewer, shoot me a PM with your info and I can log in and walk you through recreating error if you'd like...

[binhex]

The issue occurs when trying to use the SickBeard post processing script. It errors out every time

 

ok so im not that familiar with sickbeard, and thus i havent a clue which script your on about im afriad, any chance you can post some steps i can follow to replicate the issue?.

 

https://jetshred.com/2012/07/31/configuring-sickbeard-to-work-with-sabnzbd-plus/

 

This should walk you through it. Make sure to follow the last setup, editing the cfg. Instead of monitoring the download folder, it immediately processes downloaded episodes. Let me know if you have any questions.

 

Thanks for that, unfortunately i dont use usenet at the moment so i will only be able to go so far with testing this, i see it uses a cfg file, can you post it here (minus anything sensitive of course).

[newoski]

The issue occurs when trying to use the SickBeard post processing script. It errors out every time

 

ok so im not that familiar with sickbeard, and thus i havent a clue which script your on about im afriad, any chance you can post some steps i can follow to replicate the issue?.

 

https://jetshred.com/2012/07/31/configuring-sickbeard-to-work-with-sabnzbd-plus/

 

This should walk you through it. Make sure to follow the last setup, editing the cfg. Instead of monitoring the download folder, it immediately processes downloaded episodes. Let me know if you have any questions.

 

Thanks for that, unfortunately i dont use usenet at the moment so i will only be able to go so far with testing this, i see it uses a cfg file, can you post it here (minus anything sensitive of course).

 

Here is the sample cfg:

 

# Sick Beard autoProcessTV configuration file

# Used in combination with scripts like sabToSickBeard that call autoProcessTV

#

# Rename (or copy) autoProcessTV.cfg.sample to autoProcessTV.cfg

# Change the host, port, username, and password values

# to the appropriate settings for your Sick Beard server.

#

# Example:  Sick Beard can be accessed on http://localhost:8081

#          without username/password

#

# host=localhost    # Sick Beard host (localhost or IP address)

# port=8081        # Sick Beard port

# username=        # Credentials for logging into Sick Beard

# password=        # Credentials for logging into Sick Beard (don't use special characters)

# web_root=        # Sick Beard web_root

# ssl=0            # http (ssl=0) (for https use ssl=1)

 

[sickBeard]

host=localhost

port=8081

username=

password=

web_root=/

ssl=0

 

-------------------------

 

The variables at the bottom look like this on my setup:

 

[sickBeard]

host=10.0.0.9

port=8081

username=

password=

web_root=/

ssl=0

 

[binhex]

The issue occurs when trying to use the SickBeard post processing script. It errors out every time

 

ok so im not that familiar with sickbeard, and thus i havent a clue which script your on about im afriad, any chance you can post some steps i can follow to replicate the issue?.

 

https://jetshred.com/2012/07/31/configuring-sickbeard-to-work-with-sabnzbd-plus/

 

This should walk you through it. Make sure to follow the last setup, editing the cfg. Instead of monitoring the download folder, it immediately processes downloaded episodes. Let me know if you have any questions.

 

Thanks for that, unfortunately i dont use usenet at the moment so i will only be able to go so far with testing this, i see it uses a cfg file, can you post it here (minus anything sensitive of course).

 

Here is the sample cfg:

 

# Sick Beard autoProcessTV configuration file

# Used in combination with scripts like sabToSickBeard that call autoProcessTV

#

# Rename (or copy) autoProcessTV.cfg.sample to autoProcessTV.cfg

# Change the host, port, username, and password values

# to the appropriate settings for your Sick Beard server.

#

# Example:  Sick Beard can be accessed on http://localhost:8081

#          without username/password

#

# host=localhost    # Sick Beard host (localhost or IP address)

# port=8081        # Sick Beard port

# username=        # Credentials for logging into Sick Beard

# password=        # Credentials for logging into Sick Beard (don't use special characters)

# web_root=        # Sick Beard web_root

# ssl=0            # http (ssl=0) (for https use ssl=1)

 

[sickBeard]

host=localhost

port=8081

username=

password=

web_root=/

ssl=0

 

-------------------------

 

The variables at the bottom look like this on my setup:

 

[sickBeard]

host=10.0.0.9

port=8081

username=

password=

web_root=/

ssl=0

 

ok so there are no credentials sent through here, or did you just remove them?, also can you verify you have set sickbeard NOT to use ssl?

[newoski]

The issue occurs when trying to use the SickBeard post processing script. It errors out every time

 

ok so im not that familiar with sickbeard, and thus i havent a clue which script your on about im afriad, any chance you can post some steps i can follow to replicate the issue?.

 

https://jetshred.com/2012/07/31/configuring-sickbeard-to-work-with-sabnzbd-plus/

 

This should walk you through it. Make sure to follow the last setup, editing the cfg. Instead of monitoring the download folder, it immediately processes downloaded episodes. Let me know if you have any questions.

 

Thanks for that, unfortunately i dont use usenet at the moment so i will only be able to go so far with testing this, i see it uses a cfg file, can you post it here (minus anything sensitive of course).

 

Here is the sample cfg:

 

# Sick Beard autoProcessTV configuration file

# Used in combination with scripts like sabToSickBeard that call autoProcessTV

#

# Rename (or copy) autoProcessTV.cfg.sample to autoProcessTV.cfg

# Change the host, port, username, and password values

# to the appropriate settings for your Sick Beard server.

#

# Example:  Sick Beard can be accessed on http://localhost:8081

#          without username/password

#

# host=localhost    # Sick Beard host (localhost or IP address)

# port=8081        # Sick Beard port

# username=        # Credentials for logging into Sick Beard

# password=        # Credentials for logging into Sick Beard (don't use special characters)

# web_root=        # Sick Beard web_root

# ssl=0            # http (ssl=0) (for https use ssl=1)

 

[sickBeard]

host=localhost

port=8081

username=

password=

web_root=/

ssl=0

 

-------------------------

 

The variables at the bottom look like this on my setup:

 

[sickBeard]

host=10.0.0.9

port=8081

username=

password=

web_root=/

ssl=0

 

ok so there are no credentials sent through here, or did you just remove them?, also can you verify you have set sickbeard NOT to use ssl?

 

correct. i don't use credentials (username/password). I dont think I have SSL enabled. I've never touched an SSL setting on SickBeard and it works perfectly with all other SAB clients, so I think my settings are correct

[binhex]

is your sickbeard installation a docker container and is it running on the same unraid host as the sabnzbdvpn container?

[newoski]

is your sickbeard installation a docker container and is it running on the same unraid host as the sabnzbdvpn container?

Yes it is a docker.

Sab = 8080, 8090, 8118 both container and host

 

SickNess =8081 both container and host

 

Sent from my HTC6535LVW using Tapatalk

 

 

[morreale]

everything functions properly as stated except for the post processing script.  which in my case tries to establish a connection from the sab container to the sickbeard container over port 8081.  i think the issue is simply that the port is not allowed to leave the sab docker container.  i think an allow of that port (or whatever port is configured for sickbeard) will solve the issue.

 

thanks for taking the time to look into this.