Here is the list of indexers which require flaresolverr. There are only a handful. iDope and YGG are the biggest ones people complain about, the others are all niche.
https://github.com/Jackett/Jackett/search?l=YAML&q=flaresolverr
According to this https://github.com/Jackett/Jackett/issues/9029:
>Affected trackers: bteye, gktorrent, limetorrents, pornleech, torrent9clone, torrentz2, zetorrents (could be more because they enable/disable Cloudflare on demand)
It's odd that the db corrupted the moment I switched from using Nord in gluetun to Mullvad (OpenVPN to Wireguard) Apparently there's a problem with having the config files not stored locally? I have them on the removable storage. I'm not sure if that's what they mean.
I tried this: but when I enter ".recover" it just tells me "SQL error: unable to open database file" which isn't particularly helpful.
I'm now on the hotio/qbittorrent container with Mullvad VPN setup through wireguard. Below is my docker compose, am I port forwarding correctly? Do I have to do anything different for the wg0 file?
version: "3.7"
services: qbittorrent: container_name: qbittorrent image: ports: - "8080:8080" - "8118:8118" environment: - PUID=1000 - PGID=1000 - UMASK=002 - TZ=Etc/UTC - VPN_ENABLED=true - VPN_LAN_NETWORK=192.168.1.0/24 - VPN_CONF=wg0 - VPN_ADDITIONAL_PORTS=55335/tcp - VPN_IP_CHECK_DELAY=5 - PRIVOXY_ENABLED=false volumes: - /docker/qbittorrent/config:/config cap_add: - NET_ADMIN sysctls: - .src_valid_mark=1 - .disable_ipv6=0 restart: unless-stopped
Also, how do I get Prowlarr to use Qbittorrent's vpn connection?
I can’t see where those quotes are from, but I set this up using this guide from Mullvad, so I am confident it is secure Checking for leaks is even one of the steps.
hi there, i did add the port to the deluge container in the initial setup.
​
for troubleshooting, i downloaded the NordVPN container to see if that would work but i get the same problem where the webui isnt responding
Not a Sonarr nor Prowlarr issue exactly
It's part of the global SSL certificate issue caused by let's encrypt root cert expiring.
https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
Likely something you need to resolve on your host for it to trust the replacement certs
Nyaa doesn't support seasons? (AoT as an example) You can type something like this or most of the other terms that Prowlarr queried TPB with and it returns results though. I remember when I tried using jackett around a year ago it worked fine for episodes or seasons but you might be right as Jackett won't query in Nyaa either.
A log for nyaa -> attack on titan S4 in Jackett is logged as
Torznab search in Nyaa.si => Found 100 releases (from cache)
Which is just an empty search while TPB -> vamp diaries S7 logs as
Torznab search in The Pirate Bay for Vampire Diaries S07 => Found 6 releases
Logs don't really indicate anything but a screenshot like this also doesn't show much so I didn't include one. With TPB I would have thought doing a search within Prowlarr would yield the same results as Sonarr doing a search with the same filters. From the logs in Prowlarr, the terms and categories seem to be the same, and the only thing different in the query is the limit and I don't think that would make a difference in the result. What do you mean by "bot's gathering logs link"?
The only thing it could be then is if there is no download link in the results then Radarr/Sonarr/Readarr/Lidarr outright ignore them. logging for this was recently added to nightly; which would mean possibly an issue with rutracker and prowlarr
https://github.com/Lidarr/Lidarr/commit/3ac24013045efe80793a6f7e7b0c13cce9c2fed2
any adblock or pihole blocking it?
Looks like your issue is gonna be around the SSL error which something is prematurely terminating your connection.
Also try the alt URLs if you haven't already
> 2021-08-12 01:45:21.5|Trace|HttpClient|Req: [GET] https://torrentgalaxy.to/galaxyfence.php?f 2021-08-12 01:45:21.5|Trace|Http|Res: 1288 [POST] /api/v1/indexer/action/getUrls: 200.OK (6 ms) 2021-08-12 01:45:21.5|Trace|ConfigService|Using default config value for 'proxyenabled' defaultValue:'False' 2021-08-12 01:45:21.5|Debug|Api|[POST] /api/v1/indexer/action/getUrls: 200.OK (6 ms) 2021-08-12 01:45:21.8|Error|Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware|An unhandled exception has occurred while executing the request.
> [v0.1.0.768] System.Net.WebException: The SSL connection could not be established, see inner exception. ---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.