By bitnado
About an hour ago our Digital Ocean Space’s CDN endpoint started failing when trying to access directly in the browser with:
NET::ERR_CERT_COMMON_NAME_INVALID
There’s currently maintenance for Spaces in SFO2 but our Space is in NYC3.
Any idea why this suddenly started happening?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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: https://status.digitalocean.com/incidents/223f113g7r2z
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???
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.