RollinDolan

Suddenly today I'm getting 2021-04-26 09:16:36,438 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... This error comes after a couple rounds of 2021-04-26 09:14:01,357 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'... 2021-04-26 09:14:29,394 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'... 2021-04-26 09:14:57,431 DEBG 'start-script' stdout output: [info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'... Is this something related to PIA? I haven't changed anything lately and it worked yesterday. I'm using: Wireguard with PIA Swiss endpoint in the wg0 file Swiss > France > De-Berlin > De-Frankfurt for my openVPN config file I'm also now unable to upload / download. Deluge WebUI opens, but all my torrents are 0 up and 0 down.

Right, thanks. I tried that - no dice. However, I'm now noticing that my deluge docker logs are showing "Sending 'down' command to WireGuard due to dns failure" I didn't change my wireguard configs. I didn't change any of my PrivateInternetAccess config. I didn't change anything related to DNS / name servers. This worked yesterday. Sigh... guess I'll figure out what else got broken from the update.

Sorry, I should have been more specific. By "just work", I meant that binhex's post looked like I should not need to route anything through the VPN container. I did not previously route anything through the VPN container - instead, I just told Jackett to use privoxy as its proxy. The "working solution" for Sonarr and Radarr is routing them through the VPN container. I already have a working method to that (using Jackett in Sonarr and Radarr). Note - Jackett through privoxy in lieu of everything-through-container seems to be binhex's preferred method. Yet we can't get guidance on it. To answer your above question - I'm on Unraid 6.9.0 I also tried wgstarks' method: I used ifconfig to get the local IP of my docker container (I wasn't sure if you meant the deluge docker or the jackett docker, so I tried both...) and it didn't work. Same errors after saving the new IP through the Jackett gui. It was a very similar looking 172.xxx address.

As another point that privoxy should "just work", it looks like binhex stated we shouldn't need to do all this setup if we just want to use privoxy as usual. Here's the post. Maybe I'm misunderstanding. Now, what should we do? That I don't know.

So I tried that earlier, but I tried again just to confirm. There's the start of Q24 from the FAQ... Here's what I changed my Jackett container to: Added the extra parameter as dictated. I assume "binhex-delugevpn" is the VPN container name? If not, I don't know what is. Switched Network type to none Removed what used to be the first environment variable. It was the port setting, which was previously 9117. Unfortunately, this results in a failed Docker restart. "The command failed." And then my docker page shows an orphan image where binhex-jackett used to be. So something isn't right. Thanks for the help so far. I'm eager to go down the path of binding Jackett to the VPN container. However, it seems awfully strange that Jackett literally has a setting for this (which would allow me to tell Jackett to just use privoxy), and we're unable to do that anymore...

Unfortunately that does not change anything. Using the IP of my Unraid server in lieu of "tower" still yields the same error message when I try to test my indexers in Jackett.

I am using Privoxy. I am using Privoxy in jackett. Is anyone else familiar with this topic, or experiencing similar issues? I'll try to be more descriptive. Config: Jackett (all these settings are from Jackett's web GUI) Server port: 9117 Proxy type: HTTP Proxy URL: tower Proxy port: 8118 Web GUI is accessible after update All configured indexers fail after update. When I test them, I get one of two errors: "Exception (<indexer-name> Unexpected character encountered while parsing value: <. Path '', line 0, position 0.: Unexpected character encountered while parsing value: <. Path '', line 0, position 0." "Found no results while trying to browse this tracker" Radarr (all these settings are from Radarr's web GUI) Port number: 7878 Proxy: enabled, HTTP(S), hostname=tower, port=8118, "Bypass Proxy for Local Addresses"=Yes Note - I'm not sure if I even need to enable this proxy, if I'm also using Jackett for all my indexers, and Jackett is (supposed to be) through Privoxy Download client - set to Deluge (I give the hostname "tower", password, etc. This is still working and accessible from Radarr, even after the delugeVPN update Indexers: 4 indexers using the Torznab and API info from Jackett. They all worked pre-update. Now, all indexers fail in Radarr. I get one of two error messages when testing them: "Query successful, but no results were returned from your indexer. This may be an issue with the indexer or your indexer category settings." "Unable to connect to indexer, check the log for more details" Sonarr (all these settings are from Radarr's web GUI): Same as radarr, except the port number is 8989 DelugeVPN ENABLE_PRIVOXY = yes LAN_NETWORK = 192.168.86.0/24 Web GUI IS accessible, even after update It seems that my issue is Jackett? I can't access my indexers on Jackett, and so Radarr and Sonarr cannot use them either. EDIT - Binhex's FAQ number 26 says Is this not what I am doing above? I have set up Jackett to use privoxy by setting the proxy url / port to tower / 8118 I have configured Radarr and Sonarr to use Jackett as an indexer by adding my indexers with Jackett's torznab links.

Thanks for the tip on the server IP. As for the first issue (Jackett) - shouldn't I NOT do that, if I'm trying to use Jackett as recommended. (As opposed to routing Sonarr and Radarr each through privoxy individually.) No worries. I'll just wait for someone to come along and ask the exact same question so we can both find a solution.

Sorry, can you explain this? Deluge does not have "ignored addresses" in its proxy settings. Do you mean I should change the "ignored addresses" in the proxy settings for Radarr and Sonarr? Because as stated, Sonarr and Radarr aren't having any issues connecting to Deluge. The issue is that Jackett cannot connect to any indexers ("Found no results while trying to browse this tracker"), which I think means Jackett cannot talk to Privoxy? I just want things to function as they originally did EDIT - is there also no way to set the IP address to the name of my unraid server? It would be much easier to maintain if I could enter "tower" rather than an IP address which isn't guaranteed to remain static.

From the new FAQ Q26: What does this mean? After updating: I can still access the deluge web gui Radarr and Sonarr can access deluge successfully Radarr and Sonarr (which were/are configured to use Jackett) can NOT access any indexers Jackett, which was set to use privoxy, cannot access any of its indexers. What config changes am I supposed to make to Jackett to get things working again? Thanks!