Same here. My pages can’t be reached even after successful deploy. Sometimes it becomes online after a few hours.
And sometimes the production website preview domains work. But the actual pages.dev doesnt.
Same here. I set up my Pages application two days ago and it worked fine for a day and then it stopped working. A successful deployment would be followed by “The site cannot be reached”.
The original post was published months ago, seems no Cloudflare staff is aware of this. This community doesn’t look very useful.
Now occasionally I will get " Nothing is here yet" page
the deployment succeeded 27 minutes ago.
The preview doesn’t work either which finished 21 minutes ago.
What this? Vague descriptions of an error with no URL and no error message?
This community can be incredibly useful, it contains software developers, tech experts and uh… me I guess with decades of experience in diagnosing an remediating technical issues. But to do that one needs to provide actual data. This thread includes no actionable data for debugging. Could there be a Cloudflare issue? Sure. Is there?
I made my statement based on the fact that there have already been two people who have posted the same issue as mine in the span of 7 months but there is no useful reply in this thread. And this thread is the only thing related to this problem I can find in this entire forum.
I am new to both Cloudflare and this forum. Maybe it’s more useful than I have perceived so far. I will be open to wait and see.
How many people do you suppose have deployed Cloudflare pages sites in 7 months?
Is there an issue at the moment with Cloudflare Pages deployments? No idea. But 2 previous vague reports with no supporting data does not indicate a pattern.
Has your site ever worked? If so what has changed? if you roll back does it work?
Thanks for trying.
The fact that you see different result than I do, and even myself will see different results on different attempts already said there is an issue.
One more thing to share, yesterday I was able to visit the website after the deployment, but still something was weird(it used a wrong commit which I have amended, but I guess Cloudflare has some cache when pulling commit from git). Because of that I tried creating new Pages application, adding --ignoreCache parameter to the build command, etc. And now we are here.
Through the experiments, my code never changed, my build setting never changed except for the --ignoreCache parameter, so the folder is always the same. But the result is very inconsistent.
Thank you for asking this question, and with your pointer I do find something.
Below is the screenshot of my Assets uploaded tab, and weirdly there is no index.html.
However when I run my build command locally, the index.html can be successfully generated.
I will upload the screenshot in another reply as one reply can only have one media file.
Do you know what can be going wrong here?
The html file is also missing in sub-folders
For some reason, either Cloudflare didn’t generate the html files using the same command, or it didn’t upload them.
My site has worked before.
It is under development so yes something has changed.
I rolled it back in a different branch which triggered a preview build, and it still works.
Now the problem is already quite specific, why didn’t Cloudflare upload the html files? (Please refer to my replies)
If someone from the Pages team is here, maybe they can find out why in the backend logs.