[Support] binhex - SABnzbdVPN


Recommended Posts

First thank you for this, it seems to work really well.  I had it working yesterday, but all my containers are fighting over permissions, I noticed my SAB container PUID and GUID were set to 0 but sonarr has them set to 1000 (which is the UID I want to use), this container will boot up fine and run fine with the PUID and GUID set to 0 but when I went to change them to 1000, it will no longer let me get into the web interface.  The only error I am receiving is :

 

2016-09-14 09:44:32,990 DEBG 'sabnzbd-script' stdout output:
Error:
Can't write to logfile

2016-09-14 09:44:33,011 DEBG 'sabnzbd-script' stdout output:

 

any ideas? TIA

Link to comment

I'm not running your container on Unraid at the moment. I use it on a Ubuntu system with docker installed.

 

how do i upgrade to Sabnzbd 1.1.0?

I'm assuming your running 6.1.9 and thus updates are broken, to work around this enable advanced view and then select force update to force the update.

 

Sent from my SM-G900F using Tapatalk

 

ive just checked and its not been updated on AUR yet so no update to 1.1.0 is available. once the image is built you would need to do a stop of your existing container, then remove image and container and then re-pull down and create the container by issuing the docker run command.

Thank you for your response. I'll wait for AUR then.

Link to comment

First thank you for this, it seems to work really well.  I had it working yesterday, but all my containers are fighting over permissions, I noticed my SAB container PUID and GUID were set to 0 but sonarr has them set to 1000 (which is the UID I want to use), this container will boot up fine and run fine with the PUID and GUID set to 0 but when I went to change them to 1000, it will no longer let me get into the web interface.  The only error I am receiving is :

 

2016-09-14 09:44:32,990 DEBG 'sabnzbd-script' stdout output:
Error:
Can't write to logfile

2016-09-14 09:44:33,011 DEBG 'sabnzbd-script' stdout output:

 

any ideas? TIA

If you change the values of either puid or pgid then you will need to stop the container and then delete the file perms.txt  from /config then start the container again to force the re applying of permissions.

 

Sent from my SM-G900F using Tapatalk

 

 

Link to comment

I'm not running your container on Unraid at the moment. I use it on a Ubuntu system with docker installed.

 

how do i upgrade to Sabnzbd 1.1.0?

I'm assuming your running 6.1.9 and thus updates are broken, to work around this enable advanced view and then select force update to force the update.

 

Sent from my SM-G900F using Tapatalk

 

ive just checked and its not been updated on AUR yet so no update to 1.1.0 is available. once the image is built you would need to do a stop of your existing container, then remove image and container and then re-pull down and create the container by issuing the docker run command.

Thank you for your response. I'll wait for AUR then.

 

just so you know, this did get released and ive built the image so its now available.

Link to comment

I'm not running your container on Unraid at the moment. I use it on a Ubuntu system with docker installed.

 

how do i upgrade to Sabnzbd 1.1.0?

I'm assuming your running 6.1.9 and thus updates are broken, to work around this enable advanced view and then select force update to force the update.

 

Sent from my SM-G900F using Tapatalk

 

ive just checked and its not been updated on AUR yet so no update to 1.1.0 is available. once the image is built you would need to do a stop of your existing container, then remove image and container and then re-pull down and create the container by issuing the docker run command.

Thank you for your response. I'll wait for AUR then.

 

just so you know, this did get released and ive built the image so its now available.

 

Thank you it works! However 7zip is missing. See attachmet. Can you fix it?

NamnlAs.png.fec119ccfd4c49cf73bf02647b9c1281.png

Link to comment

I'm not running your container on Unraid at the moment. I use it on a Ubuntu system with docker installed.

 

how do i upgrade to Sabnzbd 1.1.0?

I'm assuming your running 6.1.9 and thus updates are broken, to work around this enable advanced view and then select force update to force the update.

 

Sent from my SM-G900F using Tapatalk

 

ive just checked and its not been updated on AUR yet so no update to 1.1.0 is available. once the image is built you would need to do a stop of your existing container, then remove image and container and then re-pull down and create the container by issuing the docker run command.

Thank you for your response. I'll wait for AUR then.

 

just so you know, this did get released and ive built the image so its now available.

 

Thank you it works! However 7zip is missing. See attachmet. Can you fix it?

 

