Intermittent success using git over SSH #2249

cascer1 commented 2025年12月08日 16:12:51 +01:00

Comment

Hi,

I just migrated a repository from GitHub to Codeberg, after this I updated the remote URL in my local repository to point to codeberg. However, I am only very infrequently able to use SSH to interact with my repositories. About 95% of the time I get a timeout.

$ git remote -v
origin	git@codeberg.org:cascer1/advent-of-code-2025-rust.git (fetch)
origin	git@codeberg.org:cascer1/advent-of-code-2025-rust.git (push)
$ git pull
ssh: connect to host codeberg.org port 22: Connection timed out
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
$ git push
ssh: connect to host codeberg.org port 22: Connection timed out
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
$ ssh -T git@codeberg.org
Hi there, cascer1! You've successfully authenticated with the key named desktop, but Forgejo does not provide shell access.
If this is unexpected, please log in with password and setup Forgejo under another user.

Intermittently I'm able to pull or push, and often the ssh command also times out. Could this be because I'm migrating a few repositories and am running into some rate limit? If so, I would've expected a rate limit response of sorts.

I tried on two different machines:

Machine 1

• Fedora Linux 43 (Workstation Edition) x86_64
• zsh 5.9
• OpenSSH_10.0p2, OpenSSL 3.5.4 30 Sep 2025
• git version 2.52.0

Machine 2

• Windows 11
• PowerShell 7.5.1
• OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.1
• git version 2.48.1.windows.1

### Comment Hi, I just migrated a repository from GitHub to Codeberg, after this I updated the remote URL in my local repository to point to codeberg. However, I am only very infrequently able to use SSH to interact with my repositories. About 95% of the time I get a timeout. ```bash $ git remote -v origin git@codeberg.org:cascer1/advent-of-code-2025-rust.git (fetch) origin git@codeberg.org:cascer1/advent-of-code-2025-rust.git (push) $ git pull ssh: connect to host codeberg.org port 22: Connection timed out fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. $ git push ssh: connect to host codeberg.org port 22: Connection timed out fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. $ ssh -T git@codeberg.org Hi there, cascer1! You've successfully authenticated with the key named desktop, but Forgejo does not provide shell access. If this is unexpected, please log in with password and setup Forgejo under another user. ``` Intermittently I'm able to pull or push, and often the ssh command also times out. Could this be because I'm migrating a few repositories and am running into some rate limit? If so, I would've expected a rate limit response of sorts. I tried on two different machines: **Machine 1** - Fedora Linux 43 (Workstation Edition) x86_64 - zsh 5.9 - OpenSSH_10.0p2, OpenSSL 3.5.4 30 Sep 2025 - git version 2.52.0 **Machine 2** - Windows 11 - PowerShell 7.5.1 - OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.1 - git version 2.48.1.windows.1

cascer1 commented 2025年12月08日 21:11:57 +01:00

I'm ashamed to admit that this was my own problem.

I just checked my firewall logs and it detected all my ssh activity as a scan

IPS Alert 2: Attempted Information Leak. Signature ET SCAN Potential SSH Scan OUTBOUND. From: <internal ip>, to: 217.197.84.140:22, protocol: TCP

I'm ashamed to admit that this was my own problem. I just checked my firewall logs and it detected all my ssh activity as a scan ``` IPS Alert 2: Attempted Information Leak. Signature ET SCAN Potential SSH Scan OUTBOUND. From: <internal ip>, to: 217.197.84.140:22, protocol: TCP ```