Personal Access Tokens - Authentication Failed #39513
Replies: 2 comments
-
In my experience that message appears when whatever you enter when Git asks for your password isn't a token (missing permissions are different). It's hard to say remotely why that might be, but I'd check for any stored credentials, double-check how you're entering the token, and if it's correct wherever you store it (e.g. your password manager). If you're looking for a workaround, you can try using SSH instead of HTTPS to access your repositories. Note that after setting up your keys you'll have to update the remote repository URL to make Git actually use SSH. |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Token Authentication suddenly stopped working. It worked yesterday with a commit/push. Today I created a new branch and tried pushing to that branch but it keeps failing authentication (image attached).
I've checked to make sure it's not a copy/paste issue.
I've deleted all tokens and made new ones with all permissions.
I've read through the majority of discussion threads and attempted the various solutions suggested but nothing is working.
Any help is greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions