On 8/8/2019 at 11:42 AM, binhex said:

this doesn't come into play as we are talking about a usenet client here not torrents, all code to determine the incoming port is disabled for this image.

 

your log is clean, showing no issues, so i can only assume that your new ISP (and thus new router perhaps?) is issuing leases on a different network range, can you confirm the ip address of your unraid server is in the range 192.168.1.0/24

Was there an update recently?

It seems to be working properly again and I haven't changed anything.

9 minutes ago, BF90X said:

Was there an update recently?

It seems to be working properly again and I haven't changed anything.

last update was july 10th.

Summary: Fetching NZB from URL works only with internal docker container IP, not with real host IP

 

Description:

 

Some content management application M only send references to NZBs to the downloader as an URL so that the NZB must be fetched by the downloader itself.

 

Imagine that the NZB URL points to NZBhydra2 as meta indexer X running in a docker container A on the same host H where SABnzb is also running in a docker container B. As a result M (running in docker container C on H) wants SABnzb in B to fetch the NZB from X in A.

The containers A, B, C run in their vanilla setting as downloaded (Bridge mode), just the pathes were set properly.

Container A is the linuxserver container with NZBhydra2.

Container B is the binhex container with SABnzbd, OpenVPN and Privoxy.

 

Observation: Depending on how X (NZBhydra2) is referenced in the URL, SABnzbd will be able to fetch the NZB or it will time out, and this can be verify using curl in the container terminal session

What works:

(1) internal IP of container A running NZBhydra / curl 172.17.0.x:5076 works

 

What does not work

(2) external IP of container A running NZBhydra, i.e. real IP of host H / curl "local IP":5076 -> connection refused

(3) local DNS name of H / curl "local dns name":5076 -> Could not resolve host

 

Thoughts:

 

(1) should NOT work, since this IP may change and applications external to the container should always use the real IP address or DNS name of H, could be that OpenVPN treats the container-internal IPs as on the same network and not to be forwarded through the VPN tunnel?

(2) should actually work, could this have to do with OpenVPN, sending traffic for IP of H through the VPN tunnel and nothing answering there? Why would it consider its won hosts real IP address to be on the internet and not on the own end of the tunnel?

(3) reason: if using the binhex SABnzbd-VPN container, within the container local DNS names cannot be resolved because all DNS traffic is sent to the DNS server on the other end of the VPN tunnel

 

My questions (decreasing priority):

-How can I make (3) work? probably some proper setting for OpenVPN for name resolution? which?

-Why does (2) not work and how can I make (2) work?

-Why does (1) work and how can I prevent container-external processes to access container-internal IPs?

 

Thank you for your tme and effort!

 

Edited August 28, 20196 yr by b0m541
additional details

Sabnzbvpn is no longer loading for me. It stops at the following:

dos2unix: converting file /config/openvpn/Switzerland.ovpn to Unix format...

 

Need help. I am new to unraid and want to setup my vpn info but lost on how. I am using vyprvpn service.

I have

VPN_ENABLED = yes

VPN_USER = ***** (My VPN login Name)

VPN_PASS = ***** (My VPN login Pass)

VPN_PROV = custom (Since its not PIA or AirVPN)

VPN_OPTIONS = blank

 

I have put my ovpn file into the openvpn folder it created.

 

But when I try and connect to the GUI it never works, but if I disable the VPN it does. how can/ where can I pull a log.

Edited October 7, 20196 yr by almulder

Need help. I am new to unraid and want to setup my vpn info but lost on how. I am using vyprvpn service.
I have
VPN_ENABLED = yes
VPN_USER = ***** (My VPN login Name)
VPN_PASS = ***** (My VPN login Pass)
VPN_PROV = custom (Since its not PIA or AirVPN)
VPN_OPTIONS = blank
 
I have put my ovpn file into the openvpn folder it created.
 
But when I try and connect to the GUI it never works, but if I disable the VPN it does. how can/ where can I pull a log.

Follow the guide here:-
https://github.com/binhex/documentation/blob/master/docker/guides/vpn.md

Sent from my CLT-L09 using Tapatalk

Could not make it work, so I decided to just sign up to PIA and use it since it seems more geared toward that, and now it works. Thanks.

First, as always Binhex, thank you for doing this for us!

 

