-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Wrong SSH clone URL #3925
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
The url seems fine. Gitea handles the mapping between the url and the actual location of the repository. |
Yep, see this gist please: https://gist.github.com/youwontguess/7df4e19490ac53d589f8cf6b8fd789f6 |
I think this could be related to this one: #3848. Especially this comment #3848 (comment) Please try:
from Admin Panel EDIT 1: Another possibility is that you are missing permission to access that repository. EDIT 2: Maybe your git users lacks a login shell? |
pre-receive and update seem to be populated with the default content, if I'm not mistaken (/user/repo/settings/hooks/git) |
Did not see your edits.
|
@youwontguess Can you provide the log entries during repository cloning? |
Thank you @daviian , that was the right hint. May 8 19:22:59 Ubuntu-1704-zesty-64-minimal sshd[2390]: Authentication refused: bad ownership or modes for directory /home/git/.ssh Fixed that, now auth via ssh keys is working :) |
You are welcome! |
I faced same problem, anyone else have a solution.
|
YES, and more than this. When didn't use port And http clone is ok. (My Repos is private, http clone works.) |
[x]
):Description
When trying to clone over ssh I get following url:
ssh://git@domain:port/user/repo.git
But the repos are located under
ssh://git@domain:port/home/git/user/repo.git
I did not find an option similar to
ROOT_URL
for ssh. How can I configure gitea to use a custom directory for clone url over ssh without jailing my user and moving the repo root?Gitea config
RUN_USER = git
[repository]
ROOT = /home/git
[server]
SSH_DOMAIN = domain
DISABLE_SSH = false
SSH_PORT = 22
The text was updated successfully, but these errors were encountered: