Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requesting authentication & failing when trying to clone from Gitlab. #11185

Closed
LordMilitus opened this issue Dec 5, 2020 · 12 comments
Closed

Comments

@LordMilitus
Copy link

When I attempt to clone anything from GitLab into GitHub Desktop, it tells me my authentification isn't working and I get the following image (see attachment). This was an issue on my old laptop too, I had to use my friends laptop. I have moved countries now and can no longer do this. I have attempted a common log-out and log-in fix, but it did not work for me as it requires you to log in through browser now.

This is a clean install on a machine it has never been on before. I work on a team so I cannot make my own GitLab either, so cloning really has to work here.
d34c9881c07049a91b5992876e785243

Desktop Version 2.6.0
Windows 10

@LordMilitus
Copy link
Author

I got this now after I kept trying.

6f6935762e2cbf1e1f9ebbf7d619d797

@steveward
Copy link
Member

@LordMilitus please follow the instructions here that walk through authenticating with GitLab:

https://github.com/desktop/desktop/blob/development/docs/integrations/gitlab.md

Let me know if you run into any problems.

@LordMilitus
Copy link
Author

@LordMilitus please follow the instructions here that walk through authenticating with GitLab:

https://github.com/desktop/desktop/blob/development/docs/integrations/gitlab.md

Let me know if you run into any problems.

I didn't even get to that screen now to attempt it. I now have the error I showed in the comment above yours.

Ontop of this, I had a token previously and had been able to access the GitLab on another laptop roughly half a year ago.

@steveward
Copy link
Member

@LordMilitus I would try opening Credential Manager and deleting the existing GitLab credential that GitHub Desktop stores there. Once you do that try authenticating again to see if that succeeds. If that does not get things working please share the log file from GitHub Desktop. To access the log files go to the file menu in GitHub Desktop and select Help > Show Logs.
The log files are created daily -- please upload a log file as an attachment from a day where you experienced the issue.

@steveward steveward added the more-info-needed The submitter needs to provide more information about the issue label Dec 7, 2020
@LordMilitus
Copy link
Author

@steveward Hey again and thanks for the reply,

I can't seem to find the Credential Manager in either Desktop or GitLab. Do you mean in GitLab under 'Active personal access tokens (1)' ? I've gone ahead and gotten the logs already just incase. The one dated 5th should be prior to my new issue as well.

2020-12-05.desktop.production.log
2020-12-07.desktop.production.log

@no-response no-response bot removed the more-info-needed The submitter needs to provide more information about the issue label Dec 7, 2020
@no-response no-response bot reopened this Dec 7, 2020
@steveward
Copy link
Member

@LordMilitus you can see how to access the credential manager here:

https://support.microsoft.com/en-us/windows/accessing-credential-manager-1b5c916a-6a16-889f-8581-fc16e8165ac0

There should be an entry under Windows Credentials that has your GitLab token that is stored by GitHub Desktop. Try deleting that and then generating a new token via the steps in the help document I shared. Let me know if that does not get things working.

@steveward steveward added the more-info-needed The submitter needs to provide more information about the issue label Dec 7, 2020
@LordMilitus
Copy link
Author

@steveward

I did that and it still has the new error of Clone Failed: URL returned error: 404

@no-response no-response bot removed the more-info-needed The submitter needs to provide more information about the issue label Dec 7, 2020
@steveward
Copy link
Member

A 404 error indicates that the URL cannot be found. Are you seeing that error or this one still?

fatal: unable to access 'https://gitlab.com/Zapdude/mod.git/': The requested URL returned error: 400

That's a different error than a 404. If you're having specific issues accessing your GitLab repository you may need to reach out to GitLab support for assistance.

@LordMilitus
Copy link
Author

I meant 400, I'm just so used to memes about 404, my bad! I'll try that and then return to this. Thanks.

@LordMilitus
Copy link
Author

Still haven't gotten a reply. Do you think making a new account would fix this? It's a bit of a last resort but..

@LordMilitus
Copy link
Author

It SEEMS to work now! The 400 error disappeared on it's own and the steps provided above worked!

@steveward
Copy link
Member

I'm glad to hear things are working now! I'm going to close this out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants