-
Hi again,
I have a request. I use DigitalOcean’s CDN for my bucket; I’d like to be able to serve my video content through this CDN instead of through the actual digitalocean endpoint. Can you add the ability to use a CDN alias in the DigitalOcean hosting settings area?
-
-
Hello John,
Are you having issues with CDN alias integration? Do you experience any errors when you put it into the endpoint field?
Thanks,
Juraj
Yes, I try to put in the cdn alias address on the DigitalOcean endpoint (I tried both putting the full cdn address in the endpoint, and putting the subdomain as the bucket, and the root domain as the endpoint).
Am i doing it wrong?
Hello John,
I’ll discuss it with our development team. Perhaps support for DigitalOcean CDN hasn’t been integrated yet. I’ll get in touch with you in the close future with more info.
Thanks,
Juraj
Hello John,
we could add it, however we found that the DigitalOcean Spaces CDN doesn’t support signed URLs. So we are only using DigitalOcean Spaces as a storage for the video files with BunnyCDN pulling files from it with signed URLs. So we ended up not using DigitalOcean Spaces CDN.
Thanks,
Martin
Got it, I actually ended up moving away from DO CDN due to reliability issues, am now using BunnyCDN. Thank you
Hello John,
so are you using DigitalOcean Spaces as a storage and BunnyCDN for the CDN? We use that same setup and so far there were no issues.
There was a couple of days when European BunnyCDN edge servers were slow to pull files from Northern America though. Their Origin Shield should help in that case.
Thanks,
Martin
Yes, that’s my current setup. I did take a while to load all of our content from DO Spaces, but seems to be doing quite well now
