Hi @dsl225, please use a leading http or https as applicable to the Bunny CDN address. Do not include a trailing /.
I hope this information helps, but please ask if you have any other questions!
Thread Starter
John
(@dsl225)
Thanks for this but I already tried several variations, including this one, but none of them worked – while all other caching plugins that I tested are working simply by adding “mysite.b-cdn.net”. So I already switched for another one but would really curious to know how to get this up and running for next time.
Hi @dsl225,
Thanks for testing that out.
Can you please tell us a bit more about what is “not working”? It would help us to have more details so we can figure out if the problem is on our side or something specific to Bunny CDN?
Thread Starter
John
(@dsl225)
Yep, you are right, my answer was not clear.
I have an account at Bunny CDN with several sites and most of them are using WP Fastest Cache where I simply add “mysite.b-cdn.net” and then it works – meaning that when I check the URL of any random image of the site I get this same https:/mysite.b-cdn.net/…/image.jpg
For 2 different sites I wanted to switch from WPFC to Super Cache for different reasons not relating to the CDN and then tried to connect to my CDN accounts by testing differing leading strings and no ending slash. None of them worked – meaning that I never succeeded in getting Bunny’s URL for loading images and was still getting the usual https://mysite.com/… This is what I call “not working”.
I then switched to W3 Total Cache for those sites and they connect to Bunny CDN by using my account’s key and found this much more straight forward than messing with leading or ending characters whatsoever. But again, the problem here was that I really didn’t find any sort of way to connect and load images from my CDN account at Bunny.
Thanks for your interest.
Hi @dsl225, I checked with our developers, and they recommend using the BunnyCDN plugin instead of the WP Super Cache Plugin’s CDN options.
I hope this solved your issue, but please let us know if you have any other questions!
Thread Starter
John
(@dsl225)
Yeah, I know this as their plugin was working fine until a couple of months ago and then they update it with a minimum requirement of PHP 8.0 and this is not the case with those 2 sites. So I don’t think this is a real solution, sorry.
If your plugin doesn’t work with Bunny CDN you should simply notify your users about that. And, some of them, will simply switch to another caching plugin, as I did, instead of installing yet another plugin that, moreover, is limiting its usage to PHP 8.0.
(Please don’t tell me that PHP 8 is better and more secure than 7.4 as this is not really the point here.)
@dsl225 thanks. We had no idea BunnyCDN didn’t work. Could you please contact the BunnyCDN plugin developers and ask them to provide polyfills for the PHP 8 functions they use, as there are many users like yourself, who haven’t upgraded yet?
Thread Starter
John
(@dsl225)
Sorry, no. I’m not a dev and I’m not using their plugin nor do I use yours at the time.
I really cannot see any reason why you cannot discuss this together with them…
I think I’ve done my part already. Thanks.
Hi John,
It’s not within our scope of support to ensure compatibility with third-party plugins, so I’m going to go ahead and close this thread now. If you’d like to continue troubleshooting after you’ve reached out to Bunny CDN (assuming you do decide to use their plugin and ours concurrently), you can follow up here and mark the thread as not resolved in the Status section of the sidebar above.
Thanks!
