SSH Error: Connection closed by remote host when pushing to Codeberg repo #1927

0xgausk commented 2025年05月13日 10:12:56 +02:00

Comment

Hello,

I'm experiencing an issue when trying to push changes to my Git repository hosted via SSH. The error I receive is:

kex_exchange_identification: Connection closed by remote host
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 immediately checked the SSH connection manually:

ssh -T git@codeberg.org
kex_exchange_identification: Connection closed by remote host
Connection closed by 217.197.84.140 port 22

Here’s what I’ve confirmed:

• My SSH key is correctly added to my Codeberg account.
• The same SSH key works fine with GitHub.
• ssh -T git@github.com returns the expected message.
• The SSH agent is running, and the key is added using ssh-add.
• My ~/.ssh/config contains the correct settings for Codeberg.

To continue working, I temporarily switched the remote URL to use HTTPS, which works fine — but I would prefer to use SSH as usual.

Is this a known issue with Codeberg’s SSH service? Could it be related to IP blocking or firewall restrictions?

Any help or clarification would be greatly appreciated.

Thank you!

### Comment Hello, I'm experiencing an issue when trying to push changes to my Git repository hosted via SSH. The error I receive is: ```bash kex_exchange_identification: Connection closed by remote host 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 immediately checked the SSH connection manually: ```bash ssh -T git@codeberg.org kex_exchange_identification: Connection closed by remote host Connection closed by 217.197.84.140 port 22 ``` Here’s what I’ve confirmed: * My SSH key is correctly added to my Codeberg account. * The same SSH key works fine with GitHub. * `ssh -T git@github.com` returns the expected message. * The SSH agent is running, and the key is added using `ssh-add`. * My `~/.ssh/config` contains the correct settings for Codeberg. To continue working, I temporarily switched the remote URL to use HTTPS, which works fine — but I would prefer to use SSH as usual. Is this a known issue with Codeberg’s SSH service? Could it be related to IP blocking or firewall restrictions? Any help or clarification would be greatly appreciated. Thank you!

esa commented 2025年05月13日 10:15:17 +02:00

Experiencing the same issue, from different machines with different keys. Looking at the status page it claims SSH is OK. I suspect there is an issue with both the SSH access and the SSH status check.

Experiencing the same issue, from different machines with different keys. Looking at [the status page](https://status.codeberg.eu/status/codeberg) it claims SSH is OK. I suspect there is an issue with both the SSH access and the SSH status check.

ErikSchlyter commented 2025年05月13日 10:18:56 +02:00

I'm having the same problem. I have verified the SSH key, so it should be OK.

I'm having the same problem. I have verified the SSH key, so it should be OK.

Somaimo commented 2025年05月13日 10:20:22 +02:00

Same experience here, after the maintenance window.

Same experience here, after the maintenance window.

divyaranjan commented 2025年05月13日 10:34:41 +02:00

Yep, I have the same issue. SSH just stopped working.

Yep, I have the same issue. SSH just stopped working.

esa commented 2025年05月13日 10:38:48 +02:00

It just started working for me! Still not so much as a colour blip on the statuspage about SSH, but the Codeberg Pages turned green.

It just started working for me! Still not so much as a colour blip on the statuspage about SSH, but the Codeberg Pages turned green.

Somaimo commented 2025年05月13日 17:39:01 +02:00

It would be great, if the People from Codeberg would optimize their status page checks for SSH. The service disruptions are more transparent in the future.

From my perspective the best solution would be, if the ssh check would also include a clone, pull and push and if anyone of them doesn't work, it would be flagged as disrupted. That's how we do it, since it doesn't make any sense checking ssh access if none of the above functions work.

It would be great, if the People from Codeberg would optimize their status page checks for SSH. The service disruptions are more transparent in the future. From my perspective the best solution would be, if the ssh check would also include a clone, pull and push and if anyone of them doesn't work, it would be flagged as disrupted. That's how we do it, since it doesn't make any sense checking ssh access if none of the above functions work.

Gusted commented 2025年05月13日 18:35:56 +02:00

The status page software is not capable of doing SSH (or delegating such task to a script), it's currently a simple check if the TCP port is open. Closing as it was during the maintenance window, nothing actionable.

The status page software is not capable of doing SSH (or delegating such task to a script), it's currently a simple check if the TCP port is open. Closing as it was during the maintenance window, nothing actionable.