Pages Down!
The page project randomly works/breaks.
This is a bootstrap purely frontend content:
36 Replies
Looks like some quic/http3 error?
That site looks fine for me and loads globally: https://www.uptrends.com/tools/uptime?toolRequestGuid=1149739b-78a6-4a22-825d-2a028786f6c9, including with http/3, so it looks like maybe your ISP or firewall is blocking quic
Website Uptime Test: Check Website Status | Uptrends
Is your website down right now, or is it just you? Check your website uptime and availability around the world.
Could try some other basic browser stuff (clear cache, etc), shift+refresh
@Chaika
1. We've different projects in cloudflare pages without the same issue.
2. The website sometime works somtimes not, so if it's really blocked it'll be 100% blocked right?
3. Is there anyway to change this quic/http3?
Browsers upgrade/pick quic/http3 differently. Unlike http2, browsers cannot upgrade/select http3 seamlessly. They should also fallback to http2 if http3 fails is my understanding
You can't change http3 settings on the pages.dev
You can google that specific error
err_quic_protocol_errorfor more info on it. If you're behind a company firewall of some sort or in a country known to block/filter content, I would wager it's related to that
If you add a custom domain, you could disable http3 on there, but that's kind of a hacky solution
Do you know if real users are getting that error? Do you get it on a VPN/outside of your local network?
@Chaika yes real users getting same issue
Also now the base url works but custom domain no
hmm, do you know any other factors? Are your real users who are getting the issue from a specific country/ISP, or using a specific browser? Just trying to narrow it down, I don't get the error at all, and for example you can see Discord loaded it fine as per the embed
Well, the question is why is it only from this project? We've +10 pages projectr
You don't have that custom domain proxied, it's dns-only, if there was some specific blocking taking place of pages.dev or anything like that, could still be applying
(I would make it proxied, probably like the other custom domains you have are?)
All of our domains are using CNAME www to proxy to cloudflare page project
we're using the same for all projects
Are they all proxied records?
I'm not sure what that means
In your Cloudflare DNS Records, next to each record, they are either DNS-only or proxied. Proxied means your zone/domain settings/etc apply
What we do is:
We go the DNS provider add CNAME record, as instructed in custom domain instructions. Cloudflare isn't the DNS manager for the domain
ahh I see, can't proxy it in that case
It's fine, the question is what the base url sometimes doesn't work?
It never happened to us before
I would loop around back to this:
Are your real users who are getting the issue from a specific country/ISP, or using a specific browser?
They're all same country, we're from Saudi Arabia
But we're not having the issue with other projects though
interesting, just to test I tried a Saudi VPN and specifically that pages.dev fails with an ssl error, and not any other. It makes me think that it was blocked, is it a brand new project or something that has been around for a bit? I have no idea about censorship/blocking in Saudi, is there some way you would check to see if it was indeed blocked at all?
Could try making a new pages.dev site as well. It doesn't seem likea pages issue, as it works in literally every other country as far as I see
Other things you could check:
What's the IP addresses when you lookup the pages.dev?
nslookup madidah.pages.dev on windows@Chaika No it's a new project, has been there since 15th oct
And we don't usually have blocking issue in Saudi
I just did a new project
Now even some other websites are down! which we didn't do any change in their settings since long time
@Chaika Seems like a blocking issue now?
Yea or just some internet issue
What do you see when you
nslookup qubab.sa, and when you run a tracert (or mtr if on linux) to it?I'm not experienced in networking. I'm not sure how to run nslookup 🙂
I'm assuming windows, you can just open up command prompt to do it. It'd be helpful to see if your ISP was poisoning the results or any other potential issues
@Chaika
Thanks for the screenshots.
Those 188.114.x IPs are of interest. Those IPs are commonly blocked: https://community.cloudflare.com/search?q=188.114, and only seen on free plan in specific geo areas as far as I have seen.
Unfortunately, that sems to be the case here. Normally you could proxy the pages.dev with your website on Cloudflare, and then upgrade that website (with no guarantee of it fixing it) to try to get different/non-blocked IPs, but you can't do that without your site being on cloudflare.
A traceroute (
tracert on windows) or mtr might still be helpful, but it seems just on your ISP's/Governments end. Especially since you can still connect to Discord (which is also behind Cloudflare, but not using those free IPs)Search results for '188.114,' - Cloudflare Community
A place for Cloudflare users to engage with each other and with Cloudflare staff
Whats your ISP?
@Erisa | Support Engineer STC, Saudi telecom company
@erisachu Any update?