-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Gitea refuses SSH connections when using valid public keys #12667
Comments
Without logs we cannot assess further. We need the logs from the running gitea server. |
This was done on try.gitea.io. I can send you mine, but I don't see much on there, tbh. |
This is all I get. These are 2 tries to do a
|
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Aug 31, 2020
go-gitea#12624 missed lowering the provided repoPath. (Additionally make a few fixes to the way the debug flag works.) Fix go-gitea#12659 Fix go-gitea#12667 Signed-off-by: Andrew Thornton <[email protected]>
zeripath
added a commit
that referenced
this issue
Aug 31, 2020
#12624 missed lowering the provided repoPath. (Additionally make a few fixes to the way the debug flag works.) Fix #12659 Fix #12667 Signed-off-by: Andrew Thornton <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[x]
):Description
Commits afd89b1 (and 58f57b3) have an issue where all public SSH keys are rejected. This does not happen with commit f8601f3. I have been able to test this on try.gitea.io, and this is the error I get:
The repository does exist and the public SSH key is valid.
Screenshots
The text was updated successfully, but these errors were encountered: