-
Notifications
You must be signed in to change notification settings - Fork 9
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
Cloning a repo - http doesn't work, ssh key neither #8
Comments
After more tests: using a no-password ssh key doesn't work. |
Hi, |
Right. I was thinking it might be integrated, asking for login/pwd for instance, and I wanted to be sure it wasn't a bug on my side.
(feeling stupid) I missed it (I don't know how ^^), thanks !
It's the right command. |
Up :)
So is it the right configuration for the ssh daemon ? |
I just tried to connect via ssh, by forcing publickey authentication, I just have this result: I also tried by using the ssh key I use to log as root (an not for gogs, normally) - it works. |
Sorry for the response time.
|
I did before, the key was always the right one
I will check ASAP. |
You can also check
If not, put ssh in verbose mode (-vvvv) to see what happen when also monitoring auth.log. |
I think I had that message before with my gogs ssh key. Now it asks for the password corresponding to the root ssh key that I used for the test (as the gogs key wasn't working). I have it aside my gogs key. Removing the root key, while keeping the gogs key, ask only for gogs account password (and not the ssh key). |
Here is my full sshd_config : https://paste.yunohost.org/atedejuwag.vala if you want to check what's different. |
Thanks :) Well, the only differences I see are:
on my side, and you have the option no,
I don't have this line.
I have yes on my side. |
The first two won't change the behavior Have you tried to change UsePAM to no and restart the ssh daemon ? |
Done, no visible effect. |
Well to investigate more I would need the full exchange of the auth.log with the content of the gogs authorized_keys. If you're uncomfortable about exposing it here (even if it's only public keys) you can mail me here: github@max.privy.place |
Should I remove the root key before trying this and sending you the auth.log ? Should I try adding the gogs key to the root user authorized_keys file ? |
Ok I found the issue - it's not related to gogs: my ssh-agent had an issue, all the keys I generated since a previous update where not added with ssh-add (seems to be a know bug, updating solved the issue). |
I'm glad you make it work. As I said in my previous answer, since gogs worked, the solution had to be in the key exchange either in the daemon or in you ssh agent. |
And you were right, but I wasn't expecting this kind of issue, since the keys were generated and ssh-add was working (btw it reported nothing). |
Hi @mbugeia ,
despite the issue being closed, I took quite a long time to understand that git through https does not work when website is private, until I reached this thread. Shouldn't this limitation be mentioned during install, just beside the option "Make this website public" ? |
Hi,
I'm trying to clone my gogs repository.
Using http I have this kind of error:
fatal: mydomain.tld/gogs/myself/Test.git/info/refs not valid: is this a git repository?
And when trying using ssh, it ask for a password - but I can't find which one, as my login password doesn't work.
Adding an ssh key to the repo doesn't solve the issue.
Do you know how to correct that ? Is it an installation issue ?
Thanks :)
The text was updated successfully, but these errors were encountered: