You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unable to authorize GitHub password (Unathorized/Not Found) #2655
What happened:
Error creating repository: Unauthorized (HTTP 401)
Bad credentials. The API can't be accessed using username/password authentication. Please create a personal access token to access this endpoint: http://github.com/settings/tokens
More info:
git version 2.29.1.windows.1
hub version 2.14.2
I'm sorry for the inconvenience. GitHub deprecated its Authorizations API, which hub relied on for exchanging a password for a token.
Until we fix this in hub, the solution is to generate a Personal Access Token (with at least repo scope) at https://github.com/settings/tokens and paste it instead of the password.
Reacted by Takuya Endo, Kelz, Kohei🔧, Elia Pari, Matthew Reishus, Dan Allen, Ketan Shukla, Carlos Loureda, Brandin, Jiri Zajic and 134 more
Reacted by Francesco 'makevoid' Canessa, Celina Rabe, MorganJ, Mark Campbell, Amirsalar Sojoudi, Kishan Sindhi, Tosyn, Greg Lavallee, SametHope, Dan Andrews and 1 more
Reacted by Jack Mason
Reacted by Ketan Shukla, Anders Hafreager, Abolaji Femi, Matheus, Omer Ozarslan, Takashi Masuda, Tyler Brewer, João Melo, Raymond Rutjes, Adriano Cahete and 18 more
changed the title [-]hub failed to gives access after inserting username and password[/-][+]Unable to authorize with my GitHub password (Unathorized/Not Found)[/+]on Dec 15, 2020
I'm sorry for the inconvenience. GitHub deprecated its Authorizations API, which hub relied on for exchanging a password for a token.
Until we fix this in hub, the solution is to generate a Personal Access Token (with at least repo scope) at https://github.com/settings/tokens and paste it instead of the password.
This didn't fix it for me. Error stays the same. I will try to find a fix.
Reacted by Matt Evans, tomasyany, sharmadivyam102, Matin Taherzadeh, Jorge Torija Zane, Nikita Bandarevich, Cornchips007, Rachel-at-ule, Steffen Zeile, LimeCida and 6 more
I'm sorry for the inconvenience. GitHub deprecated its Authorizations API, which hub relied on for exchanging a password for a token.
Until we fix this in hub, the solution is to generate a Personal Access Token (with at least repo scope) at https://github.com/settings/tokens and paste it instead of the password.
You have NO idea how much I searched the internet to find this solution! THANK YOU!
Reacted by PatelBharat28, Martin Fabian, Johnny Lai, Jaga Santagostino, Sekti and SametHope
I'm sorry for the inconvenience. GitHub deprecated its Authorizations API, which hub relied on for exchanging a password for a token.
Until we fix this in hub, the solution is to generate a Personal Access Token (with at least repo scope) at https://github.com/settings/tokens and paste it instead of the password.
I'm sorry for the inconvenience. GitHub deprecated its Authorizations API, which hub relied on for exchanging a password for a token.
Until we fix this in hub, the solution is to generate a Personal Access Token (with at least repo scope) at https://github.com/settings/tokens and paste it instead of the password.
This information should be in the readme, and not in an issue.
Reacted by Carlos Loureda, Ollie Charles, Michael Brown, Stein Martin Hustad, Allan Leander Rostock Hansen, Nic Wanavit, FergusFettes, Jeffrey Lotthammer, Dennis Gosnell, Peter Monks and 39 more
Hello, I'ma facing this issue, I removed ~/.config/hub then I did hub create
But now I'm having this error :
Error creating repository: Not Found (HTTP 404)
Please, please, please get rid of this tool if it is no longer supported. I just wasted 30 minutes trying to get a previously working setup up and running and ended up here at the bottom of this rabbit hole.
It is fine if the tool needs a token, it is fine if the tool is discontinued, but do your best to surface this to users running the latest version as fast as possible.
If the tool is to continue to be available my suggestions are below.
Not found could be replaced with:
Not found. Are you trying to use a username and password?
Until we fix this in hub, the solution is to generate a Personal Access Token (with at least repo scope) at https://github.com/settings/tokens and paste it instead of the password.
And when it says this:
Error fetching pull requests: Unauthorized (HTTP 401)
Bad credentials
It would be better to say:
Error fetching pull requests: Unauthorized (HTTP 401)
Bad credentials
Try clearing out your ~/.config/hub file. Your next attempt to connect with request that you reauthorize.
Reacted by Ivan Greene, Alexander Mangel, Shlomo, Niklas Hambüchen, Sekti, Aaron Conway, Justin Keogh and Patrick
Извините за неудобства. GitHub устарел от своего API авторизации, на который хаб полагался при обмене пароля на токен.
Пока мы не исправим это в хабе, решение состоит в том, чтобы сгенерировать токен личного доступа (по крайней мере, с repoобластью действия) на https://github.com/settings/tokens и вставить его вместо пароля.
It works, thanks!
But if you didn't select 'Repo' when creating the key, then you get the following error: Error creating repository: Unauthorized (HTTP 401) Bad credentials
You need to delete the ~/.config/hub directory and re-authorize on github.com and everything should work fine. rm -rf ~/.config/hub
And after that, authorize again by entering your login and the key that you previously created: hub create
I just wasted 30 minutes trying to get a previously working setup up and running and ended up here at the bottom of this rabbit hole.
It is fine if the tool needs a token, it is fine if the tool is discontinued, but do your best to surface this to users running the latest version as fast as possible.
Same here.
@mislav Could you please make the tool emit an error, instead prompting for username and password and saying Not Found, when it's known that this cannot currently work?
Reacted by dziewannak, Barnaby Gray and Brent Matzelle
changed the title [-]Unable to authorize with my GitHub password (Unathorized/Not Found)[/-][+]Unable to authorize GitHub password (Unathorized/Not Found)[/+]on Mar 14, 2024
Activity
amichaelc commentedon Nov 29, 2020
I had the same issue. I went to the github tokens link provided and made a token, and now it works.
mislav commentedon Nov 30, 2020
I'm sorry for the inconvenience. GitHub deprecated its Authorizations API, which hub relied on for exchanging a password for a token.
Until we fix this in hub, the solution is to generate a Personal Access Token (with at least
reposcope) at https://github.com/settings/tokens and paste it instead of the password.flyingduck92 commentedon Dec 1, 2020
Oh okay, I will try usng Personal Access Token then.
Cheers sir
dominguespt commentedon Dec 8, 2020
Hello, I uninstalled hub gem and did the update wit Homebrew
[-]hub failed to gives access after inserting username and password[/-][+]Unable to authorize with my GitHub password (Unathorized/Not Found)[/+]JavaProScript commentedon Dec 19, 2020
This didn't fix it for me. Error stays the same. I will try to find a fix.
ketankshukla commentedon Jan 15, 2021
You have NO idea how much I searched the internet to find this solution! THANK YOU!
carlosloureda commentedon Jan 16, 2021
Thanks @mislav. That worked for me!
alk-gmathews commentedon Feb 4, 2021
This information should be in the readme, and not in an issue.
leo60228 commentedon Feb 8, 2021
Why was this issue closed? This seems like a pretty major issue.
mislav commentedon Feb 19, 2021
True— it's not solved yet, so I'm reopening.
29 remaining items
gambas-maker commentedon Jan 18, 2022
Hello, I'ma facing this issue, I removed ~/.config/hub then I did
hub createBut now I'm having this error :
Error creating repository: Not Found (HTTP 404)
Do you have an idea ?
Betristor commentedon Mar 3, 2022
They really not?
timmattison commentedon Mar 18, 2022
Please, please, please get rid of this tool if it is no longer supported. I just wasted 30 minutes trying to get a previously working setup up and running and ended up here at the bottom of this rabbit hole.
It is fine if the tool needs a token, it is fine if the tool is discontinued, but do your best to surface this to users running the latest version as fast as possible.
If the tool is to continue to be available my suggestions are below.
Not foundcould be replaced with:And when it says this:
It would be better to say:
Ask for a token, not a password
Drop `hub` and just use GitHub CLI
aamruth commentedon Aug 5, 2022
git:(master) hub create
github.com username: blabla
github.com password for blabla (never stored):
Error creating repository: Not Found (HTTP 404)
Tired using the token too, still got the same error
Switch from hub to gh
NdagiStanley commentedon Oct 11, 2022
Using the PAT (Personal Access Token) with
reposcope as the password works for me.TimCookXXX commentedon Nov 15, 2022
It works, thanks!
But if you didn't select 'Repo' when creating the key, then you get the following error:
Error creating repository: Unauthorized (HTTP 401) Bad credentialsYou need to delete the ~/.config/hub directory and re-authorize on github.com and everything should work fine.
rm -rf ~/.config/hubAnd after that, authorize again by entering your login and the key that you previously created:
hub createKlairm commentedon May 7, 2023
I'm trying to use a token for password but it doesn't work for me
docs: Drop hub command from the RELEASE.md
docs: Drop hub command from the RELEASE.md (#585)
nh2 commentedon Nov 5, 2023
Same here.
@mislav Could you please make the tool emit an error, instead prompting for username and password and saying
Not Found, when it's known that this cannot currently work?Replace `hub` by `gh`.
[-]Unable to authorize with my GitHub password (Unathorized/Not Found)[/-][+]Unable to authorize GitHub password (Unathorized/Not Found)[/+]