Spaces CDN endpoint started failing with NET::ERR_CERT_COMMON_NAME_INVALID

About an hour ago our Digital Ocean Space’s CDN endpoint started failing when trying to access directly in the browser with:


There’s currently maintenance for Spaces in SFO2 but our Space is in NYC3.

Any idea why this suddenly started happening?


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Pinned Answer

Hi there @bitnado & @flowster,

This is an issue we are currently addressing with a high priority escalation. You can view progress on our status page:

Hope that helps! - Matt.

This is absolutely terrible. Our live app with thousands of users is pretty much broken right now.

Why is this taking DAYS to resolve and not minutes???