Tor users facing long checks at https://gitlab.com/users/sign_in and https://gitlab.com/users/sign_out

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

The Checking your browser before accessing gitlab.com. page checks forever for Tor users at https://gitlab.com/users/sign_in and https://gitlab.com/users/sign_out.

At F-droid, many of our team members and users use Tor or Tor browser, it makes it difficult for them to access our repo on GitLab.com. We understand your need for mitigating the abuses. But at least their life will be easier if you at least enable the Cloudflare Onion Service, or at least make it not an infinite loop.

Also users who enable the fingerprinting protection measures: gitlab-com/www-gitlab-com#12422

This blocks our internal discussion on adopting the GitLab Open Source Program.

Steps to reproduce

1. Open the Tor browser, or a random browser with system level Tor connection (or over a Tor proxy)
2. Go to https://gitlab.com/users/sign_in or https://gitlab.com/users/sign_out
3. It shows Checking your browser before accessing gitlab.com., and redirects to another Checking your browser before accessing gitlab.com., forever.

What is the current bug behavior?

It shows Checking your browser before accessing gitlab.com., and redirects to another Checking your browser before accessing gitlab.com., forever.

What is the expected correct behavior?

The delay is removed for simply Tor (browser) users, or the check becomes only 5 sec rather than an infinite loop.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

/cc @greg @nuritzi