Unable to authorize GitHub password (Unathorized/Not Found)

[flyingduck92]

I already put an alias for hub on my
.bashrc
alias git=hub

But when I want to create a repos my credentials always failed

Command attempted:
git create jam_hub
github.com username: flyingduck92
github.com password for flyingduck92 (never stored):

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

[amichaelc]

I had the same issue. I went to the github tokens link provided and made a token, and now it works.

[mislav]

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.

[flyingduck92]

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) and paste it instead of the password.

Oh okay, I will try usng Personal Access Token then.
Cheers sir

[dominguespt]

Hello, I uninstalled hub gem and did the update wit Homebrew

[JavaProScript]

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.

[ketankshukla]

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!

[carlosloureda]

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.

Thanks @mislav. That worked for me!

[alk-gmathews]

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.

[leo60228]

Why was this issue closed? This seems like a pretty major issue.

[mislav]

True— it's not solved yet, so I'm reopening.

[bharath-123]

@mislav Can we change the intimation message until this is fixed? Something like github.com token for <user>: rather than github.com password for <user>: ? I think the message is fairly confusing.

[leonardodimarchi]

Is there a way to change the message, just like @bharath-123 said ?

@mislav Can we change the intimation message until this is fixed? Something like github.com token for <user>: rather than github.com password for <user>: ? I think the message is fairly confusing.

I was hoping that we could save the token somewhere too, is that possible ?

Edit: Found this on Hub Configurations

Hub will prompt for GitHub username & password the first time it needs to access the API and exchange it for an OAuth token, which it saves in ~/.config/hub.

To avoid being prompted, use GITHUB_USER and GITHUB_PASSWORD environment variables.

Alternatively, you may provide GITHUB_TOKEN, an access token with repo permissions. This will not be written to ~/.config/hub.

[leonardodimarchi]

Repo successful created with the token, but when i try to git push origin master, i get git@github: permission-denied.

[jamiecropley]

Repo successful created with the token, but when i try to git push origin master, i get git@github: permission-denied.

if your trying to push with git could most likely be a setting there. Do you have it set up for https or ssh?

[leo60228]

Since it doesn't seem to have been posted here, GitHub added an OAuth flow that doesn't need a web browser/server: https://docs.github.com/en/developers/apps/authorizing-oauth-apps#device-flow

[jamiecropley]

Since it doesn't seem to have been posted here, GitHub added an OAuth flow that doesn't need a web browser/server: https://docs.github.com/en/developers/apps/authorizing-oauth-apps#device-flow

I just always do SSH as I know how to get it working, however I ended up here as I completely forgot about the token thing, they really need to update the word password to token really.

[nelsonov]

Why did Git do something that would break a common workflow without first providing a fix for that workflow? Sounds a lot like something Microsoft would do...

[leonardodimarchi]

Repo successful created with the token, but when i try to git push origin master, i get git@github: permission-denied.

if your trying to push with git could most likely be a setting there. Do you have it set up for https or ssh?

I'm using https

[shubhampathak09]

I am facing a similar issue, in past whenever i did git push origin master on the new repo using git bash, it prompted me with a username and password screen, where in pwd i used to enter PAT, and things would just work fine. But this time gitbash is not prompting me with username and password.

[Overdozed]

i has to change url to https inside .git/config in order to get it up and running
[remote "origin"]
url = https://github.com/...

[fuji246]

Access Token stops working...

[davidblum]

I was able to get this working by generating a PAT per the linked docs, and then setting up a hub config file in: ~/.config/hub:

github.com:
- user: < user_name >
  oauth_token: < PAT >
  protocol: https

[ystraore]

I am trying to push a file in Github. I was able to pass in my username, but unable to put my token password. I did not see the little window that asks for my password I just see a little key picture. I will appreciate if someone can help me with that.

[pcobos]

This wasted me some time so I want to write down the solutions. If you have time to switch to gh, do it, otherwise:

• Generate PAT (with repo scope)
• Create a ~/.config/hub file like below (per mislav's comment). Put in your username as user and paste your PAT on oauth_token.

  github.com:
   - user: mislav
     oauth_token: PASTE_YOUR_TOKEN_HERE
     protocol: https
  

• Try hub clone

I tried this but I am getting the following error

.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/hub-1.12.4/lib/hub/github_api.rb:511:in block in yaml_load': undefined method []=' for nil:NilClass (NoMethodError)

I tried reinstalling the gem to no avail, any suggestions?

[mislav]

@pcobos You seem to be using the hub Ruby gem, which last had a release in 2014 and was since rewritten in Go and released through this project's Releases page. You should upgrade!

[tomoat]

Use gh instead of hub, https://github.com/cli/cli

> brew install gh
> gh auth login
> gh repo create 

[gambas-maker]

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)

Do you have an idea ?

[Betristor]

They really not?

[timmattison]

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.

[aamruth]

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

[NdagiStanley]

Using the PAT (Personal Access Token) with repo scope as the password works for me.

[TimCookXXX]

Извините за неудобства. 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

[Klairm]

Using the PAT (Personal Access Token) with repo scope as the password works for me.

I'm trying to use a token for password but it doesn't work for me

[nh2]

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?