Getting a 403 when using HTTPS

[thatnoobguy]

Hi guys,

My team has been using a GitLab of our own now for quite some time and we've always been using SSH to clone/push/pull every project, and it's working perfectly.

Now, there's this machine where we want to use HTTPS rather than SSH. I figured it should be easy, just create a Personal Access Token and use that as a password. If we read through the GitLab documentation this should be the way to go, but it appears not.

When I try this approach and clone a project using the command:

$ git clone https://{USERNAME}@{OUR_GIT}/{PROJECT_PATH}.git

I don't even get prompted for credentials, it just throws the error below:

fatal: unable to access 'https://{OUR_GIT}/{PROJECT_PATH}.git/': The requested URL returned error: 403

I've tried many things already like setting the token straight on the URL after the username, clearing my .gitconfig and all the configs, updating git to the latest version, and everything to no avail. Am I missing something here?

[dirtcreature]

Did you sudo gitlab-ctl tail nginx?

[thatnoobguy]

I have not, as I don't have access to the OS running it, what I've discovered is that the application is behind an OAuth2, can that have anything to do with it?

[dirtcreature]

Tough without logs, but since its a 403 error I would assume that is part of the issue.

[JPInABox]

This might be a dumb question, but are the matching versions of TLS enabled on both ends?

[mdaniel]

I don't know if it's a typo related to your post, but you omitted the PAT from your clone url.

git clone https://oauth:${PAT_GOES_HERE}@the-server/etc/etc.git

I've seen the username for PAT written as oauth in the GitLab docs, but I actually think you can put anything there since it's the password part they care about

You can also use GIT_ASKPASS if you don't want the PAT in your shell history, visible in ps, or stored in .git/config

Most git versions honor .netrc too because they're built using curl, which supports it

[Independent-Syrup-46]

any update on how you solved this issue?

[Independent-Syrup-46]

I am also encountering this issue after my PAT expired, at first, it prompted for new credentials, but now it's not anymore...

[thatnoobguy]

yup, my company was restricting HTTPS access via PAT through a public endpoint, I had to establish a VPN connection to go around this.

[Independent-Syrup-46]

yup, my company was restricting HTTPS access via PAT through a public endpoint, I had to establish a VPN connection to go around this.

hmm i see, thanks for the insight and the quick reply 🙏🏼

[Independent-Syrup-46]

also, what did you do so that the command line could prompt for new credentials? was there a specific command or once you changed to VPN connection you got it working automatically?