Error 522 with new Cloudflare pages deployment
I've found the following thread through a quick google search:
https://community.cloudflare.com/t/error-522-with-new-cloudflare-pages-deployment/361938
Walshy was part of the thread back then. The issue seems to have come back.
Seems to affect only new sites this time.
Cloudflare Community
Error 522 with new Cloudflare pages deployment
hello I have a problem with Cloudlfare pages. Everything was fine when one of my deployment give me a 522 error. Since, every new deployement get a 522 but the old one seems to be fine. I tried to delete some old one but i still get the issue.
18 Replies
Is this for a custom domain?
nope
you can try it out with https://brand-crowdy-ca.pages.dev
I was able to add a custom domain to an existing site & update it without problems. Only having the issue on the newly created one
How long ago did you create this project?
says 18 min ago
What does your deployment list look like? Do you have any production deployments?
Connected to Github
there are 2 because I retried just in case
from the first build, 2nd build skipped as same code version
Thanks! It should have been a more friendly error even if you didn't have any, I realize now. Only back in the old days would it straight up 522 for that, doesn't look like anything on your end
Even the specific build links give a 522 err
1d36b219.brand-crowdy-ca.pages.dev
FYI the Team is aware of this and investigating. Thanks for the report
Think I'm having the same issue, using Vite/React. Build succeeds but link gives 522. https://835115a5.davidsite-react.pages.dev/
If it's a brand new deployment most likely, watch the incident linked above
Thanks @Cyb3r-Jok3 & @Chaika ☺️
fixed, fyi. ty!
My site seems up too. Hope the overall issue is fixed when creating new pages sites.
yea it was just that every Pages site publishes a Worker, and Workers were delayed in being delpoyed/updated as per the incidient. Any new one should be deployed super quickly
Awesome, great news, thank you!