Authentication Failure with GitHub Desktop

parthe commented 4 years ago

I am unable to pull, push for a private repository through the GitHub Desktop interface. However, the commands and work perfectly fine when I run them through the command prompt i.e.(Repository -> Open in Command Prompt)

A clear and concise description of what the bug is. When I try "Fetch Origin" or "Push" from the GUI of the GitHub Desktop, it shows me the following

I have ruled out the possibility of all the 5 error messages the interface shows me.

Furthermore, if I uninstall GitHub Desktop and reinstall it, the installation interface does not ask me for any login, i.e., it does not completely delete all files during uninstallation (and perhaps uses some old credentials).

I tried removing all files in the GitHub folder where the installation was done and then reinstalling the GitHub Desktop app, but saw the same behavior.

It is not clear what the backend is for commands clicked via the GitHub Desktop GUI

Version & OS

GitHub Desktop 2.2.4 on Windows 10 Pro

steveward commented 4 years ago

@parthe thanks for contributing. Could you upload the log file from GitHub Desktop so that I could get some more information about this error? To access the log files go to the file menu in GitHub Desktop and select Help > Show Logs in Finder (macOS) or Explorer (Windows).

The log files are created daily -- please upload a log file as an attachment from a day where you experienced the issue.

jcornelius commented 4 years ago

Maybe I've missed something in all the other discussion in other issues like #6538 and #7982 , but nothing here seems to address the issue for me.

Environment

Mac OS Catalina 10.15.2 Github Desktop 2.2.4

Fresh upgrade from legacy version of Github Desktop where everything worked fine. The authentication issue has been the same no matter what I've tried.

Sequence of things I've done.

I first added the repo from my hard drive as that seemed the easiest way to go.
Logged out and logged in again using username/password in the app
Logged out and logged in using the browser
Deleted old SSH Key from my profile on https://github.com/settings/keys
Deleted local copy of repo and attempted to clone new copy from Github
Restarted the computer
Logged out & in again using both authentication methods
Tried to clone both public and private repos

Nothing changes. I get this message every time.

Here's what's in the log from the last attempt. It's the same message regardless of which repo I attempt to clone.

2020-01-10T18:15:24.525Z - info: [ui] [AppStore.getAccountForRemoteURL] account found for remote: https://github.com/ninelabs/loopsbook.git - jcornelius (has token)
2020-01-10T18:15:25.034Z - error: [ui] `git -c credential.helper= -c protocol.version=2 clone --recursive --progress -- https://github.com/ninelabs/loopsbook.git /Users/jc/Web Projects/loopsbook` exited with an unexpected code: 128.
stderr:
Cloning into '/Users/jc/Web Projects/loopsbook'...
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Anyone have ideas on how to resolve this?

ignis-sec commented 4 years ago

Maybe I've missed something in all the other discussion in other issues like #6538 6538 and #7982 , but nothing here seems to address the issue for me.

I'm here because i got notified from the 6538. 6538 was about issue using ssh keys with github desktop where we were trying to pull/push to a remote with the address like ssh://user@domain:/dir/to/project, but ssh key's passphrase was being a problem.

Maybe #8041 or #5291 can be helpful?

tierninho commented 4 years ago

@jcornelius You deleted the old SSH keys, but did you create a new one? instructions are here: https://help.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent

jcornelius commented 4 years ago

@tierninho I didn't since the app didn't seem to want one. Now I have created a new SSH key and added to my profile on Github. The app still throws the same error.

FWIW: I can use the command line to clone and push.

jcornelius commented 4 years ago

Update:

I uninstalled Github Desktop,
deleted all the local repos,
restarted the computer to clear out any lingering processes,
reinstalled Github Desktop
signed in using the native app authentication (including 2FA)
attempted to clone a repo

It still doesn't work. Here's the log:

