# Wrong ssh url path

**URL:** <https://forum.gitea.com/t/wrong-ssh-url-path/183>\
**Category:** Install/Maintain/Configure\
**Created:** [January 25, 2018, 12:01pm UTC](https://forum.gitea.com/t/wrong-ssh-url-path/183 "2018-01-25T12:01:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![asche](https://avatars.discourse-cdn.com/v4/letter/a/9dc877/32.png) [@asche](https://forum.gitea.com/u/asche)\
**Post date:** [January 25, 2018, 12:01pm UTC](https://forum.gitea.com/t/wrong-ssh-url-path/183/1 "2018-01-25T12:01:25Z")

</div>

hello,

gitea shows wrong repo path.

path in gitea:  
`git@web-app:organisation/repo.git`

git clone says:  
fatal: ‘organisation/repo.git’ does not appear to be a git repository  
fatal: Could not read from remote repository.

when i change the path manually to  
`git@web-app:/home/git/repos/organisation/repo.git`  
then it works.

my repository and server settings:

```
[repository]
ROOT = /home/git/repos

[server]
SSH_DOMAIN = web-app
DOMAIN = web-app
HTTP_PORT = 3000
ROOT_URL = http://web-app:3000
DISABLE_SSH = false
SSH_PORT = 22
LFS_START_SERVER = true
LFS_CONTENT_PATH = /home/git/gitea/lfs
LFS_JWT_SECRET = xxxxxxxxxxxxxxxxxxx
OFFLINE_MODE = false

```

what’s wrong in my config?

tahnks

---

<div class="post-metadata">

**Author:** ![andrii](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@andrii](https://forum.gitea.com/u/andrii)\
**Post date:** [March 30, 2018, 7:55am UTC](https://forum.gitea.com/t/wrong-ssh-url-path/183/2 "2018-03-30T07:55:05Z")

</div>

I suppose you are not right,  
if you use absolute path it means that the ‘git’ user has the shell access to the server and you will use ssh-key from ‘/home/git/.ssh/authorized\_keys’ file instead of keys which is added to the gitea user profile via UI.  
so then as a result you will be able to push inside not own repo

I had similar issue([https://stackoverflow.com/questions/49297267](https://stackoverflow.com/questions/49297267))  
the issue was fixed by disabling the ‘LFS\_START\_SERVER’ option

---

<div class="post-metadata">

**Author:** ![techknowlogick](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/techknowlogick/32/4706_2.png) [@techknowlogick](https://forum.gitea.com/u/techknowlogick)\
**Post date:** [May 24, 2018, 6:03pm UTC](https://forum.gitea.com/t/wrong-ssh-url-path/183/3 "2018-05-24T18:03:33Z")

</div>

Here is a response from @daviian on [another forum post](https://forum.gitea.com/t/solved-using-regular-git-ssh-not-working/286) which likely covers your issues:

> Hi,

> To clarify the SSH url: the stuff after the colon is for internal use in gitea. Gitea itself provides the mapping to the actual repository location.  
> So what you do when using the original path is bypassing gitea, which shouldn’t be possible at all!
> 
> One reason this happens is that you set your SSH key in the authorized\_keys file yourself with e.g. ssh-copy-id. However that’s wrong and you should definitely let gitea handle this file.  
> Furthermore everytime a user adds an SSH key via gitea web-UI the authorized\_keys file gets overwritten.
> 
> Another thing is that usually the user from the SSH url is git or whatever is configured in the app.ini and not the actual gitea-user itself.
> 
> The first thing you should try now is to go into the Admin settings on the gitea UI and execute:
> 
> ```
> Update the ‘.ssh/authorized_keys’ file with Gitea SSH keys. (Not needed for the built-in SSH server.)
> Resynchronize pre-receive, update and post-receive hooks of all repositories.
> 
> ```
> 
> After that you HAVE to set your SSH keys through gitea web-UI.
> 
> Hopefully that solves your issue!