fixed, please pull down the latest image.

Link to comment
  • 1 month later...

I know this is an SABnzbd issue but I was hoping someone here could help.  There seems to be an issue with obfuscated filenames not being renamed because of how SABnzdbd handles par files.  I've seen quite a few nzb's lately where a separate par file called rename.par plus an obfuscated file are left in the download directory. I'm using Sonarr for post processing and it will fail on these files because the obfuscated file name isn't the right format. From here there's two options, manually execute the rename.par file or manually rename the file so Sonarr picks it up and processes correctly.  From what I gather, the folks running SABnzbd don't really want to change how it handles par files (i.e. It only uses par files to repair damaged files, not rename them), so other Linux build users have written custom scripts to manage a workaround.  I'm wondering how to implement such a solution with my current setup of SABnzbd and Sonarr?  Does anyone else have an "automated" solution to this problem?

 

EDIT:  Here's a link to a detailed description of the issue.

Link to comment

I know this is an SABnzbd issue but I was hoping someone here could help.  There seems to be an issue with obfuscated filenames not being renamed because of how SABnzdbd handles par files.  I've seen quite a few nzb's lately where a separate par file called rename.par plus an obfuscated file are left in the download directory. I'm using Sonarr for post processing and it will fail on these files because the obfuscated file name isn't the right format. From here there's two options, manually execute the rename.par file or manually rename the file so Sonarr picks it up and processes correctly.  From what I gather, the folks running SABnzbd don't really want to change how it handles par files (i.e. It only uses par files to repair damaged files, not rename them), so other Linux build users have written custom scripts to manage a workaround.  I'm wondering how to implement such a solution with my current setup of SABnzbd and Sonarr?  Does anyone else have an "automated" solution to this problem?

 

EDIT:  Here's a link to a detailed description of the issue.

Can't help with the issue, but I'm genuinely curious if switching to nzbget would fix the problem? I'm still using SAB, so if nzbget doesn't suffer from the same problem, it may be another reason to switch.
Link to comment

I know this is an SABnzbd issue but I was hoping someone here could help.  There seems to be an issue with obfuscated filenames not being renamed because of how SABnzdbd handles par files.  I've seen quite a few nzb's lately where a separate par file called rename.par plus an obfuscated file are left in the download directory. I'm using Sonarr for post processing and it will fail on these files because the obfuscated file name isn't the right format. From here there's two options, manually execute the rename.par file or manually rename the file so Sonarr picks it up and processes correctly.  From what I gather, the folks running SABnzbd don't really want to change how it handles par files (i.e. It only uses par files to repair damaged files, not rename them), so other Linux build users have written custom scripts to manage a workaround.  I'm wondering how to implement such a solution with my current setup of SABnzbd and Sonarr?  Does anyone else have an "automated" solution to this problem?

 

EDIT:  Here's a link to a detailed description of the issue.

Can't help with the issue, but I'm genuinely curious if switching to nzbget would fix the problem? I'm still using SAB, so if nzbget doesn't suffer from the same problem, it may be another reason to switch.

 

Yeah, good question.  Let me know if it works for you!  :P  Haha, seriously though, if I get some free time then I'll try installing nzbget and will report back.

Link to comment

I know this is an SABnzbd issue but I was hoping someone here could help.  There seems to be an issue with obfuscated filenames not being renamed because of how SABnzdbd handles par files.  I've seen quite a few nzb's lately where a separate par file called rename.par plus an obfuscated file are left in the download directory. I'm using Sonarr for post processing and it will fail on these files because the obfuscated file name isn't the right format. From here there's two options, manually execute the rename.par file or manually rename the file so Sonarr picks it up and processes correctly.  From what I gather, the folks running SABnzbd don't really want to change how it handles par files (i.e. It only uses par files to repair damaged files, not rename them), so other Linux build users have written custom scripts to manage a workaround.  I'm wondering how to implement such a solution with my current setup of SABnzbd and Sonarr?  Does anyone else have an "automated" solution to this problem?

 

EDIT:  Here's a link to a detailed description of the issue.

Can't help with the issue, but I'm genuinely curious if switching to nzbget would fix the problem? I'm still using SAB, so if nzbget doesn't suffer from the same problem, it may be another reason to switch.

 

Yeah, good question.  Let me know if it works for you!  :P  Haha, seriously though, if I get some free time then I'll try installing nzbget and will report back.

Ok, so I had some time and configured nzbgetvpn.  It uses a function call Par_rename to handle obfuscated titles. As luck would have it, I haven't come across any yet but I can see in the log file where it checks for the rename.par file. So far so good. Only issue I need to figure out is cleanup of the tmp download directory.

 

Edit: Cleanup issue was from SAB pulling same nzb file before I switched off docker and download client in Sonarr. Seems to be working very well thus far with less manual intervention required.

Link to comment
  • 4 weeks later...

Finally got VPN up, but it looks like SABnzbd never starts.  from looking @ https://github.com/binhex/arch-sabnzbdvpn/tree/master/setup I can't find anything echoing out "Initialization Sequence Completed" 

 

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="binhex-sabnzbdvpn" --net="bridge" --privileged="true" -e TZ="America/Chicago" -e HOST_OS="unRAID" -e "VPN_ENABLED"="yes" -e "VPN_USER"="user" -e "VPN_PASS"="password" -e "VPN_REMOTE"="vp_IP" -e "VPN_PORT"="1194" -e "VPN_PROTOCOL"="udp" -e "VPN_DEVICE_TYPE"="tun0" -e "VPN_PROV"="custom" -e "STRONG_CERTS"="no" -e "ENABLE_PRIVOXY"="yes" -e "LAN_NETWORK"="10.0.1.0/24" -e "NAME_SERVERS"="8.8.8.8,8.8.4.4" -e "ADDITIONAL_PORTS"="8081" -e "DEBUG"="true" -e "PUID"="99" -e "PGID"="100" -p 8080:8080/tcp -p 8090:8090/tcp -p 8118:8118/tcp -v "/mnt/btrfs/temp/":"/data":rw -v "/mnt/user/appdata/binhex-sabnzbdvpn":"/config":rw binhex/arch-sabnzbdvpn

 

Any ideas?

 

2016-12-01 17:50:52,107 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...

2016-12-01 17:50:52,119 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:52 2016 OpenVPN 2.3.12 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [iPv6] built on Aug 24 2016
Thu Dec 1 17:50:52 2016 library versions: OpenSSL 1.0.2j 26 Sep 2016, LZO 2.09
Thu Dec 1 17:50:52 2016 WARNING: file 'credentials.conf' is group or others accessible


2016-12-01 17:50:52,120 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:52 2016 Socket Buffers: R=[212992->212992] S=[212992->212992]

2016-12-01 17:50:52,149 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:52 2016 UDPv4 link local: [undef]
Thu Dec 1 17:50:52 2016 UDPv4 link remote: [AF_INET]81.171.98.67:1194

2016-12-01 17:50:52,271 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:52 2016 TLS: Initial packet from [AF_INET]81.171.98.67:1194, sid=e5f49e75 96fbbabf

2016-12-01 17:50:52,417 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:52 2016 VERIFY OK: depth=1, C=US, ST=VPN, L=VPN, O=VPN, OU=VPN, CN=VPN, name=VPN, emailAddress=VPN

2016-12-01 17:50:52,417 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:52 2016 Validating certificate key usage
Thu Dec 1 17:50:52 2016 ++ Certificate has key usage 00a0, expects 00a0
Thu Dec 1 17:50:52 2016 VERIFY KU OK
Thu Dec 1 17:50:52 2016 Validating certificate extended key usage
Thu Dec 1 17:50:52 2016 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Thu Dec 1 17:50:52 2016 VERIFY EKU OK
Thu Dec 1 17:50:52 2016 VERIFY OK: depth=0, C=US, ST=VPN, L=VPN, O=VPN, OU=VPN, CN=vpn, name=VPN

2016-12-01 17:50:52,696 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:52 2016 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Thu Dec 1 17:50:52 2016 Data Channel Encrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
Thu Dec 1 17:50:52 2016 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Thu Dec 1 17:50:52 2016 Data Channel Decrypt: Using 256 bit message hash 'SHA256' for HMAC authentication

2016-12-01 17:50:52,696 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:52 2016 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Thu Dec 1 17:50:52 2016 [vpn] Peer Connection Initiated with [AF_INET]81.171.98.67:1194

2016-12-01 17:50:54,910 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:54 2016 SENT CONTROL [vpn]: 'PUSH_REQUEST' (status=1)

