Server error email on static Workers Pages deployment
Hi! I got this email just now, but what's the deployed on the domain is just static HTML, and the last deployment was in 2021. Has anyone else gotten this email for a Workers Pages deployment? Is there anywhere I can view the error rate that generated this email? How can the measured origin error rate be high if there is no origin anywhere in the zone?
12 Replies
I hope this is just a spurious email or something, but after looking into it, I was like wait, I have no monitoring on this static site, it could be that there's downtime and nobody is notified
iirc those emails refer to the domain overall, so if you have any subdomains that are erroring, could be from it. CF is also going to treat Pages as an origin though.
If you have Pro or higher you can use Web traffic analytics to filter for errors, otherwise you have the hidden support error page: https://dash.cloudflare.com/?to=/:account/support/error-analytics
That's the interesting part, there is nothing else in the zone. Here's the full DNS config
does your www work if you visit it directly?
It currently works, yes
The email says 4/28, though, and I've never gotten this email before, so any downtime may have passed already
no I mean the www, not just the apex. That setup doesn't look like it would work, unless you changed the www cname after. Each hostname has to be specifically added under Pages Custom Domains, including the www and apex, and it would autocreate a cname to pages.dev for you
Huh
This was all set up in 2021 and untouched until now, but huh, you're right, the www actually doesn't work
lol probably no one tried it until some bot or crawler did
Okay I guess someone linked to the www or something, and that generated a bunch of clicks with an error code, yea
Thanks so much for the help!
you could add it as a Custom Domain under your Pages Project settings, or create a redirect for it (better for seo if you do a redirect afaik, but up to you)
Yea, I just added a page rule to redirect it (and changed the www to an A record to 192.0.2.1 to not confuse the next person who looks at this in 2027 :P). Thanks!
Not OP, but was looking for this kind of answer, thank you