Filebot Fails to rename series.
Filebot Fails to rename series.
Filebot has stopped renaming TV Series. It still renames movies. I get Network Connection error : Connection reset by peer.
Re: Filebot Fails to rename series.
Sounds like a generic network error...
Are you using a VPN?
Which database are you using? Have you tried using a different database?
What does the Error Log say?
Re: Filebot Fails to rename series.
I am not using VPN.
I was using the TVDB.
I edited the preset to use the MovieDB and that had the same effect.
the log.
I was using the TVDB.
I edited the preset to use the MovieDB and that had the same effect.
the log.
Error: Select all
java.net.SocketException: Connection reset by peerRe: Filebot Fails to rename series.
Getting the same issue for multiple different servers would definitely be a bit strange, unless it's something CloudFlare related that happens to be used by both TMDB and TVDB. In any case, Connection reset by peer means that the remote end of the network connection closed the connection unilaterally, so there's probably not much that FileBot can do on your end to make the other side of the network connection accept the connection and reply. That said, most likely a temporary network issue that will most likely go away by itself.
Re: Filebot Fails to rename series.
I can log into the databases with a browser so it is possible to reach them.
Re: Filebot Fails to rename series.
I guess you could try using your mobile as hotspot or a different WiFi from a different place? Just for testing.
It’s almost certainly an issue between you and the target server (API server; different from the website server) so at this point you could only try lots of different tests to narrow down on possible issues and maybe find something interesting. You could try curl -v or wireshark (if you are very technical) to see if that works, at least to get more granular connection details as to when exactly the remote host sends a reset packet. A conversation with a ChatGPT / Gemini / etc can be quite helpful for user-specific step-by-step troubleshooting as well if you have time to get into the nitty and gritty of network connection debugging.
It’s almost certainly an issue between you and the target server (API server; different from the website server) so at this point you could only try lots of different tests to narrow down on possible issues and maybe find something interesting. You could try curl -v or wireshark (if you are very technical) to see if that works, at least to get more granular connection details as to when exactly the remote host sends a reset packet. A conversation with a ChatGPT / Gemini / etc can be quite helpful for user-specific step-by-step troubleshooting as well if you have time to get into the nitty and gritty of network connection debugging.