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

After configuration of SSH for my account, and in my git client I receive the error message that the connection is closed. #2054

Closed
opened 2025年07月27日 18:54:17 +02:00 by jrsofty · 9 comments

Comment

Hello,

So I added an SSH Key to my account back in May of this year in preparation for using Codeberg for an open source project I would like to build.

Today I'm ready to start with setting up for this project and have created a repository here on Codeberg. I checked the connection and I keep receiving Connection closed by 217.197.84.140 port 22. I'm not certain why this isn't working. Testing the key on Github and i have no problems and receive a valid response.

Is there something I'm missing? I've followed the documentation https://docs.codeberg.org/security/ssh-key/ and I've verified my key to ensure that it works correctly.

I'm at a loss as I cannot find any reason for the error message above.

### Comment Hello, So I added an SSH Key to my account back in May of this year in preparation for using Codeberg for an open source project I would like to build. Today I'm ready to start with setting up for this project and have created a repository here on Codeberg. I checked the connection and I keep receiving `Connection closed by 217.197.84.140 port 22`. I'm not certain why this isn't working. Testing the key on Github and i have no problems and receive a valid response. Is there something I'm missing? I've followed the documentation https://docs.codeberg.org/security/ssh-key/ and I've verified my key to ensure that it works correctly. I'm at a loss as I cannot find any reason for the error message above.

This is also happening to me as well. I didn't change my key, and I pushed some commits last night.

This is also happening to me as well. I didn't change my key, and I pushed some commits last night.

another "me too" – haven’t had any issues for a while, but did a git push a little bit ago and get an error:

Connection closed by 2a0a:4580:103f:c0de::1 port 22
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
another "me too" – haven’t had any issues for a while, but did a `git push` a little bit ago and get an error: ``` Connection closed by 2a0a:4580:103f:c0de::1 port 22 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ```

Yeah,

Seems like this is a wider issue:

I also created issue about this case: #2056

Yeah, Seems like this is a wider issue: I also created issue about this case: https://codeberg.org/Codeberg/Community/issues/2056

https://social.anoxinon.de/@Codeberg/114926394214941898

It looks like we are under attack, that caused SSH connections to fail. We have deployed mitigations and the situation calmed down. Please let us know if the issue occurs again.

https://social.anoxinon.de/@Codeberg/114926394214941898 > It looks like we are under attack, that caused SSH connections to fail. We have deployed mitigations and the situation calmed down. Please let us know if the issue occurs again.

Lame. Someone needs a better hobby than to attack a community of open source developers...and using their tools. I can confirm it works now. Thanks!

Lame. Someone needs a better hobby than to attack a community of open source developers...and using their tools. I can confirm it works now. Thanks!
Author
Copy link

Thanks everyone for the quick feedback. I had truly thought I had made a mistake. It's working now so I'll close this.

Thanks everyone for the quick feedback. I had truly thought I had made a mistake. It's working now so I'll close this.

As @juhe said in #2056, perhaps the status page could be improved so that ssh issues are shown?

As @juhe said in #2056, perhaps the status page could be improved so that ssh issues are shown?

I believe this is still failing. see also #2055.

I believe this is still failing. see also #2055.

I've been experiencing this also for the past couple days now, and have verified my SSH and GPG keys and always get this error:

Enter passphrase for key '/home/matt/.ssh/id_ed25519':
Connection closed by 217.197.84.140 port 22
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I've been experiencing this also for the past couple days now, and have verified my SSH and GPG keys and always get this error: ``` Enter passphrase for key '/home/matt/.ssh/id_ed25519': Connection closed by 217.197.84.140 port 22 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ```
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
6 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#2054
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?