Password denied from Github

812 views
Skip to first unread message

too...@gmail.com

unread,
Feb 27, 2021, 11:57:47 AM2/27/21
to tortoisegit-users
Hello everybody,
did install TortoiseGit. Guess there is something in choosing the right settings.
In case of security I was ask if I wanted the "Default" settings or SSH. I did choose Default.
When I login on website of Github, my password is accepted. 
If I try to push changes to Github with TortoiseGit the password is denied.
 I did already even change my password, this did not change anything.
How can I solve? Please help.
Regards, Thomas

Sven Strickroth

unread,
Mar 2, 2021, 3:57:57 AM3/2/21
to tortoise...@googlegroups.com, too...@gmail.com
Hi Thomas,

Am 27.02.2021 um 17:57 schrieb too...@gmail.com:
> Hello everybody,
> did install TortoiseGit. Guess there is something in choosing the right
> settings.
> In case of security I was ask if I wanted the "Default" settings or SSH.
> I did choose Default.
> When I login on website of Github, my password is accepted.
> If I try to push changes to Github with TortoiseGit the password is denied.
>  I did already even change my password, this did not change anything.

Are you using HTTPS or SSH? - For HTTPS you need a special perosnal
token, see
<https://docs.github.com/en/github/using-git/why-is-git-always-asking-for-my-password>.

If you use SSH you might need to use the passphrase of your key instead
of of your GitHub password. SSH with GitHub username/password does not work.

--
Best regards,
Sven Strickroth
PGP key id F5A9D4C4 @ any key-server

too...@gmail.com

unread,
Mar 2, 2021, 4:21:01 AM3/2/21
to tortoisegit-users
Hello Sven,

thanks for your answer, nice help from you.

I believe the core problem ist the understanding of the difference
of the options in install dialog. As I wrote the dialog says:

"Do you want a) Default security settings OR b) SSH"

Sorry, I can't remember exactly from mind, what the text was.
As I did choose "Default security settings" I guess it is NOT SSH.
If someone would have told me that SSH is the better/more easy 
setting I would have choosen that.

Additionally I don't know, if the 2F authentication does prohibit 
a single password login. On website github I can login without 
problems. Pushing to my existing repository with TortoiseGit 
the error message says, my password would be wrong. This 
cannot be because of login with it on the website is possible.

Thanks for the link, I will read it.

regards, Thomas

On Tuesday, March 2, 2021 at 9:57:57 AM UTC+1 Sven Strickroth wrote:
Hi Thomas,

Sven Strickroth

unread,
Mar 2, 2021, 4:43:52 AM3/2/21
to tortoise...@googlegroups.com, too...@gmail.com
Hello Thomas,

Am 02.03.2021 um 10:21 schrieb too...@gmail.com:
> "Do you want a) Default security settings OR b) SSH"

The TortoiseGit installation wizard asks whether to use TortoiseGitPlink
(default and recommended for TGit) or OpenSSH. This is just regarding
the technology to use for SSH connections. That does not say that you
cannot use HTTPS or even the git protocol - that is independent. OpenSSH
and TortoieGitPlink have both advantages and disavantages. Even if you
have chosen one technology, you can easily change in in TortoiseGit
network settings.

> Additionally I don't know, if the 2F authentication does prohibit
> a single password login. On website github I can login without
> problems. Pushing to my existing repository with TortoiseGit
> the error message says, my password would be wrong. This
> cannot be because of login with it on the website is possible.

Again, for username/password login you need to use a personal access token:

*
<https://docs.github.com/en/github/authenticating-to-github/accessing-github-using-two-factor-authentication>
*
<https://docs.github.com/en/github/using-git/why-is-git-always-asking-for-my-password>

too...@gmail.com

unread,
Mar 6, 2021, 2:47:52 AM3/6/21
to tortoisegit-users
Hello Sven,

thanks again for your help.
I've tried the first link. I've stumbled upon this section:

Using two-factor authentication with the command line  

> After you've enabled 2FA, you must use a personal access token or SSH key instead of your password when accessing GitHub on the command line.

Authenticating on the command line using HTTPS

> After you've enabled 2FA, you must create a personal access token to use as a password when authenticating to GitHub on the command line using HTTPS URLs.

>When prompted for a username and password on the command line, use your GitHub username and personal access token. The command line prompt won't specify that you should enter your personal access token when it asks for your password.


This is not "possible to me. What does mean a "personal access token"?
I've choosen SMS. But it could not be, I should use every time this one SMS-code I've received, could it be?
This is my actual position.

To give a better overview what I've done I will describe.

I've read some manuals:

done.
Then because of the error:

done.
Then:

done.

Now if I try to push the changes to my repository there comes a GUI-dialog (Windows)
with the request of my user name or email and pw.
I've tried the user name as well as the email and also did combine 
it with pw of account and pw of key.
Nothing works.
So I'm in the wild. :-\

Thanks again for your help and have a nice weekend, Thomas

On Tuesday, March 2, 2021 at 10:43:52 AM UTC+1 Sven Strickroth wrote:
Hello Thomas,

> Additionally I don't know, if the 2F authentication does prohibit
> a single password login. On website github I can login without
> problems. Pushing to my existing repository with TortoiseGit
> the error message says, my password would be wrong. This
> cannot be because of login with it on the website is possible.

Again, for username/password login you need to use a personal access token:

*
<https://docs.github.com/en/github/authenticating-to-github/accessing-github-using-two-factor-authentication>
*
<https://docs.github.com/en/github/using-git/why-is-git-always-asking-for-my-password>
--
Sven Strickroth

Sven Strickroth

unread,
Mar 7, 2021, 6:09:25 AM3/7/21
to tortoise...@googlegroups.com, too...@gmail.com
Hallo Thomas,

first, please decide on what you want to use SSH or HTTPs.

For HTTPs everything is described here:
Authenticating on the command line using HTTPS:
<https://docs.github.com/en/github/authenticating-to-github/accessing-github-using-two-factor-authentication#authenticating-on-the-command-line-using-https>

on that page there is a link on how to get a personal access token (it
is not the SMS code):
<https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token>
> Now if I try to push the changes to my repository there comes a > GUI-dialog (Windows)
That is the password dialog for HTTPs authentication. here use your
GitHub username and as personal access token as password.

too...@gmail.com

unread,
Mar 10, 2021, 3:03:08 AM3/10/21
to tortoisegit-users
Hello Sven. Thank you much for your help. I want to let you know
that I appreciate that.

Now after all I am very irritated and to say my feelings, I feel like
completely in the wild.
I'm frustrated that there is not ONE single page for either
- use Plink
- use SSH
- use what else

You gave me the hint to look for personal access token.
I looked over there but what they told did sound crude to me. Why should I
tell detailed what I want to use of the parts if I am the owner?
To be honest, I did not have the smallest idea what they did want from me.
Next part is that my English isn't that perfect. I am many times
in doubt if I did understand right. May be this is because I'm
native German speaker. Sure there are every time in English some
misunderstandings.
Seems I have to search for a good guy speaking German. But I did
already, found none.

Because I did not know what to do I decided to start a new and did
uninstall TortoiseGit.
I installed it a new. I did hear many people in the past talking about SSH.
So I decided to try if this is less painfull.
I will try it and make a complete list of all my steps with screenshots.
Maybe this will lead me to the point of error.

Many thanks to you.
Have a nice evening. Thomas
Reply all
Reply to author
Forward
0 new messages