The cached image is not displaying, but it DOES exist on the server
What steps have you taken to resolve the issue?
Add a string at the end of the URL
It seems this Cloudflare issue is resolved if I purge the cache, but I hope it doesn’t become a recurring problem… I’m going to purge the cache now. I’m attaching images of the issue because once it’s purged, I believe the problem will be fixed (hopefully).
We have the same issue here. Image files for which we receive 404 not found are actually present on our server. When we bypass Cloudflare cache everything works fine. Clearing the entire cache CF didn’t help.
It seems to be working fine now. I’m not certain if the fix was applied on their end, but it started working after I revisited the SSL/TLS settings and set the SSL/TLS mode to ‘Flexible.’
I made this change because I noticed Cloudflare would occasionally attempt to contact my server over HTTPS instead of HTTP. Again, I’m not entirely sure if this was the primary cause of the alleged cache malfunction.
Therefrom, might be issue if you’ve tried to purge it.
Could be 404 was fixed at your Web server, however it’s a resource extension which by default cached at Cloudflare as follows:
Therefrom, needs to be Purged individually, or rather Purge Everything.
Currently not cached anymore:
cf-cache-status: DYNAMIC
Hopefully no origin cache such as Nginx would kept it as “unchanged” despite it’s overwritten, and might need restart web server to get new version of it.
Have you tried using a different Web browser or Incognito Mode (Private Window)?
Shouldn’t be used if you have SSL certificate at your origin.
It causes issue with redirection HTTP to HTTPS and Mixed Content error as well.
"Yesterday, after more than 10 purges of ALL the cache, with the cache getting worse each time, and after dozens of tests, I disabled my cache rules and set the site to developer mode.
This morning, EVERYTHING got MUCH worse!!! The homepage of my site only displayed the message “ok”, just that, A DISASTER!!!
Full of 404 errors everywhere… and I said GOODBYE TO CLOUDFLARE… just when I was about to revert my DNS to the originals, I tried switching the SSL/TSL settings from “Flexible” to “Full”, following a suggestion from the team that manages my server.
I should mention that it had always been working on Flexible, and no one changed that setting. But after switching it, everything started working again.
Still, the truth is that this madness that suddenly appeared with Cloudflare cost us a lot of time. The help documentation didn’t help, the purges didn’t actually purge, and it was just a bad experience overall…
For now, we’re back online. I’ll see when I can reactivate the cache. Honestly, things were going well, but this left a bad taste in my mouth."
Fritex, I really appreciate your help and the information you provided regarding the issue that came up. Without reading the post, I had already solved everything today at 11am, but your assistance was on the right track.
I hope this message helps someone who encounters a similar issue.
Hopefully, Cloudflare won’t pull these stunts again…
