I've had my ssh set up on a repository and been pushing commits to my code repo from the CLI without problem for about a month. I was then working on Codeberg CI using different test repositories, and I think interleaving work on that with pushes from the earlier code repo.
I took a few days break and suddenly, trying to push changes to the code repo is giving an error:
$ git push --set-upstream origin main
Forgejo: Public (Deploy) Key: 104603:ssh_key is not authorized to write to happybeing/dweb.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I don't understand what "104603:ssh_key" refers to. I noted that I had a global ssh key, so added and verified another but the error persists. I noticed I didn't have a Deploy key in the code repo settings, so added one there (following instructions at https://docs.codeberg.org/security/ssh-key/ and added that public key to the code repo.
I still get the above error so guess something has happened to stop the very first (global) ssh key I added from being recognised. So I deleted that global key (which showed "Added on Jun 1, 2025 — Last used on Jul 4, 2025").
Still the error message remains the same.
I'm not sure what I've done to mess this up or if it could be a Codeberg issue.
Any help appreciated.
### Comment
I've had my ssh set up on a repository and been pushing commits to my code repo from the CLI without problem for about a month. I was then working on Codeberg CI using different test repositories, and I think interleaving work on that with pushes from the earlier code repo.
I took a few days break and suddenly, trying to push changes to the code repo is giving an error:
```
$ git push --set-upstream origin main
Forgejo: Public (Deploy) Key: 104603:ssh_key is not authorized to write to happybeing/dweb.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
```
I don't understand what "104603:ssh_key" refers to. I noted that I had a global ssh key, so added and verified another but the error persists. I noticed I didn't have a Deploy key in the code repo settings, so added one there (following instructions at https://docs.codeberg.org/security/ssh-key/ and added that public key to the code repo.
I still get the above error so guess something has happened to stop the very first (global) ssh key I added from being recognised. So I deleted that global key (which showed "Added on Jun 1, 2025 — Last used on Jul 4, 2025").
Still the error message remains the same.
I'm not sure what I've done to mess this up or if it could be a Codeberg issue.
Any help appreciated.