image.tmdb.org ssl is expired.

The Movie Database Support

akabdullah
STAFFMOD
erabiltzaileak Maiatza 19, 2025 egunean 5:42 AM(e)tan bidalia

hi, https://image.tmdb.org/t/p/w600_and_h900_bestv2/bKzJz4ezNiGZdUoWhw4tikbAqeE.jpg

its ssl is expired

6 erantzun (1(e)tik 1. orrian)

BK Erabiltzailearen Erantzuna

STAFFMOD

Maiatza 19, 2025 egunean 3:12 PM(e)tan

I've also been noticing some intermittent issues with this today. Can't be positive, but it seems like the wildcard "*.cloudfront.net" certificate is sometimes being returned for image.tmdb.org requests. It's been intermittent and sometimes resolves itself, so has been hard to track down.

Error: "An SSL error has occurred and a secure connection to the server cannot be made."

URL: https://image.tmdb.org/t/p/original/cckcYc2v0yh1tc9QjRelptcOBko.jpg

Certificate information:

*.cloudfront.net i: Amazon RSA 2048 M01
Amazon RSA 2048 M01 i: Amazon Root CA 1
Amazon Root CA 1 i: Starfield Services Root Certificate Authority - G2
Starfield Services Root Certificate Authority - G2 i: Starfield Class 2 Certification Authority

rhyswilliamsza Erabiltzailearen Erantzuna

STAFFMOD

Maiatza 19, 2025 egunean 3:29 PM(e)tan

Seeing the same thing - seems CloudFront is sometimes unable to establish outbound connections to the backend (403), or a WAF/some other mechanism may be blocking requests from certain regions/ips etc.

403 ERROR The request could not be satisfied. Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. Generated by cloudfront (CloudFront)

I am able to establish connection from my home ISP, however connecting to Cloudflare Warp causes the issue to pop back up.

BK Erabiltzailearen Erantzuna

STAFFMOD

Maiatza 19, 2025 egunean 3:45 PM(e)tan

@rhyswilliamsza Ahh – yeah, seems like similar issue for me. My DNS resolver is Cloudflare (1.1.1.1) and it seems image.tmdb.org is sometimes hitting a CloudFront edge that has a bad/invalid cert (Peer certificate: CN=*.cloudfront.net). Occasionally, it hits an edge with a valid cert (Peer certificate: CN=image.tmdb.org).

I'm out of my element here, but maybe there's something the folks @ TMDb can do to purge the Cloudflare cache?

TurtleWilly Erabiltzailearen Erantzuna

STAFFMOD

Maiatza 19, 2025 egunean 9:22 PM(e)tan

Besides the obvious TLS/certificate issue I'm also getting a 403, if I get past that (e.g. using --insecure with cURL):

curl 'https://image.tmdb.org/t/p/w780/2EjOW4G2pg6wFU77PZQ99YhwG96.jpg' -H 'Accept: /' -H 'Accept-Language: en-US,en;q=0.5' --compressed -H 'Connection: keep-alive' -H 'Pragma: no-cache' -H 'Cache-Control: no-cache' --insecure

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Bad request.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: 6Y***redacted***A==
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>

EHayes Erabiltzailearen Erantzuna

STAFFMOD

Maiatza 20, 2025 egunean 12:17 AM(e)tan

This seems like it stops for a good amount of time 1 minute then goes crazy again - its been hit or miss for the past 4 hours.

Travis Bell Erabiltzailearen Erantzuna

STAFFMOD

Maiatza 20, 2025 egunean 11:51 AM(e)tan

Yup, a bad SSL config went out. I just corrected it, and you should not see the error anymore.

Eztabaida Honetako Erabiltzaileak

Categories

The Movie Database Support