Codeberg/Community
54
325
Fork
You've already forked Community
12

previously working ssh key being rejected and I can't set up a new one that works #2024

Closed
opened 2025年07月14日 18:31:35 +02:00 by happybeing · 2 comments

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.

### 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.

Hi, you have added the SSH key that you are pushing with as a deploy key on https://codeberg.org/happybeing/ci-test-codeberg-pages. So you can only push to that repository with your SSH key.

But it seems you also have a global SSH key, you might need to configure your SSH config to make sure that this key is used when you are connecting to codeberg.org and not the deploy key.

Hi, you have added the SSH key that you are pushing with as a deploy key on https://codeberg.org/happybeing/ci-test-codeberg-pages. So you can only push to that repository with your SSH key. But it seems you also have a global SSH key, you might need to configure your SSH config to make sure that this key is used when you are connecting to codeberg.org and not the deploy key.

Sorted, many thanks.

For others I found this StackOverflow answer helpful and solved my issue by creating a ~/.ssh/config for the domain codeberg.org which selects a global key on this account.

Sorted, many thanks. For others I found this StackOverflow answer helpful and solved my issue by creating a `~/.ssh/config` for the domain `codeberg.org` which selects a global key on this account.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2024
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?