What happens when CDN settings have gone wrong on your site?
Last night, I messed up the settings for BunnyCDN. Which means that all of the feature images (the one you see on the blog page) and some inline images were not visible. My apologies for that. It was a case of over zealous CDN settings. Or not realizing I was making a mistake. The end result was something like below.
New! You can listen to the audio version of the blog post by clicking below
Images gone AWOL! See below screenshots
While setting up BunnyCDN for my blog, there was no display of images on this website. This is a classic case of content delivery network settings gone wrong.
I decided to start migrating the CDN or content delivery network for images. So far the inline images (the ones you see embedded in the blog post) were served from fast.io. As I posted elsewhere, the service is closing and it was time to move the CDN.
Once the server synced with the images, the disappearing act began. Somewhere in the settings I had opted for a URL rewrite, that is, instead of the feature images being hosted from this server, they were getting served from a folder on BunnyCDN that did not exist. The result? Sorry, no images for you.
Digging into the logs showed what was going on.
Temporary fix- disabling the WordPress plugin for BunnyCDN.
I obviously did something wrong. While I get the issue resolved, apologies or this (yet) another issue with images.
Resolving issues with Content Delivery Network and images
2021 February 2022, all images on this site will be served from either of:
Gumlet or BunnyCDN. These two options have worked best for me, both plans are paid off for atleast 3 years, and the experimentation has probably taken more time than reasonable.
I will retain the images from previous posts on their current servers, but will update the URLs so that we do not have recurring issues with images.
What about the images in this post? Well, they were uploaded to storage folder in BunnyCDN, and served from there! Compressed using imgbot of course. Update November 2021: Unfortunately, the imgbot .ai service is no longer operational.
This post was updated on 2022-02-23