SSH check out gets stuck when file count was high

[VinothKumar-Ganesan]

Description

Cloning into 'development-server'...
remote: Enumerating objects: 248101, done.
remote: Counting objects: 100% (248101/248101), done.
remote: Compressing objects: 100% (34424/34424), done.
Receiving objects: 1% (2482/248101)

Gitea Version

1.23.7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

docker

Database

PostgreSQL

[lunny]

Could you post more details? What's the error on git client and any logs from Gitea side?

[VinothKumar-Ganesan]

Hi @lunny ,We are encountering this issue only when using SSH, particularly when the object count is huge but we can checkout the source using http over SSH but we can't proceed with http because it will expose authentication token currently we have do authentication in machine using SSH.

Repository Details

Clone Command:

git clone ssh://git@localhost:222/Sample-Organisation/reponame.git

Repository Name: reponame
Organization: Sample-Organisation
Repo Size: ~208 MB
Total Objects: 248,101
Progress Stalled At: ~23% (57,064 objects, 19.37 MiB)

📄 Gitea Logs (Key Events)

gitea | 2025/06/26 09:10:07 HTTPRequest [I] router: polling GET /user/events for 192.168.143.2:35000, elapsed 3061.3ms @ events/events.go:18(events.Events)
gitea | 2025/06/26 09:10:12 HTTPRequest [I] router: completed POST /Sample-Organisation/reponame/lastcommit/7b0a1fe40a0d39ef5f13cd4960baff3b8884ec7b/ for 192.168.143.2:36512, 200 OK in 8129.2ms @ repo/view.go:226(repo.LastCommit)
gitea | Accepted publickey for git from 192.168.143.2 port 60482 ssh2: ED25519 SHA256:0+kHgBx20xVap2+R836JR3DES+5e74bnBRbZ7x/iPW8
gitea | 2025/06/26 09:11:54 HTTPRequest [I] router: completed GET /api/internal/serv/command/1/Sample-Organisation/reponame?mode=1&verb=git-upload-pack for 192.168.143.2:0, 200 OK in 190.5ms @ private/serv.go:79(private.ServCommand)

[wxiaoguang]

These logs are unrelated to the problem.

You are reporting about "SSH checkout failing...", but your log doesn't contain any failure/error message.

At least, you need to figure out what's wrong.

An example for reporting the problem can be like this:

• Pure SSH hangs with LFS upload after Idle timeout #34834

I suspect you are cloning a LFS repo and maybe related to #34834 , which has been fixed in 1.24 nightly

[VinothKumar-Ganesan]

Hi @wxiaoguang , we don't have any LFS File in that repo but it was struck while check out

[wxiaoguang]

Then let's figure out where (and why) it gets stuck.

Git has an env option "GIT_TRACE": https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables

And maybe you need to collect more logs from Gitea server side (maybe not only logs, also process states and other clues)

[wxiaoguang]

The influence of irrelevant factors needs to be excluded, for example: are you able to reproduce the problem by a local setup? You can try to deploy a Gitea instance locally without reverse-proxy and try to use SSH to clone the same repo, to see whether it also gets stuck.

• If it can't reproduce, then it is related to your server or network.
• If it can reproduce, please share the setup steps and the reproducible repo (you can mock one) then others can reproduce and debug.

By the way, please use 1.24.2 or nightly to reproduce, beucase 1.23 is outdated and will not be maintained.