SSH key doesn't get deleted #1996

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

Originally created by @tarelda on GitHub (Jul 2, 2018).

  • Gitea version (or commit ref): 6efdcae
  • Git version: Not relevant I think
  • Operating system: gitea in docker
  • Database (use [x]):
    • PostgreSQL
    • [ x ] MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • [ x ] Not relevant
  • Log gist:

Description

First, I added key as a rw deploy key to repo. Pushing didn't do anything, so I re-added it as account key only to encounter this error:

Invalid key ID[key-5]: public key does not exist [id: 5]
fatal: Could not read from remote repository.

Recreating repo didn't help.

Originally created by @tarelda on GitHub (Jul 2, 2018). - Gitea version (or commit ref): 6efdcae - Git version: Not relevant I think - Operating system: gitea in docker - Database (use `[x]`): - [ ] PostgreSQL - [ x ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ x ] Not relevant - Log gist: ## Description First, I added key as a rw deploy key to repo. Pushing didn't do anything, so I re-added it as account key only to encounter this error: ```Gitea: Invalid key ID Invalid key ID[key-5]: public key does not exist [id: 5] fatal: Could not read from remote repository. ``` Recreating repo didn't help.
GiteaMirror added the type/bug label 2025-11-02 04:20:33 -06:00
Author
Owner

@techknowlogick commented on GitHub (Jul 2, 2018):

Are you able to select the "rewrite your authorized key file" from the admin page, and try again?

@techknowlogick commented on GitHub (Jul 2, 2018): Are you able to select the "rewrite your authorized key file" from the admin page, and try again?
Author
Owner

@tarelda commented on GitHub (Jul 3, 2018):

@techknowlogick actually fixed it, but I am wondering why it is not automagically update while altering keys in ui?

@tarelda commented on GitHub (Jul 3, 2018): @techknowlogick actually fixed it, but I am wondering why it is not automagically update while altering keys in ui?
Author
Owner

@tarelda commented on GitHub (Jul 4, 2018):

@techknowlogick Small update with new scenario probably related with previous.
Tried pull without key installed first. Pull obviously failed, so I added key. Still not worked so regenerated authorized_keys, but without luck. Readded key and repeated previous steps still with no success. I had to manually delete reference to key with lower id from authorized_keys and was finally able to pull sources.

@tarelda commented on GitHub (Jul 4, 2018): @techknowlogick Small update with new scenario probably related with previous. Tried pull without key installed first. Pull obviously failed, so I added key. Still not worked so regenerated authorized_keys, but without luck. Readded key and repeated previous steps still with no success. I had to manually delete reference to key with lower id from authorized_keys and was finally able to pull sources.
Author
Owner

@lunny commented on GitHub (Jan 9, 2019):

Related #1357 and should be fixed by #5671. I think you could rewrite public keys on Admin UI to manually fix that.

@lunny commented on GitHub (Jan 9, 2019): Related #1357 and should be fixed by #5671. I think you could rewrite public keys on Admin UI to manually fix that.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1996