xxDeadbolt

Hey - I've moved over to this & having a little issue. I've got it set up, added Radarr/Sonarr & Qbit VPN (all your containers), but when I tell Prowlarr to use the proxy, I can't connect to Qbittorrent. Radarr & Sonarr still connect, though, & all my indexers test OK which some don't when proxy is off. Can't quite figure out where I'm going wrong, tried testing Firefox on a different machine on the LAN to check the proxy was working, which it is. Any nudges in the right direction would be appreciated... (didn't provide any info on the mappings as I wasn't 100% sure if it was Prowlarr or Qbit, but if anything is needed let me know)

It's set to use /tmp

Strange, I've literally just dealt with this about an hour ago (it was sitting at around 40Gig!). I used the unraid terminal to delete the numbered folder, & it's contents, in the Sync+ directory. Wasn't sure if just deleting the Sync+ folder would make a difference, but decided to just keep it and delete everything in it. So far, no issues.

Yep, UPnP was enabled. So, I'd already set the port forward manually... I just didn't think to try completing the set up & seeing if it worked anyway. That error made me fixate on it; however, it's set up & connecting fine. Thanks for the nudge, not sure why the UPnP client isn't playing ball with my router, but it works!

Trying to set this up & encountering an issue with UPnP/port forwarding. I'm getting the remark "UPnP: forwarding not set" & "The Local endpoint resolves to xx.xx.xx.xx. In most cases, this should be your public WAN IPv4 instead: xx.xx.xx.xx", where xx.xx.xx.xx show my correct public IP, on both mentions in the message. This is the port forward on my router: & it also shows UPnP is enabled: I'm using DuckDNS & it's working fine for other services, but this just doesn't seem to change. I've also set the "Local gateway uses UPnP" setting to both yes & no, with no change. When set to No, it shows "Remark: configure your router with port forwarding of port 51820/UDP to 192.168.0.103:51820" instead of "UPnP not set" & when set to yes, it just says the message as above. I don't have anything special/complex going on in terms of my network, so not entirely sure what's going on. Anyone any pointers?

Getting the same thing here, can't see anything in the syslog either. Possibly the update itself?

That’s weird, I checked the language thing & Chrome was set to ‘English’ in there, too. I changed it to ‘English (UK)’ and removed any other variant, relaunched but still the same behaviour. However, I’d gone to the ‘Manage extensions’ setting, as I’d realised I had more than the 2 I’d mentioned before (they were hidden, instead of displaying on the toolbar, so slipped my mind) Disabled them and the search started working. Enabled them one by one, but it worked each time. So I’m not sure which one was interfering, but it seems one of them was. If this behaviour starts again, I’ll disable one at a time & check again, but it seems to be working again for now. Cheers

Updated to latest version of CA & getting new behaviour, when searching, in this pop up error message: Here's the console errors: Edit: Forgot to add CA debugging log CA-Logging-20210516-1832.zip

Search doesn't work at all. Autocomplete will show things as I type, but hitting enter, or clicking on one of the autocomplete options, does nothing.

Sorry to piggyback, I'm also getting this behaviour in Chrome & Brave. Firefox sometimes/rarely works, at first attempt, then I get this issue. I don't have any add-ons in FF, Chrome only has Bitwarden & iCloud bookmarks. Strange.

Mine has been working for a couple of weeks now with everything configured as above. Only problem I had was self-inflicted, where I initially entered the variable value as 'hcaptcha_solver' instead of 'hcaptcha-solver'

Mine has a few more lines, though most autopopulated. I chose the Berlin endpoint, that's all I needed to manually edit: [Interface] Address = *[redacted]* PrivateKey = *[redacted]* PostUp = '/root/wireguardup.sh' PostDown = '/root/wireguarddown.sh' [Peer] PublicKey = *[redacted]* AllowedIPs = 0.0.0.0/0 Endpoint = de-berlin.privacy.network:1337 Forgot to say, I'm running rTorrentvpn, not Delugevpn, but the vpn config info should be pretty much the same (as far as I know)

See the recommended post at top

Same here, with the same 3 items.

Awesome, 6.9.0 > 6.9.1 done. All seems to be running as expected. Thanks again!

Just updated from 6.8.3 > 6.9 with no issues (so far).

haha yeah that's it. I can't remember setting the proxy manually in radarr/sonarr tbh, so I must've done it a long time ago & never had a reason to change it before now. All working fine now though 🙂

Can I check - is the privoxy/port 8118 not able to be used with the iptable tightening now? I used the same proxy settings on radarr/sonarr and the indexers were failing in them until I removed it. I'm not entirely sure I need the proxy on them, tbh, when the indexer traffic is being routed through the vpn on rTorrent, but just wondering if this is what's affecting it.

Think it's fixed now - for some reason, I had the proxy settings set to use the rTorrent/privoxy port 8118 in my jackett settings. I removed that, since it's routing through the container anyway and it's fine now. Cheers again!

Yeah I've restarted jackett a couple of times, but still failing.

Strange, all my indexers are failing now 😕

Awesome, sorted! I assume this is the case, but just to double check: am I ok to delete the manual key I created for jackett to run through it, now that it's in the additional_ports? Edit: Oops, tried it and it broke again. Sorted once I added it back 🤣 Cheers binhex!

Yup, routing it through your rTorrentvpn container.

Anyone having issues accessing the gui? Seems to have just been today for me. Logs look fine, just can't access gui & Radarr/Sonarr both say indexers down. This is Jackett log: 2021-02-25 12:24:57,088 DEBG 'jackett' stdout output: 02-25 12:24:57 Info Jackett startup finished in 2.346 s 2021-02-25 12:24:57,088 DEBG 'jackett' stdout output: Hosting environment: Production Content root path: /usr/lib/jackett/Content Now listening on: http://[::]:9117 Application started. Press Ctrl+C to shut down. Radarr/Sonarr just show a 503:ServiceUnavailable message.

I realise this will sound a little self-involved - but, if I'm not entirely sure what pyrocore is, then I assume I'll not be affected in any significant way with this change?😆