Strange ssh authorization issues (repo doesn't exist) #54

Closed
opened 2025-11-02 03:06:20 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @smcquay on GitHub (Nov 12, 2016).

  • Gitea version (or commit ref):

    555d8b1

  • Git version:

    git version 2.7.4

  • Operating system:

    ubuntu 16.04.1

  • Database (use [x]):

    • PostgreSQL
    • MySQL
    • SQLite
  • Log gist:

Description

I had a bunch of ssh public keys configured, but since an upgrade to gitea I cannot clone repos.

Example from a public repo:

sm@impa:~
ssh git@s.mcquay.me                                                                                  rc: 128  
PTY allocation request failed on channel 0
Hi there, You've successfully authenticated, but Gogs does not provide shell access.
If this is unexpected, please log in with password and setup Gogs under another user.
2016/11/11 23:12:55 <nil>
Connection to s.mcquay.me closed.
sm@impa:~
git clone git@s.mcquay.me:sm/fo.git                                                                    rc: 1  
Cloning into 'fo'...
Gogs: Repository does not exist or you do not have access
User  does not have level read access to repository sm/fo.git
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Originally created by @smcquay on GitHub (Nov 12, 2016). - Gitea version (or commit ref): 555d8b1 - Git version: git version 2.7.4 - Operating system: ubuntu 16.04.1 - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] SQLite - Log gist: ## Description I had a bunch of ssh public keys configured, but since an upgrade to gitea I cannot clone repos. Example from a public repo: ```bash sm@impa:~ ssh git@s.mcquay.me rc: 128 PTY allocation request failed on channel 0 Hi there, You've successfully authenticated, but Gogs does not provide shell access. If this is unexpected, please log in with password and setup Gogs under another user. 2016/11/11 23:12:55 <nil> Connection to s.mcquay.me closed. sm@impa:~ git clone git@s.mcquay.me:sm/fo.git rc: 1 Cloning into 'fo'... Gogs: Repository does not exist or you do not have access User does not have level read access to repository sm/fo.git fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ```
GiteaMirror added the type/bug label 2025-11-02 03:06:20 -06:00
Author
Owner

@smcquay commented on GitHub (Nov 12, 2016):

I tried creating a different db, and got this:

git clone git@s.mcquay.me:sm/foo.git                                                                          
Cloning into 'foo'...
Gogs: Invalid key ID
Invalid key ID[key-37]: public key does not exist [id: 37]
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

but after I ran Rewrite '.ssh/authorized_keys' file (caution: non-Gitea keys will be lost) I get the same:

git clone git@s.mcquay.me:sm/foo.git                                                                          
Cloning into 'foo'...
Gogs: Repository does not exist or you do not have access
User  does not have level read access to repository sm/foo.git
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
@smcquay commented on GitHub (Nov 12, 2016): I tried creating a different db, and got this: ``` bash git clone git@s.mcquay.me:sm/foo.git Cloning into 'foo'... Gogs: Invalid key ID Invalid key ID[key-37]: public key does not exist [id: 37] fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ``` but after I ran `Rewrite '.ssh/authorized_keys' file (caution: non-Gitea keys will be lost)` I get the same: ``` bash git clone git@s.mcquay.me:sm/foo.git Cloning into 'foo'... Gogs: Repository does not exist or you do not have access User does not have level read access to repository sm/foo.git fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ```
Author
Owner

@smcquay commented on GitHub (Nov 12, 2016):

If I make the repo public I can clone, but can't push.

@smcquay commented on GitHub (Nov 12, 2016): If I make the repo public I can clone, but can't push.
Author
Owner

@lunny commented on GitHub (Nov 12, 2016):

Hi, please update gitea to the latest version. Since 555d8b1 has an obvious bug, I have sent #154 later and it was merged.

@lunny commented on GitHub (Nov 12, 2016): Hi, please update gitea to the latest version. Since 555d8b1 has an obvious bug, I have sent #154 later and it was merged.
Author
Owner

@smcquay commented on GitHub (Nov 12, 2016):

Indeed; thanks for the fix!

@smcquay commented on GitHub (Nov 12, 2016): Indeed; thanks for the fix!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#54