I've been beating my head against the wall. So any help would be greatly appreciated.

The moment i disable the VPN, it starts working... but then again... no VPN

I have swapped my network to a full unifi network, but that shouldnt be the cause : 

I am able to connect to the VPN but unable to load up the GUI for sabnzb. Attached is my debug enabled log : 

 

https://pastebin.com/i9JrSE5Y

Edited October 11, 20196 yr by denellum

24 minutes ago, denellum said:

First, as always Binhex, thank you for doing this for us!

 

I've been beating my head against the wall. So any help would be greatly appreciated.

The moment i disable the VPN, it starts working... but then again... no VPN

I have swapped my network to a full unifi network, but that shouldnt be the cause : 

I am able to connect to the VPN but unable to load up the GUI for sabnzb. Attached is my debug enabled log : 

 

https://pastebin.com/i9JrSE5Y

nothing obviously wrong there, you sure this is correct?:-

 

2019-10-11 10:20:04.904522 [info] LAN_NETWORK defined as '10.10.40.0/24'

 

what is your servers ip address and subnet mask?

3 minutes ago, binhex said:

nothing obviously wrong there, you sure this is correct?:-

 

2019-10-11 10:20:04.904522 [info] LAN_NETWORK defined as '10.10.40.0/24'

 

what is your servers ip address and subnet mask?

Yes sir, i have my network well segmented

The server is 10.10.40.40/24

3 minutes ago, denellum said:

Yes sir, i have my network well segmented

The server is 10.10.40.40/24

and the pc you are attempting to connect to the web ui, is that also on 10.10.40.0/24?

1 hour ago, binhex said:

and the pc you are attempting to connect to the web ui, is that also on 10.10.40.0/24?

No, i am on my admin network, which has the ability to traverse : 

https://imgur.com/a/Ml9iYTV

No, i am on my admin network, which has the ability to traverse : 
https://imgur.com/a/Ml9iYTV

It may well have the ability to traverse but iptables will block until you add that network to lan_network. Add it to the existing with a comma to separate.

Sent from my CLT-L09 using Tapatalk

22 minutes ago, binhex said:

It may well have the ability to traverse but iptables will block until you add that network to lan_network. Add it to the existing with a comma to separate.

Sent from my CLT-L09 using Tapatalk
 

OMG, THAT DID IT! Thank you!!!!! Donation coming in after work today

Updated to latest version today and am receiving the following error.  Container won’t start.

 

OpenVPN config file (ovpn extension) is located at /config/openvpn/ipvanish-US-Atlanta-atl-a72.ovpn
/usr/local/bin/init.sh: line 145: /usr/local/bin/dos2unix.sh: No such file or directory

Same, just updated now won't start with the same error.

dos2unix.sh error with latest update as well.

Rolled back to 2.3.9-1-05.  Now working again.

 

looks like 2.3.9-1-06 is not working

Edited October 16, 20196 yr by beaverly72

6 minutes ago, beaverly72 said:

Rolled back to 2.3.9-1-05.  Now working again.

 

looks like 2.3.9-1-06 is not working

Okay, not just me, thanks for the update.

 

Others wanting to know how to downgrade until it's fixed, in the template change the Repository to this "binhex/arch-sabnzbdvpn:2.3.9-1-05"

59 minutes ago, beaverly72 said:

Rolled back to 2.3.9-1-05.  Now working again.

 

looks like 2.3.9-1-06 is not working

 

Same here on Ubuntu 19.04 w/ Docker 19.03.3

Edited October 17, 20196 yr by Maverick0984

Sorry for a n00b question but how do I roll back to an older version? I swear I had read it somewhere but I cannot remember.

 

Thanks

Same here. been wracking my brain for about 2 hours trying to solve this, looks like it was an update (timed perfectly with a docker corruption)

Edited October 17, 20196 yr by rav007
spelling

hi guys, spotted the issue regards dos2unix.sh and corrected it, image now  building, should be done in around an hour.. then pull and you should be back up and running.

9 hours ago, binhex said:

hi guys, spotted the issue regards dos2unix.sh and corrected it, image now  building, should be done in around an hour.. then pull and you should be back up and running.

I can confirm this update fixed things for me.  Thanks!

Just a heads up for those that rolled back, make sure you do a "force update", it didn't just work for me after reverting back to the latest option in the repository.