-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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: Internal Error" when using git clone SSH #15785
Comments
need ssh error log, you can get it by set |
Thanks. I will get the log again. |
I changed
I seem to know the problem. |
I set |
a1012112796
added a commit
to a1012112796/gitea
that referenced
this issue
May 8, 2021
as title, when a ssh error ocure like go-gitea#15785. only when switch ``RUN_MODE`` to dev can we found which error is ocure. But this way is not a good idea for production envirment. this changes try save ssh error mesage to the log file like other log by a new internal hook. I think it's usefull for find error message in production envirment. Thanks. Signed-off-by: a1012112796 <[email protected]>
techknowlogick
added a commit
that referenced
this issue
May 21, 2021
* add a new internal hook to save ssh log as title, when a ssh error ocure like #15785. only when switch ``RUN_MODE`` to dev can we found which error is ocure. But this way is not a good idea for production envirment. this changes try save ssh error mesage to the log file like other log by a new internal hook. I think it's usefull for find error message in production envirment. Thanks. Signed-off-by: a1012112796 <[email protected]> * rename and fix nit * Update modules/private/hook.go Co-authored-by: silverwind <[email protected]> Co-authored-by: techknowlogick <[email protected]> Co-authored-by: silverwind <[email protected]> Co-authored-by: techknowlogick <[email protected]>
AbdulrhmnGhanem
pushed a commit
to kitspace/gitea
that referenced
this issue
Aug 10, 2021
* add a new internal hook to save ssh log as title, when a ssh error ocure like go-gitea#15785. only when switch ``RUN_MODE`` to dev can we found which error is ocure. But this way is not a good idea for production envirment. this changes try save ssh error mesage to the log file like other log by a new internal hook. I think it's usefull for find error message in production envirment. Thanks. Signed-off-by: a1012112796 <[email protected]> * rename and fix nit * Update modules/private/hook.go Co-authored-by: silverwind <[email protected]> Co-authored-by: techknowlogick <[email protected]> Co-authored-by: silverwind <[email protected]> Co-authored-by: techknowlogick <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[x]
):Description
When I use
git clone
and use SSH authentication, git will promptGitea: Internal Error
, git output:ssh -T gitea @ $ {git_host}
output:I don't know where I have a problem, try.gitea.io everything is normal.
If you like, you can use Chinese to communicate with me.
The text was updated successfully, but these errors were encountered: