Thanks. It seems like the IPv6 address dropped off the server for some reason, and I can't seem to get it back. So I've just removed it from DNS, so it should work without you needing the workaround any more.
Hi, I've been noticing some weird timeout behaviors on my Sonarr host over the last few days, and I think its because of the IPv6 address configuration. I can force a connect with IPv4 by turning off IPv6. But the moment I turn on IPv6 again I am getting timeout errors. This is likely because Sonarr is aggressively trying to connect by IPv6.
I hope you don't mind me sharing some scans.
$ nmap -Pn -p 443 feed.animetosho.torrentbay.st Starting Nmap 7.92 ( https://nmap.org ) at 2022-07-30 12:17 PDT Nmap scan report for feed.animetosho.torrentbay.st (163.172.88.174) Host is up (0.15s latency). Other addresses for feed.animetosho.torrentbay.st (not scanned): 2001:bc8:32d7:10a::1 rDNS record for 163.172.88.174: 163-172-88-174.rev.poneytelecom.eu
PORT STATE SERVICE 443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 0.27 seconds
$ nmap -6 -Pn -p 443 feed.animetosho.torrentbay.st Starting Nmap 7.92 ( https://nmap.org ) at 2022-07-30 12:17 PDT Nmap scan report for feed.animetosho.torrentbay.st (2001:bc8:32d7:10a::1) Host is up. Other addresses for feed.animetosho.torrentbay.st (not scanned): 163.172.88.174
PORT STATE SERVICE 443/tcp filtered https
Nmap done: 1 IP address (1 host up) scanned in 2.12 seconds
Comment in Feedback 27/07/2022 00:13 * — Anonymous: "Manie Castiglione"
[spam]
Comment in Feedback 26/07/2022 02:02 * — Anonymous: "Tanesha McLaughlin"
I can't see any obvious delays around the time you posted. Would you happen to have further info, e.g. the last entry showing here vs what's at Nyaa, and for how long the discrepancy lasted?
if it's in the wrong category on nyaa, the best thing to do is contact the group/poster to get it corrected on nyaa. then it will get auto added here, if it's recent.
06/08/2022 10:56 — admin