fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. #2465

New Issue

GiteaMirror · 2025-11-02T04:37:17-06:00

GiteaMirror commented

2025-11-02 04:37:17 -06:00

Originally created by @symgryph on GitHub (Oct 29, 2018).

gitea.service.txt

Gitea version (or commit ref):
Git version: 2.19.0
Operating system: Centos 7.5
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:
https://gist.github.com/symgryph/521309620e2a236c4d113d725ae8569b

Description

I am unable to clone private repos via ssh. It works fine over https, or if I use the 'internal' ssh that comes with gitea. I can get into the system, log things etc, but alwas get the titel for my error. The file exists in proper directory, and the git user has write/read access to the repo.

I am using an attched systemd service file to start gitea as a non root user. Gitea is fronted by a caddy proxy (web stuff is fine).
gitea.service.txt

app.txt
sshd_config.txt

...

Screenshots

Originally created by @symgryph on GitHub (Oct 29, 2018). [gitea.service.txt](https://github.com/go-gitea/gitea/files/2523460/gitea.service.txt) - Gitea version (or commit ref): - Git version: 2.19.0 - Operating system: Centos 7.5 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: https://gist.github.com/symgryph/521309620e2a236c4d113d725ae8569b ## Description I am unable to clone private repos via ssh. It works fine over https, or if I use the 'internal' ssh that comes with gitea. I can get into the system, log things etc, but alwas get the titel for my error. The file exists in proper directory, and the git user has write/read access to the repo. I am using an attched systemd service file to start gitea as a non root user. Gitea is fronted by a caddy proxy (web stuff is fine). [gitea.service.txt](https://github.com/go-gitea/gitea/files/2523462/gitea.service.txt) [app.txt](https://github.com/go-gitea/gitea/files/2523447/app.txt) [sshd_config.txt](https://github.com/go-gitea/gitea/files/2523450/sshd_config.txt) ... ## Screenshots

GiteaMirror closed this issue

2025-11-02 04:37:18 -06:00

GiteaMirror commented

2025-11-02 04:37:19 -06:00

@lunny commented on GitHub (Oct 29, 2018):

Could you try ssh -vvv ... to give more logs?

@lunny commented on GitHub (Oct 29, 2018): Could you try `ssh -vvv ...` to give more logs?

GiteaMirror commented

2025-11-02 04:37:19 -06:00

@symgryph commented on GitHub (Oct 29, 2018):

For some reason if you use UpperCaseNames it converts them all to lower case causing the ssh to bork up. If I just use lowecase everything works. Verified that this is a bug, since I created a new repo and used camel case, the ssh directory was all lower case.

@symgryph commented on GitHub (Oct 29, 2018): For some reason if you use UpperCaseNames it converts them all to lower case causing the ssh to bork up. If I just use lowecase everything works. Verified that this is a bug, since I created a new repo and used camel case, the ssh directory was all lower case.

GiteaMirror commented

2025-11-02 04:37:19 -06:00

@symgryph commented on GitHub (Oct 29, 2018):

Figured it out NOT camel case. You can't set git's user as /bin/false you HAVE to allow for logins.....

@symgryph commented on GitHub (Oct 29, 2018): Figured it out NOT camel case. You can't set git's user as /bin/false you HAVE to allow for logins.....

GiteaMirror referenced this issue

2025-11-02 12:10:04 -06:00

[PR #2465] [MERGED] Fix migration from pre-v15 to 1.2.0 (#2460) #16414

Sign in to join this conversation.