Connection reset by peer when cloning via git://

Summary

When cloning a repository via git clone git://gitlab.com/user/repo.git, the error message fatal: read error: Connection reset by peer is displayed and the repository can't be cloned.

Steps to reproduce

• Have a public repository hosted on https://gitlab.com
• Attempt to clone the repository via git clone git://gitlab.com/user/repo.git
• Get the error message

Example Project

I'm building my own fork of LineageOS here on GitLab, instead of on GitHub. https://gitlab.com/Kaukov/android

I require this when using the repo utility. Using https://gitlab.com instead of git://gitlab.com produces constant prompts for username for GitLab when syncing the projects.

What is the current bug behavior?

And error message fatal: read error: Connection reset by peer appears and the repo isn't cloned.

What is the expected correct behavior?

The repo should be cloned as if it's being cloned via https://gitlab.com or git@gitlab.com.

Relevant logs and/or screenshots

git clone git://gitlab.com/Kaukov/android.git -b lineage-18.1
Cloning into 'android'...
fatal: read error: Connection reset by peer

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info --- NOT RELEVANT

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 --- NOT RELEVANT

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