2020-01-10T20:34:29.846Z - info: [ui] [AppStore] loading 0 repositories from store
2020-01-10T20:34:30.057Z - info: [ui] Opt in reported.
2020-01-10T20:34:30.174Z - info: [ui] [Welcome] no sign in step found. ignoring...
2020-01-10T20:34:30.437Z - info: [ui] [Welcome] no sign in step found. ignoring...
2020-01-10T20:34:30.927Z - info: [ui] launching: 2.2.4 (Mac OS 10.15.2)
2020-01-10T20:34:30.938Z - info: [ui] execPath: '/Applications/GitHub Desktop.app/Contents/Frameworks/GitHub Desktop Helper.app/Contents/MacOS/GitHub Desktop Helper'
2020-01-10T20:34:30.952Z - info: [ui] [Welcome] no sign in step found. ignoring...
2020-01-10T20:34:31.032Z - info: [ui] [Welcome] no sign in step found. ignoring...
2020-01-10T20:34:32.609Z - info: [ui] [Welcome] advancing to step: SignInToDotCom
2020-01-10T20:34:32.614Z - info: [ui] [Welcome] current sign in state not found. ignoring...
2020-01-10T20:34:48.562Z - info: [ui] [Welcome] kind Authentication is the same as Authentication. ignoring...
2020-01-10T20:34:52.197Z - info: [ui] [Welcome] kind Authentication is the same as Authentication. ignoring...
2020-01-10T20:34:55.155Z - info: [ui] [Welcome] kind Authentication is the same as Authentication. ignoring...
2020-01-10T20:35:02.149Z - info: [ui] [Welcome] kind TwoFactorAuthentication is the same as TwoFactorAuthentication. ignoring...
2020-01-10T20:35:02.848Z - info: [ui] [AppStore] adding account jcornelius (J Cornelius) to store
2020-01-10T20:35:02.865Z - info: [ui] [Welcome] advancing to step: ConfigureGit
2020-01-10T20:35:02.965Z - info: [ui] [Welcome] no sign in step found. ignoring...
2020-01-10T20:35:03.047Z - info: [ui] [Welcome] no sign in step found. ignoring...
2020-01-10T20:35:03.591Z - info: [ui] [Welcome] no sign in step found. ignoring...
2020-01-10T20:35:07.876Z - info: [ui] [Welcome] advancing to step: UsageOptOut
2020-01-10T20:35:09.591Z - info: [ui] Opt in reported.
2020-01-10T20:35:09.597Z - info: [ui] [Welcome] no sign in step found. ignoring...
2020-01-10T20:36:53.101Z - info: [ui] [AppStore.getAccountForRemoteURL] account found for remote: https://github.com/jcornelius/jcornelius.com.git - jcornelius (has token)
2020-01-10T20:36:53.637Z - error: [ui] `git -c credential.helper= -c protocol.version=2 clone --recursive --progress -- https://github.com/jcornelius/jcornelius.com.git /Users/jc/Web Projects/jcornelius.com` exited with an unexpected code: 128.
stderr:
Cloning into '/Users/jc/Web Projects/jcornelius.com'...
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

(The error was parsed as 2: Authentication failed. Some common reasons include:

- You are not logged in to your account: see GitHub Desktop > Preferences.
- You may need to log out and log back in to refresh your token.
- You do not have permission to access this repository.
- The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits.
- If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account.)

tierninho commented 4 years ago

I attempted to clone the same repo, and did so successfully. 🤔

Can you run ssh -T git@github.com which may require your password and report back.

cc @steveward for any ideas here

jcornelius commented 4 years ago

Can you run ssh -T git@github.com which may require your password and report back.

$ ssh -T git@github.com
Enter passphrase for key '/Users/jc/.ssh/id_rsa': 
Hi jcornelius! You've successfully authenticated, but GitHub does not provide shell access.

/cc @tierninho

tierninho commented 4 years ago

GitHub still isn't able to authenticate you despite just setting up the SSH keys on your account. You can also use the HTTPS instead, but SSH should still work ideally.

GitHub has a help page specifically for that error message here which might help. Could also be the SSH agent or the git remote.

jcornelius commented 4 years ago

For whatever strange reason, running ssh-add /path/to/key solved it. Thanks, @tierninho.

tierninho commented 4 years ago

Awesome, thanks for the confirmation!

