helloshithub Public

Notifications Fork 0 Star 0

Git HTTPS push/clone fails with `Recv failure: Connection was reset` for newly created repository #2

New issue
Open chenghuaning opened this issue · 0 comments
chenghuaning opened

Summary

I registered an account, created a new public repository, and can open the repository page in the browser, but Git operations over HTTPS fail consistently.

Repository page:

Git remote:

  • https://shithub.sh/chenghuaning/helloshithub.git

What I expected

I expected to be able to push the first commit to the new repository, or at least clone / query the remote normally over HTTPS.

What happened

git push, git clone, and git ls-remote over HTTPS fail with:

fatal: unable to access 'https://shithub.sh/chenghuaning/helloshithub.git/': Recv failure: Connection was reset

SSH also does not work from my side because port 22 times out:

ssh: connect to host shithub.sh port 22: Connection timed out
fatal: Could not read from remote repository.

Reproduction

1. Create a new repository

Create a new public repository on shithub:

  • chenghuaning/helloshithub

2. Try to push initial commit

git init
echo "# helloshithub" > README.md
git add README.md
git commit -m "init"
git branch -M trunk
git remote add origin https://shithub.sh/chenghuaning/helloshithub.git
git push -u origin trunk

3. Actual result

fatal: unable to access 'https://shithub.sh/chenghuaning/helloshithub.git/': Recv failure: Connection was reset

Additional checks

Browser access works

The repository page opens normally in the browser:

The page shows the normal empty-repo quick setup UI.

Git Smart HTTP endpoint appears partially available

Requesting:

https://shithub.sh/chenghuaning/helloshithub.git/info/refs?service=git-upload-pack

returns HTTP 200 and application/x-git-upload-pack-advertisement.

Example response begins with:

001e# service=git-upload-pack
...

So the Git endpoint does not appear completely absent.

But Git client operations still fail

All of these fail over HTTPS with the same reset error:

git ls-remote https://shithub.sh/chenghuaning/helloshithub.git
git clone https://shithub.sh/chenghuaning/helloshithub.git
git push -u origin trunk

SSH check

Port 22 appears unavailable from my side:

ssh: connect to host shithub.sh port 22: Connection timed out

Environment

  • OS: Windows
  • Git: 2.55.0.windows.1
  • libcurl: 8.21.0
  • OpenSSL: 3.5.7

git version --build-options:

git version 2.55.0.windows.1
cpu: x86_64
libcurl: 8.21.0
OpenSSL: OpenSSL 3.5.7 9 Jun 2026

Notes

This does not look like a wrong remote URL or missing repository:

  • the repository page exists
  • the repository is visible publicly
  • the Git HTTP discovery endpoint returns a response

It looks more like the Git HTTPS transport path is being reset during actual Git client communication, or the reverse proxy / Git backend is not fully handling push/fetch traffic correctly.

Request

Please check whether:

  • Git Smart HTTP is fully configured for push/fetch
  • reverse proxy handling for Git traffic is complete
  • TLS / HTTP transport behavior is compatible with standard Git clients
  • SSH access is intentionally disabled or currently broken