Question

Can't get Let's Encrypt SSL to work on a NS subdomain

Posted on November 17, 2023
DigitalOcean Spaces
Asked by Miro Hristov

I’ve added NS record for a subdomain files.elevation-us.com

Also added the domain in DO domains with CNAME ‘ftp’ to nyc3.digitaloceanspaces.com digitalocean subdomain ssl That way I end up with ftp.files.elevation-us.com.

Finally, CDN was enabled with a wildcard SSL for *.files.elevation-us.com digitalocean subdomain ssl For some reason I can only select the wildcard and that’s why i need the additinal ftp part.

I’ve tried creating both the spaces/buckets to no avail. digitalocean subdomain ssl

The following works but the SSL is not working: https://ftp.files.elevation-us.com/test.png

The current SSL used is for *.nyc3.digitaloceanspaces.com

I’m stuck here. How do I get custom CDN subdomain to work with existing domain without transferring the entire NS to DO? If I don’t use NS and only CNAME I can’t issue certificate. If I do, the SSL doesn’t work even when it’s wildcard. (Ideally, i want only files.elevation-us.com but ftp.files… would work if it’s needed) The only thing that worked in the past is to route trough CloudFlare and use flexible SSL.

Submit an answer

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.

Bobby Iliev

Site Moderator