damien-mattei commented 4 years ago

my password was good in github desktop preferences but wrong in the .git/config file

for me the only working solution was to manually edit the file: .git/config

that contains this line: url = https://user:password@github.com/user/repo.git

change password to the GOOD password because it was an older one for me

Boehm92 commented 4 years ago

I had the same Problem as @jcornelius. When i tried to clone my repos, the access at my gitlab-server was denied. But i used github desktop on a diffrent pc with this server bevor. I solved it, with cloning a repo with visual studio code and added the local repo. I updated the branch with the "fetch origin button" and just then github deskop asked me the first time for my account credentials for gitlab. I tipped them in and now its working! Hopefully this is helpfull.

Firestar-Reimu commented 4 years ago

I had the same problem but I return this:

$ ssh -T git@github.com
git@github.com: Permission denied (publickey).

scosoli commented 4 years ago

Same problem here, could not authenticate and clone the repository to my local MBP. made it work after logging out and logging back in to Github Desktop

alexandre-liberato commented 4 years ago

I suppose that everyone here is trying to understand why Github Desktop stopped working when you start using SSH keys. So I've been trying to understand why Github Desktop didn't work with SSH and after doing a test, I realized that Git Bash works perfectly with SSH keys, BUT Gitbub Desktop only works if the repository is configured as HTTP. That is:

Git Bash works with

git@github.com:alexandre-liberato/project-curso-git.git

and with

https://github.com/alexandre-liberato/projeto-curso-git.git

BUT Github Desktop ONLY WORKS with

https://github.com/alexandre-liberato/projeto-curso-git.git

Well, I should have read the MANUAL before start using it. Here is what Github says about Github Desktop: https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/about-connections-to-github

GitHub Desktop connects to GitHub using HTTPS. If you use GitHub Desktop to access repositories that were cloned using SSH, you may encounter errors. To connect to a repository that was cloned using SSH, change the remote's URLs. For more information, see "Changing a remote's URL."

So, the problem is how Github handles SSH keys. I could not find a way to force it to use SSH keys and there is no place to configure Github Desktop to use SSH keys.

Question: Does anyone know how to configure both separately so that Git Bash uses SSH and Github Desktop uses HTTP?

marksteven commented 4 years ago

same problems here. will not connect throwing up all errors shown above. Anyone manage to get past the git@github.com: Permission denied (publickey).

100Worries commented 3 years ago

I know this may seem like a 'Do'h' kind of thing, but I received this error when trying to push from an account that didn't have write access to the origin. Simple oversight on my part, but I didn't notice off the bat until I saw a notice near my commit comment area about write access.

varungulati commented 3 years ago

Signout and sign in worked for me . https://stackoverflow.com/questions/24960247/how-do-i-sign-out-of-the-desktop-version-of-github/24960299

tliawi commented 3 years ago

