Hello,
It seems that since a couple of weeks I can’t access gitlab.com webpage, no issue with gitlab repo or about.gitlab.com.
Is there any way to check whether there is a filter/block on some ip from Cloudflare ?
Regards,
Gitlab doesn’t use Cloudflare. Are you seeing something that’s saying Cloudflare is the issue?
1 Like
No offense but @sdayman, you are wrong
Hey,
They used cloudflare and after several check with them we end up on that potential issue, hence my question.
However, they will raised it on there side I guess it will have more impact 
Yes, you can, it should be in your firewall logs! For help on accessing the logs, see any one of the articles below
Because most anybody is allowed to use Cloudflare DNS, even if they don’t proxy their site(s) through Cloudflare.
Oh, so they have a Cloudflare DNS set, it’s just they’ve turned off the proxy (set it to “DNS ONLY”)!
about.gitlab.com is probably not proxied ( and I have no issue to acces this subdomain) my issue is with gitlab.com “main” website ( https://www.gitlab.com)
It seems to redirect to about.gitlab.com (where I see this)
You might want to check your DNS records within your Cloudflare dashboard and see if about.gitlabs.com is set to “Proxied”! If it, change the record to “DNS only” (
cloud)!
Nope, I misread it. I’m mobile right now and can’t dig into proxy status right now.
What error is showing?
I misread. Anyhow, the naked domain only redirects.
1 Like
But if they’re blocked at the naked domain (which is proxied by Cloudflare), they won’t get that redirect to the ‘about’ subdomain.
They’re probably seeing a 1020 screen:
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.