16

I went to about.gitlab.com. from there I clicked on sign in. The browser keeps showing: "Checking your browser before accessing gitlab.com.". This has been going on for 10 hours. I have Already tried clearing my cookies and restarting my pc. This did not yield any result. My firewall is turned off so it isn't a firewall issue.

1
  • One possible cause: images are blocked in the browser (seems their verification process loads some data with an image content-type)
    – Janaka Bandara
    Commented Jul 28, 2023 at 13:15

5 Answers 5

Reset to default
17

This is so extremely frustrating and makes me want to move everything back from GitLab to GitHub.

In my case, the addon that GitLab (actually cloudflare) didn't like was the Chameleon (Random Agent Spoofer) plugin, which I use to prevent tracking/fingerprinting across websites.

Thanks Cloudflare for depending on fingerprinting and effectively issuing a DOS attack on GitLab customers that use tools to protect themselves.

4

That seems related to a DDOS protection by Cloudflare (since GitLab has changed ts CDN provider to Cloudflare last March 2020

GitLab.com users with a whitelist of sites in their firewall setup will need to change what is whitelisted for GitLab.com.
For the initial change, we will be switching DNS to Cloudflare. This will cause all GitLab.com traffic to be proxied through Cloudflare.
This change will be visible by changes in DNS records queried for GitLab.com. A whitelist of IPs can be found here.

The OP freeroamer90 reports in the comments:

  • it is working in incognito mode
  • the issue seems related to the Quick Heal Anti Tracker extension (Firefox or Chrome) which was blocking the site.
6
  • my firewall is turned off. So I shouldn't have to whitelist the IPs. Also, I can access the website on my phone(not on my laptop), so I think the server is not Under DDOS attack. So how can I resolve this? plz help.
    – freeroamer90
    Commented Dec 1, 2020 at 10:46
  • @freeroamer90 Can you check if the error persists with a different browser? (Chrome/FF/IE)
    – VonC
    Commented Dec 1, 2020 at 10:55
  • Yes, it persists in both Edge and Chrome. I also tried it with different networks(My Home broadband and Mobile Hotspot). But on a recommendation, I tried in an Incognito Windows, and it worked. So I have Isolated it to an extension which was on both browsers and seemed to block the site. I have removed it and its now working as expected. Thanks for your time and help @VonC
    – freeroamer90
    Commented Dec 1, 2020 at 12:00
  • @freeroamer90 Great! What was the problematic extension?
    – VonC
    Commented Dec 1, 2020 at 12:34
  • Quickheal Anti Tracker. It came packaged with the antivirus and never even knew it was there :)
    – freeroamer90
    Commented Dec 1, 2020 at 14:42
4

This also happens when privacy.resistFingerprinting is enabled in Firefox. This is the relevant GitLab issue (#14234).

There are also discussions on this on GitLab’s forums:

and on the Cloudfare forums:

This is just terrible! As others have mentioned, sites like GitHub have no problem with this. Not a good impression at all from GitLab.

0

I didn't have any plugins or blockers and this is what worked for me on Windows 11.

  1. Turn off Windows Firewall for both public and private networks
  2. Open gitlab in Chrome Incognito.
0

simply i have changed my date and time in local system will change automatic date and time fix issuse

1
  • Is this answer intended to solve a problem with browsing the GitLab website? If so, could you clarify what effect client time has?
    – SmellyCat
    Commented Apr 30 at 8:17

Not the answer you're looking for? Browse other questions tagged or ask your own question.