Hard reload causes "Pages had an internal error, if this persists please contact support!"
Hard reload on our pages app leads the error above. How do we debug?
CIs this on your site? Or when building?
.On the site
.Build is fine
CCan you share the domain?
.app.skiff.com
U..SJCUAnd can you screenshot the error page you get? (It works fine for me I assume it could be a specific colo issue)
.There you go
Ucc: @Walshy | Pages know what might cause this?
.On Chrome (previous one from Brave) just in case.
UJust curious if you go to the pages.dev domain of your site does it have the same issue?
.Checking
.Yeah the pages.dev link load fine
NHey folks! PM of Pages here we chatted on the phone just a couple weeks back on a similar issue. Like last time, it looks like the issue isn’t affecting all your traffic just those with hard reloads which I believe are mostly coming from your team.
Curious as to why you are doing a hard reload on every request?
Curious as to why you are doing a hard reload on every request?
NDefinitely aware of the hard reload issue and are brainstorming a fix but curious to get more info 
.Typically we do it make sure latest changes are surfaced on the frontend
.Especially after a deployment
.We may also suggest it to users if we believe that the issue they are experiencing could be a state issue on the FE
TI just got this issue too on beta.tomatenkuchen.eu (only on one path or deeper tho, top level is fine), colo is
And well, hard reloading prevents all caching issues
While Pages may clear the cache for some assets + I've disabled caching in browser devtools, there are still issues sometimes with outdated assets
FRA (as always for me)And well, hard reloading prevents all caching issues
While Pages may clear the cache for some assets + I've disabled caching in browser devtools, there are still issues sometimes with outdated assets
J
ɆYep, we're seeing the same issue. In our case, we do
location.reload() if we can't connect to a local server so that we can retry the connection and clear the javascript environment (this page just serves as a loader to bridge some gaps between our program and OBS, which doesn't really like pages on localhost).
BSame issue here, multiple times today. Never saw it before today.
0+1, already had the issue a few days ago, but it recovered back then
WHey everyone, thank you for the reports, we have now resolved the issue - https://www.cloudflarestatus.com/incidents/lzcsjxf31wdw
0out of curiosity, could you provide any detail about the cause?
(Headers for hard-refresh/normal requests looked somewhat identical, couldn't reproduce the issue with curl)
(Headers for hard-refresh/normal requests looked somewhat identical, couldn't reproduce the issue with curl)
JIf you're ENT, you can probably request an Incident Report 
