3 hours ago, superloopy1 said:

Both instances use port 8118 as vpn port though. That appears to be the problem. Closing the first app, in this case delugevpn terminates the vpn it seems and my sabnzbdvpn connection goes down?

Sent from my LG-D855 using Tapatalk
 

But you should be able to map them to different ports so they aren't using the same port. That's the whole point of port mapping.

But you should be able to map them to different ports so they aren't using the same port. That's the whole point of port mapping.

Mapping to another port doesnt seem to work. If the other instance is running, eg delugevpn, then sab wont start on another port than 8118 and vice versa, i've tried. Problem seems to be multiple instances using the same port which seems wrong anyway. I can gave EITHER sab or deluge using vpn on privoxy (which appears to be the underlying problem) port 8118 but not both.

Sent from my LG-D855 using Tapatalk

12 minutes ago, superloopy1 said:

Mapping to another port doesnt seem to work. If the other instance is running, eg delugevpn, then sab wont start on another port than 8118 and vice versa, i've tried. Problem seems to be multiple instances using the same port which seems wrong anyway. I can gave EITHER sab or deluge using vpn on privoxy (which appears to be the underlying problem) port 8118 but not both.

Sent from my LG-D855 using Tapatalk
 

What are your port mappings for each?

yep, but with the docker container, what you are doing is assigning a 'new'port to the container

 

think like this - all your containers have a web gui and they all listen on port 80

 

you could never get to all of them, as they are all on port 80

 

what you have to do, it say

 

delugevpn port 8118 > MAP TO xxxx (another port number)

sabznb port 8118 > MAP TO xxxx (either 8118, or if thats in use, another port number)

what your doing then, is connecting to the app on the new port you have suggested, and that is passed through to the docker and maps to the actual port it needs

yep, but with the docker container, what you are doing is assigning a 'new'port to the container
 
think like this - all your containers have a web gui and they all listen on port 80
 
you could never get to all of them, as they are all on port 80
 
what you have to do, it say
 
delugevpn port 8118 > MAP TO xxxx (another port number)
sabznb port 8118 > MAP TO xxxx (either 8118, or if thats in use, another port number)
what your doing then, is connecting to the app on the new port you have suggested, and that is passed through to the docker and maps to the actual port it needs

I think the problem lies with Privoxy in a way that i dont understand. Changing either container to another port to avoid clashing doesnt work. The changed server wont start. It seems that i need some way of keeping the privoxy channel up and running to multiple users of port 8118?

Sent from my LG-D855 using Tapatalk

Just to make absolutely sure we aren't talking past each other, could you please answer this question?

41 minutes ago, trurl said:

What are your port mappings for each?

 

Or just post a screenshot of your Docker page.

Or just post a screenshot of your Docker page.

Port mappings are as per original. As i say thw only change i tried was to move one of the containers to use privoxy on 8119 instead of 8118 to avoid clash. I'll see if i can grab a screenshot ...

Sent from my LG-D855 using Tapatalk

So I maybe don't really understand how privoxy plays into this. Are you saying privoxy won't allow you to use a different port for deluge, for example?

 

Or do you just not know how to map delugevpn port 8118 to a different host port?

 

While it is true that both applications will want to use port 8118, that doesn't mean that one of the applications can't remap container port 8118 to another host port. That is the whole point of docker port mapping, to allow a container to use the port it thinks it should use, but to map that container port to a different port on the host so that different host ports are used when communicating on the network and internet.

21 hours ago, superloopy1 said:

I think the problem lies with Privoxy in a way that i dont understand. Changing either container to another port to avoid clashing doesnt work. The changed server wont start. It seems that i need some way of keeping the privoxy channel up and running to multiple users of port 8118?
 

Don't enable privoxy in both. It's unnecessary, and complicates things way too much, as you found out. The VPN works regardless of whether privoxy is enabled, privoxy is just a way to pass the already existing VPN  tunnel along to browsers or other metadata fetchers that you wish to use the VPN for.

 

TLDR; disable privoxy in one of them, doesn't matter which one. Everything will still work the way it's supposed to.

Don't enable privoxy in both. It's unnecessary, and complicates things way too much, as you found out. The VPN works regardless of whether privoxy is enabled, privoxy is just a way to pass the already existing VPN  tunnel along to browsers or other metadata fetchers that you wish to use the VPN for.  

