For the past few weeks (months? Time is hard) I've been getting nothing but red discs while attempting to load album information. The error's the same each time, CAA JSON error: SSL handshake failed.

Debug log (relevant segment):

D: 10:49:53,081 coverart_init_.next_in_queue:149: Trying cover art provider UrlRelationships ...

D: 10:49:53,081 coverart_init_.next_in_queue:149: Trying cover art provider CaaReleaseGroup ...

D: 10:49:53,082 webservice\ratecontrol._out_of_backoff:222: ('coverartarchive.org', 443): oobackoff; delay: 62ms -> 31ms; slow start; window size 5.000 -> 6.000

D: 10:49:53,082 webservice\ratecontrol.get_delay_to_next_request:118: ('coverartarchive.org', 443): Last request was 267 ms ago, starting another one

D: 10:49:53,082 webservice\ratecontrol.increment_requests:138: ('coverartarchive.org', 443): Incrementing requests to: 1

D: 10:49:53,358 webservice\ratecontrol.decrement_requests:146: ('coverartarchive.org', 443): Decrementing requests to: 0

E: 10:49:53,359 webservice_init_._handle_reply:459: Network request error for https://coverartarchive.org:443/release-group/1ddd8aa3-ca35-3417-9ca3-d2064e7dd5f6/: SSL handshake failed (QT code 6, HTTP code 0)

E: 10:49:53,359 ui\item.error_append:106: <Album 2a595ac3-bb36-484c-91c9-13232f8df0e5 ''>: CAA JSON error: SSL handshake failed

This happened on 2.6.3, then after upgrade to 2.64, and now when I tried on 2.7.0b1.

If I had to guess it might have to do with a CA root detrust, but I'm not sure what Picard's network stack is so I'm not sure if there's a cache I can invalidate or something else I can do to resolve this locally. For what it's worth I've checked all the dupes of this issue (from as far back as 2017) and nothing suggested in the threads and tickets seems like something worth trying excepting perhaps updating openssl dlls out from under the app but that sounds like a good way to break things.