I had same problem after I had updated a bunch of things (macos to Mojave, updated github desktop, and on github added 2 part SMS login verification). What fixed it was when I went to Github Desktop preferences, and logged in from there. It said it would login VIA my browser, where I was already logged in to gitHub, and sure enough it blinks my browser and comes back successful (I didn't have to enter userid or password or anything), and the problem was fixed.

WesJones127 commented 3 years ago

I forgot to add the -t rsa or -t ed25519 option to the ssh-keygen command so my key wasn't the right type. Solution was to generate a new key and then everything started working again.

evgen66rus commented 3 years ago

Same problem. Found in the log: ssh_askpass: exec(/usr/X11R6/bin/ssh-askpass): No such file or directory git@github.com: Permission denied (publickey). fatal: Could not read from remote repository.

akshri866 commented 3 years ago

This was the main culprit for me. If you can reproduce the same then i guess GitHub needs to improve for this https://github.com/desktop/desktop/issues/12484

code-warrior commented 3 years ago

I can verify that generating a new SSH key fixed the problem for me. GitHub

zjhu-QSM commented 2 years ago

I did all the thing listed above, still did not work..... until I uncheck the options : Use system openSSH, that options is under the menu Files/Options/Advanced

mass10 commented 2 years ago

for your information

When I met a problem as below. (GitHub Desktop: Version 2.9.4, x64)

log was

2021-11-25T05:08:50.023Z - error: [ui] `git -c credential.helper= -c protocol.version=2 fetch --progress --prune origin` exited with an unexpected code: 128.
stderr:
Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

(The error was parsed as 2: Authentication failed. Some common reasons include:

- You are not logged in to your account: see File > Options.
- You may need to log out and log back in to refresh your token.
- You do not have permission to access this repository.
- The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits.
- If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account.
- If you use SSH authentication, ensure the host key verification passes for your repository hosting service.
- If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.)

what I did

run ssh -T git@github.com
I found several github.com lines in my C:\Users\%USERNAME%\.ssh\known_hosts.
I removed duplicated lines.
Worked!

oguncimen commented 2 years ago

Delete repository on github if already exist.
Remove remote repository from app -> git remote rm origin
Delete repository to github desktop and sign out-sign in.
Add your repo to github desktop.

This worked for me.

GreeshSah commented 2 years ago

I did all the thing listed above, still did not work..... until I uncheck the options : Use system openSSH, that options is under the menu Files/Options/Advanced

This worked for me as well.

aislanspeedio commented 2 years ago

Use system openSSH this option is not available for me.

I'm using ubuntu deb version of the Github Desktop

icrichmond commented 2 years ago

I did all the thing listed above, still did not work..... until I uncheck the options : Use system openSSH, that options is under the menu Files/Options/Advanced

This is the only thing that worked for me, thank you!!

KhadijaNaz commented 2 years ago

I was facing same issue. Solution: 1] Open Github Desktop 2] Navigate to Files/Options/Advanced 3] Signout your account. 4] Now close the Github Desktop and open it again 5 ]Navigate to Files/Options/Advanced 6] Click on Signin 7] It will ask you to open default browser 8] Go ahead and give credentials. 9] This is worked for me.

If you are still facing issue Follow thses different steps https://github.com/desktop/desktop/issues/8860

AnisimovArthur commented 1 year ago

What worked for me was removing the project from the list and adding it again.

I ran into this when I changed the remote repository through the console.

mohangbits commented 1 year ago

I ran into this issue on 03/23/2023 and this helped me in resolving: https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/

doublesharp commented 1 year ago

Using the blog post above I ran ssh-keygen -R github.com in a terminal and then Github saved the new known_host ssh value the next time I tried to push from Github Desktop.

rijarobinson commented 1 year ago

The above worked for me as well.

HamzaNasry commented 1 year ago

Just sign out of the GitHub desktop and then sign in again with the browser. :/ - Worked for me.

umerfarooq777 commented 1 year ago

1-sign out 2-sing in you good to go

brownberrytechnologies commented 1 year ago

Re-clone the repo worked for me

brenoperucchi commented 1 year ago

~/Devs/signalforex on master *2 ❯ git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin

Warning: the ECDSA host key for 'github.com' differs from the key for the IP address '140.82.112.3'
Offending key for IP in /Users/brenoperucchi/.ssh/known_hosts:10
Matching host key in /Users/brenoperucchi/.ssh/known_hosts:33
Are you sure you want to continue connecting (yes/no)?

Delete line /Users/brenoperucchi/.ssh/known_hosts:10

❯git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin

Now everything should be fine

HamzaNasry commented 1 year ago

I keep getting random emails from this months later, its so weird.

SantiagoGaonaC commented 11 months ago

For commit in organizations: go to https://github.com/organizations/NAME-ORG/settings/oauth_application_policy Remove Third-party application access policy, it should look something like this: worked for me

alfatahnesab commented 10 months ago

I was facing same issue.

Reason: Old SSH auth key was removed,

Solution: Worked for me.

Only remove local cloned repo. (Skip if you are choosing new clone location)

Download and install SourceTree

Login GitHub Account using Host Github Auth Type: OAuth Protocol: SSH

Then, Click on Connect Account.

Copy generated SSH Key value to click on Copy to Clipboard button

Add New SSH Key

In the "Access" section of the sidebar, click SSH and GPG keys.

