Question
How long does it take for the CDN endpoints to come alive?
- Posted on December 23, 2023
- CDNDigitalOcean Spaces
Asked by JetForMe
I just created a new Space, and enabled the CDN in the process. Origin links work, but CDN links fail the SSL handshake. How long does it take for the CDN to be provisioned? My other spaces’ CDNs seem to work fine.
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!
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.
Featured on Community
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hi there,
Usually, this should take only a few minutes. In your case, the SSL error indicates an issue with the SSL certificate that you’ve provided for your Spaces CDN custom domain:
Can you confirm if you’ve used the automated Let’s Encrypt Spaces SSL or if you uploaded your own custom SSL certificate?
If you’ve uploaded a custom SSL you need to make sure that the SSL is valid and that you’ve also added the CA bundle.
UPDATE: In this case the issue here was the dot in the Spaces name.
The wildcard SSL certificate would cover all domains for
*.sfo2.cdn.digitaloceanspaces.combut in your case, you have an extra layer of a subdomain after the.org. This is what breaks the SSL encryption.What you could do is create a new Spaces bucket called
jetforme.sfo2.cdn.digitaloceanspaces.cominstead ofjetforme.org.sfo2.cdn.digitaloceanspaces.com.Best,
Bobby
Heya @jetforme,
That should be almost instant, in a few minutes top. However, the SSL error you’re encountering suggests a problem with the SSL certificate for your Spaces CDN custom domain. For more details, you can refer to DigitalOcean’s guide on customizing CDN endpoints:
https://docs.digitalocean.com/products/spaces/how-to/customize-cdn-endpoint/
Could you please verify whether you have employed the automated Let’s Encrypt SSL for Spaces, or if you have implemented your own custom SSL certificate?
In the case of a custom SSL certificate, it’s important to ensure its validity and that the CA bundle has been correctly included