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
Git ssh access does not work. When ENABLE_GZIP = true, http doesn't work too. #412
Comments
Could you show your git version? And run user has the access to run git. |
|
About git over ssh not working: I tried with git 2.1.0 and git 2.0.4. With gogs 0.4.5.0704 Alpha it worked fine. I backed up my old installation so I can confirm that this is still the case. When I restore the old version clone/pull/push over ssh work. For 0.4.9.0831 Beta I did two clean installations on two different systems and the problem exists on both systems. I use sqlite3 as my database if this makes any sense. |
What is your system? |
I am on Gentoo. I removed all go sources ( |
I'm not sure, but there was some dependency changes on yesterday, glad works now! |
Keep open for reminding to disable |
Thanks and sorry for the false alarm. |
This has been fixed! Please update all deps, especially |
I also get errors like |
@pilt If you set |
I reverted to v0.5.2 for now. Let me know if I can help. We install the binary distribution at gobuild.io and run Ubuntu 14.04. |
With the current master branch [0.4.9.0831 Beta] I can not access my repositories through ssh.
The git commands (clone, push, etc) just hang, waiting for a response from gogs.
If I use a wrong name for a repository, gogs informs me that given repository does not exist and
closes the connection as expected.
When I use the correct name, it hangs. If I kill the git command with ctrl+c, then the following line is appended to
log/serv.log
:Also when I enable the option
ENABLE_GZIP
inconf/app.ini
then it is no longer possible to access the repositories through http/https.In this case the error doesn't come from gogs but from the git command and is:
The text was updated successfully, but these errors were encountered: