WordPress problem fix
NitroPack and Cloudflare can fight over your images. We get both working together without rolling either back.
If your WordPress site started returning Cloudflare 522 timeout errors on images after installing NitroPack, the two layers are racing each other. NitroPack proxies images through its CDN, then Cloudflare in front times out waiting for the origin response on a cache miss. The fix is to align the two: configure NitroPack to bypass Cloudflare for its image domains, or move image optimization off NitroPack and into Cloudflare Polish, then warm the cache. Most sites are stable again the same day.
If any of these match, you are on the right page.
Random images return Cloudflare 522 errors
First load after deploy is broken, second load is fine
It started right after enabling NitroPack
Mobile users see broken images more than desktop
NitroPack adds its own CDN layer for images. With Cloudflare in front, the request goes Cloudflare to NitroPack to origin, and if origin or NitroPack stall on a cache miss, Cloudflare times out and shows 522.
You can but you lose DDoS protection and SSL termination. Better to align the two so they cooperate.
No, it is a layering issue. Two CDNs in series need explicit configuration to avoid timing races. Both vendors document it.
The real method, in the order it works.
Identify which domain serves your images (origin, nitrocdn, or Cloudflare).
In Cloudflare, set the image domain to Bypass on cache miss or increase origin timeout above 100 seconds.
In NitroPack, enable Cloudflare compatibility mode under Integrations.
Purge both caches, warm the homepage and 10 highest traffic URLs.
Monitor real user errors for 24 hours through Search Console or Sentry.
Real fix, from our work
A UK marketing network with 30 plus WordPress sites started showing Cloudflare 522 errors on images after a NitroPack rollout. The two CDNs were fighting on cache misses. I enabled NitroPack Cloudflare compatibility, set the nitrocdn subdomain to bypass on miss in Cloudflare, purged everything, then warmed the cache from a fresh IP. Errors stopped inside an hour. Average LCP also improved by 0.4 seconds because the layers stopped duplicating work.
Written by Ali Yasin Jatoi
Founder of WebCare Studios. Ali has worked with WordPress for more than 10 years, including managing a fleet of 150+ sites with WP-CLI automation for updates, security cleanup, and malware removal. He has hands on experience across major hosts including Cloudways, A2 Hosting, Hostinger, and Bluehost.
Site down, hacked, or broken checkout gets a senior engineer within 4 hours. No ticket queues, no bots.
Flat quote up front. If we cannot get you back online, you do not pay. Risk sits with us, not you.
We work on a snapshot first and never touch your live database until the fix is verified safe.
We run a fleet of WordPress sites every day. The errors you are seeing are ones we have closed hundreds of times.
Both, configured correctly, gives the best result. NitroPack handles image optimization and critical CSS, Cloudflare handles edge caching and security. The issue is misconfiguration, not the combination.
No. Once aligned, LCP and CLS usually improve because the layers stop duplicating work. We measure before and after on every project.
Yes. Any plugin that fronts images with its own CDN can race with Cloudflare. The fix pattern is the same: explicit compatibility mode and matching cache rules.
Two fields. Email and your URL. A senior WordPress engineer reads it within minutes and replies on email and WhatsApp with what is wrong and what we will do next.