GitLab remote: HTTP Basic: Access denied and fatal Authentication

Question

Unlike this post, I am on macOS.

I have the password configured in GitLab. I also have an SSL key created after the project was made on GitLab.

When I use an existing folder for a new project and follow the steps below, I am prompted to enter my GitLab username and password.

Existing folder

cd existing_folder
git init
git remote add origin https://gitlab.com/sobopla/Geronimod.git
git add .
git commit -m "Initial commit"
git push -u origin master

After the password is entered I get the following error.

remote: HTTP Basic: Access denied fatal: Authentication failed for 'https://gitlab.com/myname/myproject'

Following answers didn't work for me..If still anyone facing this issue in mac...this link might help... https://stackoverflow.com/questions/17659206/git-push-results-in-authentication-failed — Pallamolla Sai, Apr 13 '20 at 12:42
This error can also occur if your GitLab account has as password expiration date set but you are using another authentication method, e.g. LDAP. Then GitLab throws the 403 without even checking your credentials against the LDAP server. — Andy, Jun 10 '21 at 12:56
Penaltily related question: [macos - How do I update the password for Git? - Stack Overflow](https://stackoverflow.com/questions/20195304/how-do-i-update-the-password-for-git) — user202729, Jun 01 '22 at 03:03
One workaround is to authenticate using SSH rather than HTTP. In the steps above, that would mean replacing the third line with `git remote add origin git@gitlab.com:sobopla/Geronimod.git`. This should if you have your SSH keys set up properly. — dinosaur, Aug 31 '22 at 19:25
I'm surprised no one has suggested the first thing that you should do. **Double-check your username and password!** — Janez Kuhar, Sep 06 '22 at 10:10

score 961 · Answer 1 · edited Oct 14 '21 at 11:34

961

It happens every time I'm forced to change the Windows password and none of the above answers helped me.

Try the below solution which works for me:

Go to Windows Credential Manager. This is done in an EN-US Windows by pressing the Windows Key and typing 'credential'. In other localized Windows variants you need to use the localized term (See comments for some examples).

alternatively you can use the shortcut control /name Microsoft.CredentialManager in the run dialog (WIN+R)
Edit the git entry under Windows Credentials, replacing old password with the new one.

edited Oct 14 '21 at 11:34

Troll

1,895
3
15
34

answered Aug 30 '18 at 08:49

mpro

14,302
5
28
43

12

Thanks, that worked for me as well and solved the problem. You need this solution if you have different Github accounts on your device – Dany Wehbe Nov 21 '18 at 16:44
8

It worked for me too though i am using multiple gilab accounts so what i did i updated my all the gitlab account with the same password that i have in my Credential Manger and the problem is solved Thanks@mpro – Rajan Chauhan Nov 27 '18 at 06:22
This seems a much cleaner solution under Windows and worked perfectly for me after updating my domain network password. – julealgon Dec 28 '18 at 12:29
8

Note: type it in your language system. Rus: "Credential Manager" = "Диспетчер Учетных Данных" – Dyno Cris May 26 '19 at 18:25
@DanyWehbe If you have different Github account then I would suggest you to merge them into one, it will make it more easy for you to manage. – Srijan Chaudhary Aug 24 '19 at 04:00
In my case editing credentials did not work for some reason. I had to remove credentials completely and add it again. – BugHunter Sep 25 '19 at 16:57
3

Great answer. This is especially a case with your work accounts where you have to change your passwords every now and then. – geekidharsh Sep 26 '19 at 17:53
8

In German it is "Anmeldeinformationsverwaltung" and then "Windows-Anmeldeinformationen". – nachtigall Dec 03 '19 at 11:14
Go to Windows credentials. You could see the git below. Change the password and try gitbash . – Akarsh Kolanu Jan 17 '20 at 22:38
4

In French it is "Gestionnaire d’informations d’identification". – Maarti Jan 28 '20 at 16:06
1

How to create the git credential in the first place? – Pedro77 Feb 21 '20 at 13:43
Perfect answer. Worked for me on GitLab. – nocdib Jul 22 '20 at 15:39
It worked for me, as i was facing issue while pushing my commit to my gitlab personal account. Meanwhile i had saved other gitlab creds. from my office. Deleting all creds. solved my problem ofc by help of this ans. Thanks btw ;) – Hassan Raza Jul 27 '20 at 19:16
1

@Maarti : I have "Gestionnaire d'identification". Maybe it depends on which Windows version one is on? I'm on Windows 10 Enterprise. – Jean-David Lanz Jan 12 '21 at 15:43
Swedish = Autentiseringshanteraren – Yamo93 Apr 23 '21 at 07:15
Worked like charm.. first I tried to clone Proj. with wrong credentials but in the meantime wrong credentials as were automatically stored in Win. Cred. Manager. I just had to edit them and update the new ones and clone them again. – kishorK Jul 28 '22 at 12:18
Oh well! It works like charm! How could you explain that ? :) – Niz.Dam Jul 26 '23 at 19:16

score 466 · Answer 2 · edited Nov 15 '21 at 17:06

466

For me, the following worked:

Do not use your GitLab password, but create an access token and use it instead of your password:

In GitLab, at the top-right corner, go to Personal Profile → Settings → Access Tokens
Create a new personal access token (check the api option)
git clone ...
When you are asked for your password, copy and paste the access token instead of your GitLab password

edited Nov 15 '21 at 17:06

Troll

1,895
3
15
34

answered Jul 02 '18 at 10:07

JavAlex

4,974
1
12
14

4

Alternatively, on Windows, replace the password in Windows Credential Manager for the token. – Original BBQ Sauce Mar 10 '21 at 15:45
I had already created a token but didn't know that after this you login with it instead of the password. Thanks for the tip. – Telmo Dias Apr 14 '21 at 08:46
For me using password was not working (and I didn't have tokens yet), it only worked when I created a token and used it instead. Thanks!!! – Alisson Reinaldo Silva May 11 '21 at 16:24
5

This should be the accepted answer. It is necessary in some projects according to the security configuration. Gitlab password will never work, just create and use your token. (Save your token in a secure place for future uses). – eduardosufan Jul 08 '21 at 13:45
17

LOL, didnt found any place telling me that I should use access token in password field... – Alexandre Prazeres Aug 31 '21 at 01:14
A token name needs to set first. – Friedrich -- Слава Україні Sep 15 '21 at 17:30
This response deserves more upvotes, for the sheer user-friendliness. And I'm absolutely baffled, that the password is not my actual gitpassword but the token. I should have guessed it, but not going to lie, I hate how cumbersome gitlab feels. – ak.leimrey Jan 12 '22 at 11:50
It worked! I was beating my head against the wall for hours with this. I don't remember seeing use the personal access token as the password anywhere -_- – WTFranklin Feb 11 '22 at 14:43
can you give an example of how to store the personal access token and then using it via git command in a bash shell? – majorgear Feb 18 '22 at 15:28
when I try git clone , it's not asking for a password. Directly cloning the project. I do have token .gitconfig but still receiving same error – Krtti Mar 02 '22 at 14:59
After creating Access Token, go to Credential Manager and change the password for the ```git:https://gitlab....``` and try ```git clone``` again. Worked for me – lpkej Mar 07 '22 at 14:32
To clarify for some use cases: you need to use this method if you have 2FA turned on for your account because you can't authenticate with 2FA via command line process (i.e. running git commands via the CLI). – KenLFG Mar 23 '22 at 18:40
3

Doesn't work for me, got no idea why, I've been cracking my head at this for far too long – Villager Apr 10 '22 at 09:02
Looks 'Settings' is 'Preferences' in GitLab dropdown now. Creating a token and updating it into Windows Credentials Manager 'Password' field worked. I have `credential.helper=wincred` (if you do `git config --list` you see what you have) – Vladislav Povorozniuc Jul 14 '22 at 18:39
how do I set the contents of the access token? I need an access token that I can memorize because I am not comfortable storing the access token in any application on my computer. – dinosaur Aug 31 '22 at 19:18
it happens if you authenticate your gitlab account with your gmail's email address. So the best option is to create a web token as it has been explained in with the screenshots. Save that web_token somewhere and always use that web token. Reason it does not accept your gmail password is because gmail will never gives your password to 3rd party. This is a security breach. – bizimunda Nov 02 '22 at 09:13
"when you are asked for your password"--> this only happens if there was previously no password or token. If one was defined git continues to use it. I now have a new token however and need to know how to get git to use it instead of the old one. – Christopher Hamkins Mar 14 '23 at 13:13
Does This access token work for all projects you have access to automatically or do they have to be manually added? – Micah Apr 24 '23 at 18:51
This worked for me. Thank you soo much! additionally, I ran command at project level: git config --unset credential.helper – AskQ Jun 05 '23 at 15:51
you saved my life . – Yogi Arif Widodo Aug 30 '23 at 22:34

score 332 · Answer 3 · edited Nov 15 '21 at 17:12

332

You can try the following command:

git config --system --unset credential.helper

Then, enter a new password for Git remote server.

edited Nov 15 '21 at 17:12

Eric Bolinger

2,722
1
13
22

answered May 30 '18 at 05:41

hatanooh

3,891
1
14
9

37

Note that on Windows you need to run it as Administrator, otherwise you'll get permission errors – Eternal21 Aug 05 '18 at 01:34
14

It depends where you put your credentials. If the previous command does not work try also using global flag: `git config --global--unset credential.helper` – Luca Natali Oct 15 '18 at 10:24
1

This is the most relevant answer for the OP as it addresses the issue, and doesn't go on some "on Windows" tangent. Also, as a side note, you may need to run this command as `sudo` if your user doesn't have access to `/etc` – Ghostrydr Oct 17 '18 at 16:43
git config --system credential.helper manager, to use credential.helper again. – hatanooh Feb 19 '19 at 01:43
9

If you unset credential helper, you would have to provide username and password each time connecting to the GIT repository. To fix that you can set helper again by using the following command: git config --global credential.helper store – Tomasz Czechowski Sep 02 '19 at 07:05
What if you don't have administrator access? – Not a bug May 19 '20 at 07:52
1

If you don't have administrator access omit --system or --global flag and set the credential helper only for your current git repository – Juan Rojas Nov 16 '20 at 16:31
this also works on Mac OS.. You still need an admin access!! – Velu Jun 15 '22 at 09:59
When re-setting the password with git config --global credential.helper store, the same note about needing sudo if you don't have /etc access also applies. – redeveloper May 24 '23 at 20:18

score 136 · Answer 4 · edited Dec 06 '19 at 18:23

136

I got the same error and I solved this by :

Apply command from cmd (run as administrator)

git config --system --unset credential.helper
And then I removed gitconfig file from C:\Program Files\Git\mingw64/etc/ location (Note: this path will be different in MAC like "/Users/username")
After that use git command like git pull or git push, it asked me for username and password. applying valid username and password and git command working.

hope this will help you...

edited Dec 06 '19 at 18:23

Barry Michael Doyle

9,333
30
83
143

answered Jun 26 '18 at 11:56

Bharti Ladumor

1,624
1
10
17

16

If you get that error, you can just run your command prompt as Administrator, and the error goes away. – Eternal21 Aug 05 '18 at 01:33
FYI: Just resetting the config (your first cmd) worked. I then did my git push and blammo! I think its because my shop requires monthly password changes so the internal git lab goes haywire. – yardpenalty.com Mar 15 '19 at 15:34
4

also try it this way with **--global** `git config --global --unset credential.helper` – Mike Aug 24 '19 at 02:06
deleting gitconfig file i get error: "error setting certificate verify locations: cafile" – Alexbogs Dec 01 '20 at 11:51

score 87 · Answer 5 · answered Jun 27 '18 at 00:30

87

The only thing that worked for me was using https://username:Password@gitlab.com/user/projectgit instead of https://gitlab.com/user/projectgit. See https://gitlab.com/gitlab-com/support-forum/issues/1654

answered Jun 27 '18 at 00:30

Paulo Morgado

14,111
3
31
59

Thanks. Although for me have to replace it with SSL repo url but your answer make me help out. I have upvoted it. – Muzzamil Apr 01 '20 at 13:56
Thanks. I didn't have such issue when using BitBucket or Github. With GitLab I have to create personal access token, then use that in remote origin `git remote set-url origin https://usernameHere:personalAccessTokenHere@gitlab.com/usernameHere/projectNameHere` – Woppi Jun 19 '20 at 03:26

score 50 · Answer 6 · edited Nov 30 '18 at 20:36

50

Go to Windows Credential Manager (press Windows Key and type 'credential') to edit the git entry under Windows Credentials. Replace old password with the new one.

Windows Credential Manager

edited Nov 30 '18 at 20:36

JJJ

32,902
20
89
102

answered Nov 30 '18 at 20:07

Andy Quiroz

833
7
8

OP is on macOS, not Windows. – Matthieu Brucher Nov 30 '18 at 20:37
This wouldn't help OP, but it worked like a charm on my Windows dev box. – Tony Feb 08 '19 at 15:17

score 45 · Answer 7 · answered Jul 17 '19 at 13:27

45

Just add your username before the domain:

https://**username**@gitlab.com/user/projectgit

And the assistant will ask you the password

answered Jul 17 '19 at 13:27

gal007

6,911
8
47
70

2

https://:@gitlab.com/user/project.git – Saleh Rahimzadeh Sep 01 '22 at 06:46

score 37 · Answer 8 · edited Jun 03 '19 at 10:02

37

I was also facing the same issue. The reason for the problem was authentication error. To solve this problem go to Control Panel -> Credential Manager -> Generic Credentials here find your gitlab credential and edit them. Make sure your ID password is right or not

edited Jun 03 '19 at 10:02

barbsan

3,418
11
21
28

answered Jun 03 '19 at 09:43

Kshama Jain

469
5
3

This did the trick, in my case it was because the company forces us to change the domain password every few months. This change didn't update the credentials in this credential manager. As soon as I updated the password it was working. – k4yaman Dec 02 '19 at 12:18

score 31 · Answer 9 · answered Jan 11 '18 at 14:22

31

If you are using git > 2.11 and using Kerberos to interact with Gitlab you need set this configuration in your local git to avoid the remote: HTTP Basic: Access denied error.

$ git config --global http.emptyAuth true

Source

answered Jan 11 '18 at 14:22

Pigueiras

18,778
10
64
87

1

I'm not using Kerberos but thank you for your reply. – jeancode Jan 11 '18 at 18:04
`Kerberos` aren't necessary. Thanks! https://git-scm.com/docs/git-config – contributorpw Aug 01 '18 at 14:37
After doing a clean install of Git on Windows this morning. This answer solved Access denied error for me. – James Nov 12 '18 at 12:48
Holy cow - I went through all the other suggestions and finally FINALLY this one worked. Indeed was using Kerberos! – Bon Crowder at MathFour Feb 19 '20 at 20:04

score 25 · Answer 10 · edited Oct 24 '19 at 22:56

25

Well, I faced the same issue whenever I change my login password.

Below is the command I need to run to fix this issue:-

git config --global credential.helper wincred

After running above command it asks me again my updated username and password.

edited Oct 24 '19 at 22:56

halfer

19,824
17
99
186

answered Jun 26 '18 at 07:00

Vikash Pandey

5,407
6
41
42

score 20 · Answer 11 · answered Oct 06 '20 at 19:00

Before digging into the solution lets first see why this happens.

Before any transaction with git that your machine does git checks for your authentication which can be done using

An SSH key token present in your machine and shared with git-repo(most preferred) OR
Using your username/password (mostly used)

Why did this happen

In simple words, this happened because the credentials stored in your machine are not authentic i.e.there are chances that your password stored in the machine has changed from whats there in git therefore

Solution

Head towards, control panel and search for Credential Manager look for your use git url and change the creds.

There you go this works with mostly every that windows keep track off

Thanks @chuklore great to see people looking to understand the issue and not just quick fixes. — Manasvi Mittal, Jul 19 '21 at 17:27

score 19 · Answer 12 · answered Dec 18 '17 at 06:02

19

Note: do not mix GitLab SSL settings and GitLab SSH keys.

If what you have configured in your GitLab profile is an SSH public key, then your HTTPS URL would not use it.

Regarding your HTTPS credentials, double-check:

if the two-factor authentication is disabled, or
if you have special characters in your username or password, or
if you have a Git credential helper: git config credential.helper.

answered Dec 18 '17 at 06:02

VonC

1,262,500
529
4,410
5,250

1

- I have a space in my username because I authenticated Gitlab through Github - Two-factor autentication is disabled - What do you mean "If I have a Git credential helper? – jeancode Dec 18 '17 at 19:32
@jeancode I mean: what do you see when you type `git config credential.helper`: that could have cached the wrong credentials. – VonC Dec 18 '17 at 20:15
@jeancode For the space, did you percent encode it? (https://en.wikipedia.org/wiki/Percent-encoding#Character_data: %20) – VonC Dec 18 '17 at 20:15
I didn't do anything to the space in the name, the space comes from my name in GitHub, that GitLab grabbed during authentication login through Github. – jeancode Dec 19 '17 at 01:42
"authentication login through Github"... that does not looks like "my GitLab username and password". GitHub should not be involved here. – VonC Dec 19 '17 at 07:40
It is involved because you can Login to Gitlab through Github... Like I said, my name has a space in it because of my name in Github. Gitlab allows a user to authenticate signing in through Github. – jeancode Dec 20 '17 at 20:11
@jeancode I understand. Still, check what `git config credential.helper` returns. – VonC Dec 20 '17 at 20:13
this is the output `osxkeychain` – jeancode Dec 22 '17 at 21:36
@jeancode Then delete any credentials (https://help.github.com/articles/updating-credentials-from-the-osx-keychain/#deleting-your-credentials-via-the-command-line) in it related to github.com and gitlab.com, and try again. – VonC Dec 22 '17 at 21:37
1

I was getting the error due to trying to use deploy keys while two factor authentication was enabled. Apparently you can only use personal access tokens if two-factor is enabled. – Joshua Dyck Oct 15 '19 at 20:55
3

I solved, just editing the password of GitLab in Windows Credentials, Thanks! – Joel Meza Baca Jul 06 '20 at 15:15
I am facing the same issue for two days can not resolved this from sourcetree client. not understand why this is the most complicated user name and password changed ever made – Bastian Oct 07 '21 at 12:16
@Bastian What is your SourceTree version, Git version, OS version? And what type of URL are you using for your remote repo? https://... or git@gitlab.com? – VonC Oct 07 '21 at 12:18

score 16 · Answer 13 · answered May 26 '19 at 18:19

16

It happens if you change your login or password of git service account (GitHub or GitLab, Bitbacket, etc). You need to change it in Windows Credentials Manager too.

So, type "Credential Manager" (rus. "Диспетчер Учетных Данных") in Windows Search menu and go to your git service account and change data too.

answered May 26 '19 at 18:19

Dyno Cris

1,823
1
11
20

Although I didn't change my user or password (it is an AD credential), this happened to me because of a rebuild of the Gitlab server and the above solution has fixed this error. – John Ranger Sep 10 '19 at 12:41

score 14 · Answer 14 · answered May 16 '20 at 08:10

14

I beleive I'm little late here. But I think this would help the new peeps!

My Errors were: remote: HTTP Basic: Access denied

remote: You must use a personal access token with 'read_repository' or 'write_repository' scope for Git over HTTP.

remote: You can generate one at https://gitlab.com/profile/personal_access_tokens

fatal: Authentication failed for 'https://gitlab.com/PROFILE_NAME/REPO_NAME.git/'

I'm on Ubuntu but this worked for me:

Goto https://gitlab.com/profile/personal_access_tokens
Create new token and mark check to all.
Copy your token
Now go to your Terminal and paste it like this.

git clone https://oauth2:YOUR_TOKEN@gitlab.com/PROFILE_NAME/REPO_NAME.git/

answered May 16 '20 at 08:10

Gaurav

479
4
5

`:@gitlab.com//.git` works for me when configuring a "Mirroring Repository" – mochadwi Aug 02 '20 at 13:35
You sir, are my hero today! – Barry Michael Doyle Oct 13 '20 at 09:15
For me with out profile name worked. git clone https://oauth2:YOUR_TOKEN@gitlab.com/REPO_NAME.git/ – Harish Apr 29 '22 at 11:02

score 13 · Answer 15 · answered Oct 12 '18 at 05:27

13

Open command prompt as administrator then run this command:

git config --system --unset credential.helper

answered Oct 12 '18 at 05:27

MD. Shafayatul Haque

928
11
19

could not lock config file C:\Program Files\Git\mingw64/etc/gitconfig: Permission denied – Oct 19 '19 at 07:13
1

You do not use config file, just open you command prompt as administrator and run the command. Hope this helps – MD. Shafayatul Haque Oct 19 '19 at 08:21
try with sudo git config --system --unset credential.helper – bimeri noel Nov 15 '21 at 20:40

Artorias2718 · Answer 16 · 2019-07-01T19:15:03.817

There are two ways I got around this problem:

I added my username to the front of the remote URL (https://username@gitRepoURL)
- Not always the best solution; where I work, even though we're slowly moving towards using GIT, we have our applications on a network drive, so if I do this, only I can push changes even if someone else worked on a feature.
I can't run git config --system --unset credential.helper from GIT Bash, so I had to open up an Admin Command Prompt and run it there (this assumes you installed GIT such that it can run from both GIT Bash and the Command Prompt). From Bash, I get a "could not lock config file" error.

for more info, see: `git config -l`. Also try above with `--global` instead of `--system` — Mike, Aug 24 '19 at 02:14

score 11 · Answer 17 · answered Sep 22 '20 at 15:44

It is certainly a bug, ssh works with one of my machines but not the other. I solved it, follow these.

Generate an access token with never expire date, and select all the options available.
Remove the existing SSH keys.
Clone the repo with the https instead of ssh.
Use the username but use the generated access token instead of password.

alternatively you can set remote to http by using this command in the existing repo, and use this command git remote set-url origin https://gitlab.com/[username]/[repo-name].git

Yeah, answers above did not work for me, and this was straightforward - "git remote set-url origin [https://new-token-name:token-value@gitlab.com/path/to/repo/](https://new-token-name:token-value@gitlab.com/path/to/repo/)" — MiroJanosik, Jan 02 '22 at 21:59

score 10 · Answer 18 · edited Jun 25 '18 at 04:00

10

Try this:

Go to: C:/Users/(YourUserName)/
Delete file .gitconfig

edited Jun 25 '18 at 04:00

Stephen Rauch

47,830
31
106
135

answered Jun 25 '18 at 03:29

boy_vkallstar

141
1
3

1

do not do this one, this kills your settings in general – ZR87 Jun 22 '21 at 13:35

score 9 · Answer 19 · edited Oct 28 '19 at 20:48

9

Same problem with Sourcetree On Mac

Solution: Delete the password in keychain access.

https://community.atlassian.com/t5/Sourcetree-questions/SourceTree-quot-fatal-Authentication-failed-for-quot/qaq-p/201844

When you try to push again it will ask for your password.

edited Oct 28 '19 at 20:48

NicolasElPapu

1,612
2
11
26

answered Jul 31 '19 at 07:34

rotoava

625
8
18

Did not work for me in Mac, It keeps failing with error `HTTP Basic: Access denied. The provided password or token is incorrect` – Saif May 23 '23 at 12:20

score 8 · Answer 20 · answered Oct 10 '18 at 14:04

8

Go to Control Panel->Credential Manager->Windows Credentials select github or gitlab credentials and modify it. This is for windows10

answered Oct 10 '18 at 14:04

SanjX

957
1
8
12

score 8 · Answer 21 · edited Aug 07 '19 at 07:59

8

When I had the same problem,

I solved it by removing the file "passwd" in

C:\Users\<USERNAME>\AppData\Local\Atlassian\SourceTree

After removing Sourcetree will prompt for the password.

Note:
OS Version : win10 
Sourcetree Version:  3.1

edited Aug 07 '19 at 07:59

SAMUEL

8,098
3
42
42

answered Jun 06 '19 at 08:45

Jean-Philippe Vankemmel

1,134
10
4

This solved my issue on source tree. – vinsinraw Mar 11 '22 at 11:43
This solved my issue with the Sourcetree. – Aldan Apr 17 '22 at 12:37

score 7 · Answer 22 · answered Aug 26 '18 at 06:22

7

i removed gitlab credential from 'Credential Manager' in windows and pushed successfully

answered Aug 26 '18 at 06:22

saiedkia

69
1
4

score 6 · Answer 23 · answered Jun 03 '19 at 10:48

For Mac user:

Go to keychain and delete gitlab accounts
Go to your project path in terminal and simply type git pull
Then you will be asked for username and password for gitlab
Enter your username which you will find out in gitlab account in profile section.
Then after that enter you updated password here.
Here we go, again try to push your code, it may help you guys.

score 6 · Answer 24 · answered Oct 05 '19 at 10:15

For me it was some other git URL placed in config file, so I did change it manually:

Move to .git/config file and edit it,
Remove invalid URL(if it's there) and paste the valid git SSH/HTTP URL like below way:

[remote "origin"]
        url = git@gitlab.com:prat3ik/my-project.git

And it was working!!

score 6 · Answer 25 · answered Nov 26 '19 at 10:41

I had the same problem using GitLab, and here's how i fixed it:

Generate an access token: to do so go to settings/access tokens, then give it a name and expiration date and submit.
In your project files open the "config" file in ".git" directory: /.git/config.
You will find a line like this:

[remote "origin"] url = https://[username]:[token]@your-domain.com/your-project.git
You will have your gitlab username instead of [username], and you should replace [token] with your token generated in step 1.
Save the changes.

score 6 · Answer 26 · answered Jul 27 '20 at 18:26

6

Strangely enough, what worked for me was to sign out and sign back in to the GitLab web UI.

I have no earthly idea why this worked.

answered Jul 27 '20 at 18:26

ATOMP

1,311
10
29

score 5 · Answer 27 · answered Nov 05 '18 at 10:07

it worked for me: I use Mac and I wrote the path on finder:

~/Library/Application Support/SourceTree

I deleted the auth file which should be like

yourUserName@STAuth-gitlab.yourAdress

then tried to push and pull the code from the source tree and it worked.

You can also read the following answers:

https://community.atlassian.com/t5/Sourcetree-questions/How-to-update-HTTP-S-credentials-in-sourcetree/qaq-p/297564

score 5 · Answer 28 · answered Nov 22 '18 at 21:04

So for me the problem was that I had created my GitLab account via linking my GitHub account to it. This meant that no password formally existed for the account as it was created via hotlink between GitHub and GitLab. I fixed it by going to GitLab Settings -> Password -> and writing the same password as my GitHub account had.

lkostka · Answer 29 · 2018-12-18T10:58:40.683

None of the above solutions worked for me and I don't have admin rights on my laptop, but they eventually led me to the git tools credential storage doc :

My setup Windows 10 | git version 2.18.0.windows.1 | Clone through HTTPS link

This solution works if you use wincred as credential helper :

> git config --global credential.helper
wincred

Changing the helper to "cache" should do the trick, as it will ask you to provide your credentials again. To set it to cache, just type :

> git config --global credential.helper cache

Check your update is active:

> git config --global credential.helper
cache

You should now be able to clone / pull / fetch as before.

score 4 · Answer 30 · answered Mar 10 '18 at 18:11

In my case I reinstalled to the latest version of git (currently 2.16.2). I don't know if it was that my old version of git was outdated, but I read on a github page that this should be done if you stumble into https cloning errors. I figured it was an https cloning error as the error focuses on HTTP Basic, while GitLab uses HTTPS. I might be wrong in this thought process, but the solution helped in my case, and I hope this helps anyone in the future!

score 4 · Answer 31 · answered Jun 11 '18 at 10:31

If your trying to login Gitlab with your existing Git account. You need to reset your password of Gitlab, for the first time.

Step: Navigate to setting by clicking your profile icon( drop down menu on top right corner).
Step: Go to settings
Step: Click on the lock icon or glyphicon icon(i.e password).
Step : Enter the new password for Gitlab.

score 3 · Answer 32 · edited Aug 06 '18 at 15:17

3

GO TO C:\Users\<<USER>> AND DELETE THE .gitconfig file then try a command that connects to upstream like git clone, git pull or git push. You will be prompted to re-enter your credentials. Kindly do so.

edited Aug 06 '18 at 15:17

prashant17

1,520
3
14
23

answered Aug 06 '18 at 13:55

Dennis Mutegi

39
1

score 3 · Answer 33 · answered Mar 25 '21 at 11:00

3

I had to do below two steps to resolve this issue

create ssh-keygen and add the public key to my gitlab account
disable https using below command

git config --global http.sslVerify false

answered Mar 25 '21 at 11:00

Mateen

1,631
1
23
27

Andy · Answer 34 · 2023-02-04T07:55:03.760

There is another reason for this error apart from invalid credentials in your credential manager.

I had a problem where my account was using LDAP for authentication but still had a password expiration date set. Because the server was configured to use LDAP authentication only, the password expiration was not visible in the web UI and became only an issue after GitLab published a security fix with version 13.12.2.

You can check and edit the password_expires_at attribute of a user account via the GitLab Rails Console. Setting it to nil solved the issue and got the LDAP authentication working again.

score 3 · Answer 35 · answered Aug 08 '22 at 11:38

3

This worked for me in Windows and Mac as well:

https://Username:accessToken@git.gitlab.com/path/to/repo/my-app.git

Here accessToken is your personal access token created in GitLab.

answered Aug 08 '22 at 11:38

Shailendra Madda

20,649
15
100
138

1

For access token generation in Gitlab (sidebar menu): 1. Settings 2. Access Tokens 3. Set name for access token 4. Set expiration date and scope 5. Create project access token, then use git command: git clone https://YOUR_LOGIN:ACCESS_TOKEN@git.gitlab.com/path/to/repo/my-app.git – Jacob Jul 28 '23 at 11:04

score 2 · Answer 36 · answered Jan 11 '19 at 12:56

2

When the Windows Credential Manager asks for your credentials to access GitLab, those are username and password you use when accessing GitLab. EG: use your email and password.

answered Jan 11 '19 at 12:56

aercolino

2,193
1
22
20

score 1 · Answer 37 · answered Feb 28 '19 at 10:02

1

go to credential setting on your windows computer and Remove https://gitlab.com/sobopla/Geronimod.git

answered Feb 28 '19 at 10:02

Taib Lamkhazni

21
2

OP said macOS . – Tony Apr 29 '19 at 18:51

Hearen · Answer 38 · 2019-09-18T06:40:04.680

Just for reference, I encountered this issues while using the URL wrongly after I generated and pasted the ssh_rsa.pub to the SSH Keys in gitlab.

$ git clone http://gitlab.x
Cloning into 'start-up'...
remote: HTTP Basic: Access denied
remote: You must use a personal access token with 'api' scope for Git over HTTP.
remote: You can generate one at http://gitlab.x

Solved by using the following URL instead.

$ git clone gitlab@gitlab.xxx.com/your_project.git

score 1 · Answer 39 · answered Apr 06 '20 at 07:32

I've faced this same issue after once I've entered the wrong credentials of my git account. The thing that did work for me is, open keychain Access -> Password -> find your entered wrong password and update it and hit save, after that you will be able to perform your operations on git without any issue.

I hope this works for you.

score 1 · Answer 40 · answered Oct 27 '20 at 10:43

1

On mac use KeyChain -> Login -> Password: change password

answered Oct 27 '20 at 10:43

Yu Jiaao

4,444
5
44
57

What password in the keychain? I don't see anything containing with "git". – Arjun Kalidas Mar 08 '23 at 04:24

score 1 · Answer 41 · answered Nov 30 '20 at 07:08

I had the same issue but before I went ahead to implement any of the suggestions on here, I checked if I was still logged into my github account. I had the problem while working in my Gitlab account. I found out I was still logged into my Github account and I logged out of the account immediately. I tried to clone again in Gitlab and I didn't have the error and the clone was successfully.

Janith Priyankara · Answer 42 · 2021-09-18T15:41:34.160

1

You have to update the config file inside the .git directory with current access token. See This Link where I resolved the problem caused by accidentally changing the access token. I was using GITLAB and CLion,

edited Sep 18 '21 at 15:41

answered Sep 17 '21 at 14:19

Janith Priyankara

73
5

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-ask). – Community Sep 17 '21 at 14:50

score 1 · Answer 43 · answered Jan 18 '22 at 17:34

I got the same error and I solved this by :

Open Windows search
Type: Git Bash
Click second mouse button and select: Run as administrator
Go to your project directory: cd "C:\path\to\our\project\name"
Execute command: git config --system --unset credential.helper NB : On linux run this command with sudo command: sudo git config --system --unset credential.helper

score 1 · Answer 44 · answered Apr 26 '22 at 09:31

1

For me, i created a personal access token and then updated my git origin as thus:

https://<personal_access_token_name>:<personal_access_token>@gitlab.com/username/your-project.git

answered Apr 26 '22 at 09:31

Macdonald

880
7
21

score 0 · Answer 45 · answered May 15 '18 at 11:59

0

I tried with browser URL for the repository then

git clone $(browserURL)

it prompted for my username and then my password

It worked fine then

answered May 15 '18 at 11:59

Saurabh Verma

627
1
14
27

score 0 · Answer 46 · answered May 13 '22 at 07:53

0

I have same problem i followed these steps and it has been resolved. step 1:- set username amd password setp 2:- git push -f origin

answered May 13 '22 at 07:53

sachin kannaujiya

129
1
3

score 0 · Answer 47 · answered Dec 17 '22 at 22:09

In Gitlab go to the Administrator/Settings/General/SignIn Restrictions section.

If you are authenticating to your GitLab over HTTPS, make sure that you have:

Allow password authentication for Git over HTTP(S)

checked. This option assumes that you are not using 2FA. If you are not using an external authentication provider, you show also have the:

Allow password authentication for the web interface

also checked.

score 0 · Answer 48 · edited Jan 30 '23 at 05:16

Yes, this is a login credentials issue. In my case I was working on some ad-hoc temporary branch, I made changes, and committed it to the same branch. While pushing I was getting this error.

Next, I checked out in master. Took git pull, and it asked for my updated credentials. I entered correctly. After that, I checked out the ad-hoc temp branch, created a feature branch and pushed that branch to remote with no issues this time.

score 0 · Answer 49 · answered Feb 02 '23 at 15:27

I'd like to add one more variation to all of these already: if you are accessing a company instance of GitLab that is not behind a proxy, make sure you do not have the proxy variables set - e.g. HTTP_PROXY, HTTPS_PROXY. After going through pretty much all of the solutions in this question, I figured out my problem was due to this.

score 0 · Answer 50 · answered Jun 14 '23 at 11:56

0

Just add your repo link like this:

https://oauth2:<PAT>@gitlab.com/<Project>/<repo>.git

answered Jun 14 '23 at 11:56

thirteen4054

465
4
17

score -1 · Answer 51 · answered Jun 18 '19 at 05:53

-1

Create a new access token from gitlab ->setting --> access token

answered Jun 18 '19 at 05:53

Abhijit som

5

GitLab remote: HTTP Basic: Access denied and fatal Authentication

51 Answers51

Before digging into the solution lets first see why this happens.

Why did this happen

Solution

Linked