TLDR; disable privoxy in one of them, doesn't matter which one. Everything will still work the way it's supposed to.

 

You sure? If so, then that just confirms that i need to give up on all of this sab, deluge, sonarr, radarr docker stuff and get back on the desktop. My understanding was that, if used, then privoxy could accomodate all traffic. Both delugevpn and sabnzbdvpn have a privoxy option to do this. Are you saying that they dont need to be used and that privoxy would handle any torrent/usent traffic automatically? The vpn side of things is working just fine, i dont see the link between it and my vpn.

Sent from my LG-D855 using Tapatalk

 

 

 

 

 

16 hours ago, jonathanm said:

Don't enable privoxy in both.

 

2 hours ago, superloopy1 said:

You sure?

Yes, definitely.  There is no point or need to enable privoxy in both.  Privoxy lets non-VPN enabled applications "piggy-back" on a Docker with a VPN connection.  There's no need to enable two Dockers to give VPN piggy back rides, and you're hitting port conflicts as you try to do it.

 

2 hours ago, superloopy1 said:

My understanding was that, if used, then privoxy could accomodate all traffic.

One instance should be able to handle any browsers or fetchers you need.  However, those applications need to allow a proxy setting.

 

2 hours ago, superloopy1 said:

If so, then that just confirms that i need to give up on all of this sab, deluge, sonarr, radarr docker stuff and get back on the desktop.

I don't know why?  You've almost got this working.  Just turn off privoxy in Deluge and leave it running in Sab (or vice versa).  Then anyone who needs a secure proxy just asks for tower:8118.

I don't know why?  You've almost got this working.  Just turn off privoxy in Deluge and leave it running in Sab (or vice versa).  Then anyone who needs a secure proxy just asks for tower:8118.

Ok but i still dont understand why both delugevpn AND sabbzbdvpn have privoxy options to enable? Is the privoxy just there to hook other apps to or is it there to protect deluge and sab? Must admit i thought thr latter and that as a further benefit the likes of sonarr and radarr etc could also piggyback. Am i wrong in thinking that privoxy primarily protects my torrents or usenet access from ads etc. Surely both will need to be privoxied? I think i'll just remove delugevpn and be done with it. Most probably not that interested in torrenting, too much hassle. 

Sent from my LG-D855 using Tapatalk

 

 

 

 

 

4 hours ago, superloopy1 said:

Ok but i still dont understand why both delugevpn AND sabbzbdvpn have privoxy options to enable?

Because not everyone runs both of them.

 

4 hours ago, superloopy1 said:

Is the privoxy just there to hook other apps to or is it there to protect deluge and sab?

Mostly to give piggy back rides to other apps that don't have built in VPN but do have proxy capabilities.

 

4 hours ago, superloopy1 said:

Am i wrong in thinking that privoxy primarily protects my torrents or usenet access from ads etc.

Yeah, sorry - that's not primarily what it's doing.  It has very little to do with "protecting" sab or deluge.  VPN does that.  Privoxy is a non-caching web proxy, and in this case it's there to help other applications take advantage of the VPN that's built into the container.  You can use privoxy without a VPN as well, and it does some nice filtering - but the primary value in this situation is to provide VPN piggy back rides.

 

4 hours ago, superloopy1 said:

I think i'll just remove delugevpn and be done with it.

Entirely up to you, but all you need to do is turn privoxy off within Deluge to get things up and running.  I'd suggest leaving privoxy enabled in Sab since you will probably run Sab all the time, and turn it off in Deluge which you may only run once in a while.

 

Entirely up to you, but all you need to do is turn privoxy off within Deluge to get things up and running.  I'd suggest leaving privoxy enabled in Sab since you will probably run Sab all the time, and turn it off in Deluge which you may only run once in a while.  

 

So what 'protects' deluge if i choose to keep it running? I think my problem here is conceptual and maybe just an open privoxy through which anything and everything runs against would be an easier way to appreciate whats being offerred up. I'm going to remove delugevpn as i cant get my head around it being left 'open' without an instance of privoxy behind it on my system. Everything else i see hanging together, vpn is running aok and privoxy is handling the other bits that i 'think' it should.  Now i just need to make it do something ...

Sent from my LG-D855 using Tapatalk

 

 

 

 

 

Hmm.  What are you thinking privoxy is doing for you?

Hmm.  What are you thinking privoxy is doing for you?

I just dont see how delugevpn can be utilising privoxy if i dont have it pointing to it through port 8118 in the docker.

 

Sent from my LG-D855 using Tapatalk

 

 

 

5 hours ago, superloopy1 said:

I just dont see how delugevpn can be utilising privoxy if i dont have it pointing to it through port 8118 in the docker.

The VPN enabled apps don't utilize privoxy themselves at all. They connect directly through the VPN. Turning privoxy on is totally optional, and doesn't affect the primary app at all.

 

Privoxy is NOT a necessary part of the docker for VPN secure access by the named app, be it SAB, Deluge, whatever. It is ONLY used by apps EXTERNAL to the named docker, by filling in a proxy field to tell the external app or browser where to look for an internet connection. When you do that, it adds the traffic from the external app to the already established VPN tunnel in the primary named app docker.

The VPN enabled apps don't utilize privoxy themselves at all. They connect directly through the VPN. Turning privoxy on is totally optional, and doesn't affect the primary app at all.
 
Privoxy is NOT a necessary part of the docker for VPN secure access by the named app, be it SAB, Deluge, whatever. It is ONLY used by apps EXTERNAL to the named docker, by filling in a proxy field to tell the external app or browser where to look for an internet connection. When you do that, it adds the traffic from the external app to the already established VPN tunnel in the primary named app docker.

Sorry guys but i have to give up on this one. Just cant understand why there'd be a privoxy option if its not going to be utilised. Vpn i understand and seems to be working ok but surely its deluge that uses yhe privoxy as well as external apps? Would i better just running a standalone instance of privoxy and switching it off in both deluge and sab then? One more docker overhead i suppose ...

Sent from my LG-D855 using Tapatalk

1 hour ago, superloopy1 said:

surely its deluge that uses yhe privoxy as well as external apps?

No. Deluge goes directly through the VPN tunnel, it doesn't use the privoxy part at all. The option is there ONLY for external apps to be able to share the already established tunnel.

No. Deluge goes directly through the VPN tunnel, it doesn't use the privoxy part at all. The option is there ONLY for external apps to be able to share the already established tunnel.

Ok, as you keep saying. But for those people running deluge, not binhexs vpn enabled version, how do they use privoxy? Or do they not bother? I'm trying to follow SIO's videos, and very informative they have been so far, but this whole privoxy thing is a strange way of doing things within a client container IF it's not even necessary to the application itself. Would make more sense for it to gave been in sonarr or radarr containers surely? Keep this going please because i'm getting a lot from it. Total novice but to date i now have openvpn, vpn and all usenet apps working after a fashion. Understanding how and why privoxy is/is not needed would be the icing on the cake! Until the next question [emoji2]

Sent from my LG-D855 using Tapatalk

It's hard to offer advice.  You seem to feel strongly that privoxy is doing something *really* important to help deluge and sab.  But they're not even doing standard http traffic that would take advantage of a web proxy, they're doing API traffic to upload/download files.  Privoxy is a helper application in this context and many people find it really convenient that's its bundled in with deluge and sab.

Edited February 26, 20188 yr by tdallen

It's hard to offer advice.  You seem to feel strongly that privoxy is doing something *really* important to help deluge and sab.  But they're not even doing standard http traffic that would take advantage of a web proxy, they're doing API traffic to upload/download files.  Privoxy is a helper application in this context and many people find it really convenient that's its bundled in with deluge and sab.

So are you saying its not really worth enabling it, it doesnt offer any real benefit?

Sent from my LG-D855 using Tapatalk

6 minutes ago, superloopy1 said:

So are you saying its not really worth enabling it, it doesnt offer any real benefit?

Depends on if you want to use your already established VPN tunnel to allow traffic for other apps, like sonarr, radarr, etc.

 

You are correct in saying it doesn't do anything with the named app in the docker. Deluge or SAB don't use it, it's only for external apps. If you want to use your VPN for Sonarr, it's a handy way of doing it without needing another separate VPN connection, you just use the one already established by the delugevpn docker.