Getting Internal server error of CF pages
is there any maintenence window going? all my cf pages are 500.
18 Replies
Same here, all Cloudflare Pages applications are failing with 500 errors across accounts.
Same here, we just got 500 on all our pages this morning
this is what we got on the logs
That's the same error we're seeing.
Request with a GET or HEAD method cannot have a body.
Our last deployment was 38 days ago, the first log of this error was at Oct 23, 8:52 AM AEST this morning.something is going on, massive outage
anyone contacted support yet?
Not yet, opening a community topic now.
Just created the following community topic.
https://community.cloudflare.com/t/all-clouflare-pages-projects-failing-with-500-errors/849762
https://www.cloudflarestatus.com/incidents/srj1939ly923 was created a bit ago.
I'm guessing all your Pages Projects use a specific framework/setup that somehow triggered this
Thanks for the update, @Chaika , we did see an incident was created.
Our projects use Remix or React Router v7.
my speculation was that Cf changed something to disallow those methods with bodies that wasn't properly gated but looks like it's always been blocked in normal fetches, maybe something else like Smart Placement causing issues. Eh, probably useless speculation, will just have to wait for CF team to fix
Eitherway, the guarantees of Workers and Pages is that as long as you never move the compatibility date, your stuff should never break, so on the team to fix.
Happening on next-on-pages as well
Placement: Default
Compatibility date: Aug 1st, 2025
Compatibility flags: nodejs_compact
No deployments for 20days
Agreed, that was my understanding too, thanks @Chaika .
We are also getting these "TypeError: Request with a GET or HEAD method cannot have a body." status 500 errors in our rr7 project.
happens over periods of a few minutes and then the error is sometimes gone again for a few minutes
I'm experiencing the same issue for all my workers
seems like they identified the source of the issue and are working on a fix 🤞
according to the status page, a fix has been implemented... but we are still seeing the error
yes, we are still seeing the error too
It seems to be getting better now. @xatxat what about yours
yes, the last 30 minutes i didn't see the error anymore. but there were always some phases where it was fine in the last 3 hours
but let's hope it stays like this 🙂
Just out of curiosity, does this issue only occur to react user?
its solved.. all over i guess...
and mine was a next js app.