-
Notifications
You must be signed in to change notification settings - Fork 117
[1.0.4] On delete deploy key: Rugged::NetworkError (Early EOF): #418
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
Comments
I have this same on adding new deploy key or user key. Problems has begin after trying to create repository mirror on 1.0.2. |
Does repo creation work? |
Yes, i have this same error on creating repository or adding new project. Two days ago i restore redmine from backup before creating repository mirror and all works good. Today, problem go back on creating new project, without creating repository mirror. |
Be sure that the |
Sorry, i dont know where i should looking for this. |
I'm running into the same issue since I've changed permissions on my projects. I'm seeing an internal server error, as soon as I'm changing a project setting. This is happening for all projects, even if the repository module isn't enabled. The config test looks like, as everything is working. Trying SSH access with the redmine key results in the following output:
I've also tried to remove the checked out version of gitolite-admin in /tmp This is the message I'm seeing in the git_hosting.log as soon as I'm trying to save project settings:
As there is no repository inside the mentioned directory, this will clearly fail. Is there a way to enable some more debugging information? |
The following is missing from my gitolite.conf now:
This might explain, why there is no access possible and the info command won't show any repo, but I don't know, why this line is missing. |
http://gitolite.com/gitolite/emergencies.html#bypass helped me in solving my issue. I've gave the admin key permissions for gitolite-admin and everything is working again. |
But I still think, this error should be catched and a useful message in the log would be good. |
@n-rodriguez: Any update about this issue? My redmine is useless. |
Can you try this :
|
I think you have reused Gitolite admin key as a deployment key. So Gitolite thinks that this is the deployment user who tries to clone the gitolite-admin.git repo and denies access. You must not do that : http://redmine-git-hosting.io/get_started/#step-10-add-your-ssh-keys. Check Gitolite logs in |
Had the same issue as @saz, had to use the same trick. I'm not sure what was the problem, but on the config test page I saw only testing repo. |
You may have reused Gitolite admin key as a deployment key or a user key. You must not do that : http://redmine-git-hosting.io/get_started/#step-10-add-your-ssh-keys. |
It might be prudent to add a link to http://stackoverflow.com/questions/2419566/best-way-to-use-multiple-ssh-private-keys-on-one-client#2419609 on your instructions page http://redmine-git-hosting.io/get_started/#step-10-add-your-ssh-keys. |
@wilsoc5 : I don't think so. This part is handled by the plugin. You should not do that. |
This is when i trying to remove any deploy key:
The text was updated successfully, but these errors were encountered: