44 minutes ago, binhex said:

this is expected, firefox will NOT route dns queries over privoxy, it is a http/https proxy only.

 

For anyone interested, you can prevent DNS leaks when running Firefox through Privoxy by also enabling SOCKS5. Instructions for setting this up with Mullvad  can be found here.

Any ideas on why privoxy keeps restarting with this update?

I am on the latest Docker Version, and ever since I updated the Docker the Autoremoveplus plugin wont load anymore, I just get a error "Cannot enable non-existent plugin AutoRemoveplus" I did not change anything other than updating the container, just wondering if anyone else has experienced this? I have been using AutoRemovePlus-2.0.0-py3.8.egg. If no one is having the issue, I will try and roll back to see if this caused the issue or not

7 hours ago, orlando500 said:

 

Im having problems with binhex-radarr connection to binhex-delugevpn for downloads. 

 

binhex-sonarr with setup like this is working:

 

 

@binhex any clues where i should start checking?

Im having the same issue.. sonar and radarr both broken.
I use letsencrypt still...
Nothing has changed in my setup lately except updating 

tried changing IP to localhost
i get " Unable to Connect "

how can i roll back deluge?

 

adding the previous tag after a : to the repository didnt work...

 

binhex/arch-delugevpn:2.0.4.dev38+g23a48dd01-3-02
no worky

31 minutes ago, TRusselo said:

Im having the same issue.. sonar and radarr both broken.
I use letsencrypt still...
Nothing has changed in my setup lately except updating 

tried changing IP to localhost
i get " Unable to Connect "

 

 

I am having the same issue as well. Was working fine previously.

14 minutes ago, Kalembang said:

 

 

I am having the same issue as well. Was working fine previously.

Just been trying to fix this for the last hour. Came here and see I'm not alone, same as above screenshots. I will  stop mucking around and check back tomorrow

@BackupAddict @TRusselo @orlando500

 

Think I fixed it! If you guys want to try this as well. I went into Sonarr/Radarr WebUI and updated the "Host" attribute with in Settings > Download Clients:


I had to change it from 192.168.1.* to the listed IP address for Deluge found below:

 

I also had to assign a fixed IP to the Jackett application:

 

 

Once that was set to a fixed IP. I had to go and update all my indexers with in Sonarr/Radarr to use that IP address instead of the 192.168.1.*.

 

 

 

Hope it helps you guys out!

 

 

 

Edited February 28, 20215 yr by Kalembang

On 2/25/2021 at 9:44 PM, gordonempire said:

To roll back, I changed the repository from:

binhex/arch-delugevpn

To:

binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-3-01

Thank you.  I tried 'localhost' - no dice.  I tried adding my container ports to the ADDITIONAL_PORTS section and restarted all containers.  No dice.

This was my only solution.  I just spent 30 hours over 2 days on a work-related issue and I just don't have any time to really fight this right now.

 

My Unraid server sits behind an edge firewall switch and a secondary firewall.  Also - why is this container still using iptables?

Edited February 28, 20215 yr by Jason Harris

Noticed none of my plugins load anymore, anyone else had this issue since the last update ?

37 minutes ago, tjb_altf4 said:

Noticed none of my plugins load anymore, anyone else had this issue since the last update ?

I noticed we are on Python 3.9.2, not sure if this is recent or not, but I've read a number of plugins break above 3.7 ?

 

My Unraid server sits behind an edge firewall switch and a secondary firewall.  Also - why is this container still using iptables?

Just out of curiosity, what do you think it should use instead of iptables? They seem well suited to the task at hand of stopping any data leaking outside the VPN tunnel?


Sent from my iPhone using Tapatalk

31 minutes ago, tjb_altf4 said:

I noticed we are on Python 3.9.2, not sure if this is recent or not, but I've read a number of plugins break above 3.7 ?

Rolled back to 2.0.4.dev38_g23a48dd01-3-01 (latest prior to updates in last few days).

All plugins working again, Python version on this tag is 3.8.6

 