2016-12-01 17:50:55,036 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:55 2016 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 198.18.0.1,dhcp-option DNS 198.18.0.2,rcvbuf 262144,explicit-exit-notify 5,route-gateway 172.21.94.1,topology subnet,ping 20,ping-restart 40,ifconfig 172.21.94.44 255.255.254.0'

2016-12-01 17:50:55,036 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:55 2016 OPTIONS IMPORT: timers and/or timeouts modified
Thu Dec 1 17:50:55 2016 OPTIONS IMPORT: explicit notify parm(s) modified
Thu Dec 1 17:50:55 2016 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Thu Dec 1 17:50:55 2016 Socket Buffers: R=[212992->524288] S=[212992->212992]
Thu Dec 1 17:50:55 2016 OPTIONS IMPORT: --ifconfig/up options modified
Thu Dec 1 17:50:55 2016 OPTIONS IMPORT: route options modified
Thu Dec 1 17:50:55 2016 OPTIONS IMPORT: route-related options modified
Thu Dec 1 17:50:55 2016 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Dec 1 17:50:55 2016 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02
Thu Dec 1 17:50:55 2016 TUN/TAP device tun0 opened
Thu Dec 1 17:50:55 2016 TUN/TAP TX queue length set to 100
Thu Dec 1 17:50:55 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0

2016-12-01 17:50:55,037 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:55 2016 /usr/bin/ip link set dev tun0 up mtu 1500

2016-12-01 17:50:55,038 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:55 2016 /usr/bin/ip addr add dev tun0 172.21.94.44/23 broadcast 172.21.95.255

2016-12-01 17:50:55,040 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:55 2016 /usr/bin/ip route add 81.171.98.67/32 via 172.17.0.1

2016-12-01 17:50:55,041 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:55 2016 /usr/bin/ip route add 0.0.0.0/1 via 172.21.94.1

2016-12-01 17:50:55,043 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:55 2016 /usr/bin/ip route add 128.0.0.0/1 via 172.21.94.1

2016-12-01 17:50:55,044 DEBG 'start-script' stdout output:
Thu Dec 1 17:50:55 2016 Initialization Sequence Completed

Link to comment
  • 2 weeks later...
  • 2 weeks later...

hey guys,

 

i've got a problem ... suprise suprise :)

Installed the docker.

When i select vpn enable "no" I'm able to access sabnzbd.

When I enable the vpn I'm not able to reach the webinterface from my windows pc within the same LAN.

 

Pretty sure its my own stupidity but I need help :)

Usually that means you have something filled out wrong in the VPN section of the docker config page, like wrong user or password or something. Who is your VPN provider?

 

These VPN enabled containers won't run unless the VPN is working correctly if you set it to use the VPN, that's a safety feature to keep you from thinking it's working when it's not, and leaking info.

 

Have you read the general support thread for binhex's dockers? http://lime-technology.com/forum/index.php?topic=45811.0

Link to comment

You are absolutely right! :)

VPN, SAB + Proxy running.

BUT ... i cant access the privoxy webinterface from my windows machine ? Is that "normal" ? "Invalid header received from client."

Yes, that's normal. Enter the privoxy info in the proxy settings for the browser, then visit a page like https://www.whatismyip.com/ and see what external IP is reported compared to visiting the same page without the proxy.

 

BTW, if you are really concerned about privacy and making sure you are not leaking info, you should not continue to use the same browser through the VPN. Tracking cookies and the like will continue to work, and can seamlessly link your VPN and normal profiles.

 

Real privacy is hard, and a subject not well suited for this forum.

Link to comment

Does anyone know if this docker takes advantage of Intel AES-NI for OpenVPN, if one has a CPU which supports it that is?

No idea, it is running a pretty recent version of openvpn so probably yes, tbh unless your running an atom processor then you won't have an issue with the overhead caused by the encryption used by the tunnel, it's quite lightweight.

 

Sent from my LG-V500 using Tapatalk

 

 

Link to comment

Hey, might be a dumb question but I didn't see it in the first couple posts.

 

Is there a way to make sure that traffic is being router through the VPN or as long as the client can download files we're good?. Mostly asking because there are instructions to check just that in the DelugeVPN version.

 

Thanks :D.

Link to comment
  • 2 weeks later...

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.