Yesterday there was a notice on the tvdb.com forum
API Update: Removing legacy SSL support
Would this impact filebot as I am no longer able to update my tv show files?
Thanks
J
TVDB.COM API
-
RonaiSanzer
- Posts: 2
- Joined: 10 Jan 2020, 14:21
Re: TVDB.COM API
Yes, as I get the timed out socket error as of 1/10/20 8am. You can still try other options like TMVDB Episode but I had no real luck with it naming things in a good manner.
Re: TVDB.COM API
Read timed out is a different class of problem. It means the server doesn't respond, and it's definitely a temporary server-side issue.
The SSL compatibility notice discussed by the OP is unrelated. Currently, the server doesn't respond at all. For a SSL handshake to succeed or fail, there would be some initial back and forth communication, before each side agrees to not be able to agree on a TLS version, and fail.
AFAIK, FileBot does support all the latest TLS versions. So unless you using some ancient FileBot 3.* release from 2010 you're probably going to be fine.
The SSL compatibility notice discussed by the OP is unrelated. Currently, the server doesn't respond at all. For a SSL handshake to succeed or fail, there would be some initial back and forth communication, before each side agrees to not be able to agree on a TLS version, and fail.
AFAIK, FileBot does support all the latest TLS versions. So unless you using some ancient FileBot 3.* release from 2010 you're probably going to be fine.
Please read the Re: TVDB.COM API
Well, it's technology, not magic. It can be understood, step by step, all the way. Read timed out means that TCP packets are sent, and now we expect and wait for TCP packets in response, except none ever came, so and the TCP network layer errors out. That's all we know. Everything else in conjecture.