@binhex any chance we can run the slightly older version, rather than cutting edge Python ?

3 hours ago, Kalembang said:

@BackupAddict @TRusselo @orlando500

 

Think I fixed it! If you guys want to try this as well. I went into Sonarr/Radarr WebUI and updated the "Host" attribute with in Settings > Download Clients:


I had to change it from 192.168.1.* to the listed IP address for Deluge found below:

 

I also had to assign a fixed IP to the Jackett application:

 

 

Once that was set to a fixed IP. I had to go and update all my indexers with in Sonarr/Radarr to use that IP address instead of the 192.168.1.*.

 

 

 

Hope it helps you guys out!

 

 

 

 

thanks.. i just updated again to a new build of delugevpn and vollah. everything worked again without changing a bit... 

24 minutes ago, tjb_altf4 said:

Rolled back to 2.0.4.dev38_g23a48dd01-3-01 (latest prior to updates in last few days).

All plugins working again, Python version on this tag is 3.8.6

 

@binhex any chance we can run the slightly older version, rather than cutting edge Python ?

i will take a look, but this could be more tricky than expected, as arch linux is a rolling distro and thus other utilities may expect and rely on the latest python version in the arch repo.

I am also having the plugin issue, if this won't have a solution soon, how do I roll back to a specific release?

Edited February 28, 20215 yr by SubbyDew

6 minutes ago, SubbyDew said:

I am also having the plugin issue, if this won't have a solution soon, how do I roll back to a specific release?

You add a colon and the release number after the name in the repository field.

Example-  binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

21 hours ago, Antibios said:

I tried putting -2.0.4.dev38+g23a48dd01-3-01 at the end of the "repository" field and the "docker" field but it wont pull at all if I do that.

Sorry, I gave you bad info. It's not a dash it's a colon.

17 minutes ago, wgstarks said:

Sorry, I gave you bad info. It's not a dash it's a colon.

I have tried this and i find that it his fails and the created  orphan template.

54 minutes ago, chris_netsmart said:

I have tried this and i find that it his fails and the created  orphan template.

You should attach a screenshot of the run command along with the failure message. Blank out any passwords/users.

I have run the update three times yet unraid keeps showing update available?

2 hours ago, SubbyDew said:

I am also having the plugin issue, if this won't have a solution soon, how do I roll back to a specific release?

I've just (ten minutes ago) loaded the latest update, and the AutoAdd plugin seems to be working once again.

Do we have any solutions or ideas regarding privoxy constantly restarting?

 

2021-02-28 13:27:15,678 DEBG 'watchdog-script' stdout output:

fo] Privoxy not running

2021-02-28 13:27:15,681 DEBG 'watchdog-script' stdout output:

[info] Attempting to start Privoxy...

2021-02-28 13:27:16,692 DEBG 'watchdog-script' stdout output:

[info] Privoxy process started

[info] Waiting for Privoxy process to start listening on port 8118...

2021-02-28 13:27:16,701 DEBG 'watchdog-script' stdout output:

[info] Privoxy process listening on port 8118

2021-02-28 13:27:46,797 DEBG 'watchdog-script' stdout output:

fo] Privoxy not running

2021-02-28 13:27:46,800 DEBG 'watchdog-script' stdout output:

[info] Attempting to start Privoxy...

2021-02-28 13:27:47,811 DEBG 'watchdog-script' stdout output:

[info] Privoxy process started

[info] Waiting for Privoxy process to start listening on port 8118...

2021-02-28 13:27:47,820 DEBG 'watchdog-script' stdout output:

[info] Privoxy process listening on port 8118

11 hours ago, Jorgen said:

Just out of curiosity, what do you think it should use instead of iptables? They seem well suited to the task at hand of stopping any data leaking outside the VPN tunnel?


Sent from my iPhone using Tapatalk

Fair question - firewalld is my response.  But I come from EL7/EL8 land, and firewalld replaced iptables there.

updated to new build, still having issue with sonarr / radarr not communicating with deluge.