Click New SSH key or Add SSH key.

In the "Title" field, add a descriptive label for the new key. For example, if you're using a personal laptop, you might call this key "Personal laptop".

Select the type of key, either authentication or signing. For more information about commit signing, see "About commit signature verification."

In the "Key" field, paste your public key.

Click Add SSH key.

And, Go back to SourceTree app to save details.

You good to go!

stack-wuh commented 6 months ago

maybe use proxy tools, change proxy node its work

justingolden21 commented 5 months ago

I use github desktop to connect to gitlab account repos and it's worked fine for a few years. Confirmed my secret key still has several months left before it expires.

I haven't changed anything and now I can't seem to push. I'm not signed in under options to github (since it's a gitlab account) and there's no option to sign in to gitlab under options or repo specific.

Today's Log

``` 2024-06-03T16:08:49.669Z - info: [main] Using toast activator CLSID {27D44D0C-A542-5B90-BCDB-AC3126048BA2} 2024-06-03T16:08:50.448Z - info: [ui] [AppStore] loading 7 repositories from store 2024-06-03T16:08:50.768Z - info: [ui] launching: 3.3.18 (Windows 10.0.19045) 2024-06-03T16:08:50.771Z - info: [ui] execPath: 'C:\Users\First.Last\AppData\Local\GitHubDesktop\app-3.3.18\GitHubDesktop.exe' 2024-06-03T16:08:51.191Z - info: [ui] Stats reported. 2024-06-03T16:08:51.537Z - info: [ui] Executing getRemotes: git remote -v (took 1.008s) 2024-06-03T16:08:53.379Z - info: [ui] Executing getConfigValueInPath: git config -z --local user.email (took 1.864s) 2024-06-03T16:08:53.453Z - info: [ui] Executing getCommits: git log fa109c9ef5a33cb3c2cf98895f12a2e4a191c3e3 --date=raw --max-count=1 -z --format=%H%x00%h%x00%s%x00%b%x00%an <%ae> %ad%x00%cn <%ce> %cd%x00%P%x00%(trailers:unfold,only)%x00%D --no-show-signature --no-color -- (took 1.322s) 2024-06-03T16:08:53.983Z - info: [ui] Executing getCommits: git log fa109c9ef5a33cb3c2cf98895f12a2e4a191c3e3 --date=raw --max-count=1 -z --format=%H%x00%h%x00%s%x00%b%x00%an <%ae> %ad%x00%cn <%ce> %cd%x00%P%x00%(trailers:unfold,only)%x00%D --no-show-signature --no-color -- (took 2.001s) 2024-06-03T16:08:54.725Z - info: [ui] Executing getRemotes: git remote -v (took 1.259s) 2024-06-03T16:08:55.902Z - info: [ui] Executing getRemotes: git remote -v (took 1.895s) 2024-06-03T16:08:56.108Z - info: [ui] Executing getBranches: git for-each-ref --format=%00%(refname)%00%(refname:short)%00%(upstream:short)%00%(objectname)%00%(author)%00%(symref)%00 refs/heads refs/remotes (took 1.382s) 2024-06-03T16:08:56.724Z - info: [ui] Executing getRecentBranches: git log -g --no-abbrev-commit --pretty=oneline HEAD -n 2500 -- (took 1.988s) 2024-06-03T16:08:58.122Z - info: [ui] Executing getSymbolicRef: git symbolic-ref -q refs/remotes/origin/HEAD (took 1.394s) 2024-06-03T16:08:58.222Z - info: [ui] Executing getSymbolicRef: git symbolic-ref -q refs/remotes/origin/HEAD (took 1.265s) 2024-06-03T16:08:59.149Z - info: [ui] Executing getConfigValueInPath: git config -z pull.rebase (took 1.026s) 2024-06-03T16:08:59.776Z - info: [ui] Executing getConfigValueInPath: git config -z pull.rebase (took 1.601s) 2024-06-03T16:09:00.512Z - info: [ui] Executing getAuthorIdentity: git var GIT_AUTHOR_IDENT (took 1.344s) 2024-06-03T16:09:00.708Z - info: [ui] Executing getStashEntries: git log -g -z --format=%gD%x00%H%x00%gs%x00%T%x00%P refs/stash (took 1.549s) 2024-06-03T16:09:00.877Z - info: [ui] Executing getCommits: git log origin/main..main --date=raw --max-count=100 -z --format=%H%x00%h%x00%s%x00%b%x00%an <%ae> %ad%x00%cn <%ce> %cd%x00%P%x00%(trailers:unfold,only)%x00%D --no-show-signature --no-color -- (took 1.727s) 2024-06-03T16:09:00.975Z - info: [ui] Executing getStashEntries: git log -g -z --format=%gD%x00%H%x00%gs%x00%T%x00%P refs/stash (took 1.101s) 2024-06-03T16:09:01.229Z - info: [ui] Executing getCommits: git log origin/main..main --date=raw --max-count=100 -z --format=%H%x00%h%x00%s%x00%b%x00%an <%ae> %ad%x00%cn <%ce> %cd%x00%P%x00%(trailers:unfold,only)%x00%D --no-show-signature --no-color -- (took 1.453s) 2024-06-03T16:09:01.303Z - info: [ui] Executing getAuthorIdentity: git var GIT_AUTHOR_IDENT (took 1.504s) 2024-06-03T16:09:02.053Z - info: [ui] Executing getConfigValueInPath: git config -z --local user.name (took 1.536s) 2024-06-03T16:09:02.599Z - info: [ui] Executing getAllTags: git show-ref --tags -d (took 1.721s) 2024-06-03T16:09:02.663Z - info: [ui] Executing installGlobalLFSFilter: git lfs install --skip-repo (took 11.859s) 2024-06-03T16:09:02.702Z - info: [ui] Executing getAllTags: git show-ref --tags -d (took 1.401s) 2024-06-03T16:09:03.126Z - info: [ui] Executing getConfigValueInPath: git config -z --local user.email (took 1.072s) 2024-06-03T16:09:04.154Z - info: [ui] Executing getCommits: git log HEAD --date=raw --max-count=100 --skip=0 -z --format=%H%x00%h%x00%s%x00%b%x00%an <%ae> %ad%x00%cn <%ce> %cd%x00%P%x00%(trailers:unfold,only)%x00%D --no-show-signature --no-color -- (took 1.554s) 2024-06-03T16:09:05.523Z - info: [ui] Executing getChangesFiles: git log fa109c9ef5a33cb3c2cf98895f12a2e4a191c3e3 -C -M -m -1 --no-show-signature --first-parent --raw --format=format: --numstat -z -- (took 1.367s) 2024-06-03T16:10:59.285Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: Invalid credentials fatal: Authentication failed for 'https://bitbucket.org/company/company-marketing-website.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:11:00.842Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin (took 1.122s) 2024-06-03T16:11:00.843Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/company.com-2023-wordpress-theme.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:11:02.014Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/UserGroups/MachineLearning/Developer/bugatti-tools.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:11:02.983Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/demo-pages-2024.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:11:03.960Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/documentation-portal.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:11:04.070Z - info: [ui] [RepositoryIndicatorUpdater]: Refreshing sidebar indicators for 6 repositories took 6.0s of which 0.0s paused, total 6.0s 2024-06-03T16:26:06.838Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: Invalid credentials fatal: Authentication failed for 'https://bitbucket.org/company/company-marketing-website.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:26:07.941Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/company.com-2023-wordpress-theme.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:26:08.846Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/UserGroups/MachineLearning/Developer/bugatti-tools.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:26:09.669Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/demo-pages-2024.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:26:10.638Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/documentation-portal.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T16:26:10.748Z - info: [ui] [RepositoryIndicatorUpdater]: Refreshing sidebar indicators for 6 repositories took 5.0s of which 0.0s paused, total 5.0s 2024-06-03T16:31:36.141Z - info: [ui] askPassHandler: no account found for gitlab.com 2024-06-03T16:31:37.816Z - info: [ui] askPassHandler: user cancelled generic git authentication 2024-06-03T16:32:51.984Z - info: [ui] Executing push: git -c credential.helper= push origin main:main --progress (took 76.275s) 2024-06-03T16:33:52.259Z - info: [ui] askPassHandler: no account found for gitlab.com 2024-06-03T16:34:00.433Z - info: [ui] askPassHandler: user cancelled generic git authentication 2024-06-03T18:32:12.342Z - info: [ui] Executing push: git -c credential.helper= push origin main:main --progress (took 7100.597s) 2024-06-03T18:32:13.331Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin (took 1.087s) 2024-06-03T18:32:13.331Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: Invalid credentials fatal: Authentication failed for 'https://bitbucket.org/company/company-marketing-website.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:32:14.513Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/company.com-2023-wordpress-theme.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:32:15.190Z - info: [ui] askPassHandler: no account found for gitlab.com 2024-06-03T18:32:15.628Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/UserGroups/MachineLearning/Developer/bugatti-tools.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:32:17.157Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/demo-pages-2024.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:32:18.252Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/documentation-portal.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:32:18.484Z - info: [ui] [RepositoryIndicatorUpdater]: Refreshing sidebar indicators for 6 repositories took 6.4s of which 0.0s paused, total 6.4s 2024-06-03T18:32:18.574Z - info: [ui] askPassHandler: user cancelled generic git authentication 2024-06-03T18:32:24.411Z - info: [ui] Executing push: git -c credential.helper= push origin main:main --progress (took 9.704s) 2024-06-03T18:59:15.088Z - info: [ui] Executing fetch: git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin (took 1.164s) 2024-06-03T18:59:15.089Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: Invalid credentials fatal: Authentication failed for 'https://bitbucket.org/company/company-marketing-website.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:59:16.271Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/UserGroups/MachineLearning/Developer/bugatti-tools.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:59:17.447Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/demo-pages-2024.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:59:18.466Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/documentation-portal.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:59:19.686Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/company.com-2023-wordpress-theme.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T18:59:19.838Z - info: [ui] [RepositoryIndicatorUpdater]: Refreshing sidebar indicators for 6 repositories took 6.1s of which 0.0s paused, total 6.1s 2024-06-03T18:59:19.939Z - info: [ui] askPassHandler: no account found for gitlab.com 2024-06-03T18:59:49.707Z - info: [ui] askPassHandler: acquired generic credentials for gitlab.com 2024-06-03T18:59:49.939Z - info: [ui] Executing push: git -c credential.helper= push origin main:main --progress (took 30.581s) 2024-06-03T19:15:21.969Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: Invalid credentials fatal: Authentication failed for 'https://bitbucket.org/company/company-marketing-website.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T19:15:23.043Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/company.com-2023-wordpress-theme.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T19:15:23.044Z - info: [ui] askPassHandler: auth failed, deleting gitlab.com credential 2024-06-03T19:15:23.900Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/UserGroups/MachineLearning/Developer/bugatti-tools.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T19:15:24.770Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/demo-pages-2024.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T19:15:25.741Z - error: [ui] `git -c credential.helper= fetch --progress --prune --recurse-submodules=on-demand origin` exited with an unexpected code: 128. stderr: remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.com/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://gitlab.com/d3258/marketing/documentation-portal.git/' (The error was parsed as 4: Authentication failed. Some common reasons include: - You are not logged in to your account: see File > Options. - You may need to log out and log back in to refresh your token. - You do not have permission to access this repository. - The repository is archived on GitHub. Check the repository settings to confirm you are still permitted to push commits. - If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. - If you use SSH authentication, ensure the host key verification passes for your repository hosting service. - If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. Check the documentation of your repository hosting service.) 2024-06-03T19:15:25.870Z - info: [ui] [RepositoryIndicatorUpdater]: Refreshing sidebar indicators for 6 repositories took 5.0s of which 0.0s paused, total 5.0s ```

justingolden21 commented 5 months ago

Figured it out. I needed to sign in with my gitlab email and PAT (personal access token). I have no idea why after years of being signed in, github desktop decided to sign me out without mentioning and then show in the UI that I was signed in. The PAT also remained unchanged.