question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

cannot change token to authenticate to custom Git server

See original GitHub issue

Search existing issues

  • I have searched the issue tracker and confirmed that I was unable to find existing issues for the problem I am experiencing.

The problem

When setting up github desktop for the first time, I tried to clone an https repository that I self-host. Github desktop asked for the password, but I entered it incorrectly. When trying to clone it, even to another folder, it endlessly keeps hanging forever. I do not see anywhere an option to change the https access credentials.

Plus, the github desktop client itself just keeps ‘loading’ endlessly and does not provide feedback on why it is failing (e.g. in this case it would be https authentication)

I can confirm I can clone the repository from the normal git client thru https, with http authentication.

Release version

Version 2.9.6-linux1 (x64)

Operating system

Arch Linux 5.17.1-zen1-1-zen DWM

Steps to reproduce the behavior

  1. Get a git remote url repo with an https link.
  2. purposefully enter the ‘wrong’ credentials into the authentication prompt.
  3. try cloning again, does it work ?
  4. try changing the auth user/password.

Log files

edit: log files are indeed created, just not show in my file manager. the log file is in another comment

No log files are created by Github Desktop, even when clicking on Help -> Show logs

Screenshots

No response

Additional context

I understand that github implements the http transport without authentication when cloning repositories, making it unnecessary to provide access credentials. But it seems a little redundant to not provide these if I were to have an https server that does require them.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:12 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
fanninpmcommented, Apr 5, 2022

KWallet talked about support years ago but it never eventuated

There has been progress, but it has been slow.

0reactions
shiftkeycommented, Jun 25, 2022

Closing this out as I don’t think I have anything else to add about the credential store issue that’s the root cause here.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Authenticate with GitHub using a token - Stack Overflow
I am trying to authenticate with GitHub using a personal access token. In the help files at GitHub, it states to use the...
Read more >
Automatic token authentication - GitHub Docs
GitHub provides a token that you can use to authenticate on behalf of ... The token's permissions are limited to the repository that...
Read more >
Token authentication requirements for Git operations
Beginning August 13th, 2021, we will no longer accept account passwords when authenticating Git operations on GitHub.com.
Read more >
Personal access tokens - GitLab Docs
Documentation for GitLab Community Edition, GitLab Enterprise Edition, Omnibus GitLab, and GitLab Runner.
Read more >
Setting up and testing a Git connection | Looker - Google Cloud
To change the Git setup for an existing project, select Reset Git Connection in the project configuration section. Resetting your Git connection will...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found