Error when trying to clone a repository via HTTPS #2524

New Issue

GiteaMirror · 2025-11-02T04:39:24-06:00

GiteaMirror commented

2025-11-02 04:39:24 -06:00

Originally created by @shootie22 on GitHub (Nov 12, 2018).

Gitea version (or commit ref): e7128e8
Git version:
Operating system:
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

When trying to clone a rather large repo (~2 gigs), users get an error. I haven't modified anything at all related to Gitea or the server it is hosted on, really. It just suddenly stopped working. It works if we try to clone other smaller repos and it also works for users who already have the project cloned and are actively working on it. Push, pulls & fetches are working normally for those who already have the project. Here's the error the user gets when trying to clone the project:

fatal: The remote end hung up unexpectedly
fatal: protocol error: bad pack header
error: RPC failed; curl 18 transfer closed with outstanding read data remaining

Screenshots

Originally created by @shootie22 on GitHub (Nov 12, 2018).  - Gitea version (or commit ref): e7128e8 - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [X] No - [ ] Not relevant - Log gist: ## Description When trying to clone a rather large repo (~2 gigs), users get an error. I haven't modified anything at all related to Gitea or the server it is hosted on, really. It just suddenly stopped working. It works if we try to clone other smaller repos and it also works for users who already have the project cloned and are actively working on it. Push, pulls & fetches are working normally for those who already have the project. Here's the error the user gets when trying to clone the project: ``` fatal: The remote end hung up unexpectedly fatal: protocol error: bad pack header error: RPC failed; curl 18 transfer closed with outstanding read data remaining ``` ## Screenshots

GiteaMirror added the issue/stale issue/needs-feedback labels 2025-11-02 04:39:24 -06:00

GiteaMirror closed this issue

2025-11-02 04:39:25 -06:00

GiteaMirror commented

2025-11-02 04:39:26 -06:00

@lafriks commented on GitHub (Nov 12, 2018):

What git version (both on server and client) are you using? please attach also gitea.log errors

@lafriks commented on GitHub (Nov 12, 2018): What git version (both on server and client) are you using? please attach also gitea.log errors

GiteaMirror commented

2025-11-02 04:39:26 -06:00

@shootie22 commented on GitHub (Nov 12, 2018):

git version 2.11.0 on the server which apparently is the latest version
git version 2.17.1.windows.2 on the client
client log.txt
gitea.log.txt
http.log.txt

@shootie22 commented on GitHub (Nov 12, 2018): `git version 2.11.0` on the server which apparently is the latest version `git version 2.17.1.windows.2` on the client [client log.txt](https://github.com/go-gitea/gitea/files/2573750/client.log.txt) [gitea.log.txt](https://github.com/go-gitea/gitea/files/2573751/gitea.log.txt) [http.log.txt](https://github.com/go-gitea/gitea/files/2573752/http.log.txt)

GiteaMirror commented

2025-11-02 04:39:26 -06:00

@shootie22 commented on GitHub (Nov 13, 2018):

Any updates?

@shootie22 commented on GitHub (Nov 13, 2018): Any updates?

GiteaMirror commented

2025-11-02 04:39:26 -06:00

@angularsen commented on GitHub (Jan 9, 2019):

Same here. I don't see anyting special in the logs.
gitea.log
http.log

No changes on server, it just failed when I tried to fetch from a computer I hadn't used in a while so it was fetching some older history. git clone fails on both computers, so it seems like the data is corrupt maybe?

@angularsen commented on GitHub (Jan 9, 2019): Same here. I don't see anyting special in the logs. [gitea.log](https://github.com/go-gitea/gitea/files/2742127/gitea.log) [http.log](https://github.com/go-gitea/gitea/files/2742128/http.log) No changes on server, it just failed when I tried to fetch from a computer I hadn't used in a while so it was fetching some older history. `git clone` fails on both computers, so it seems like the data is corrupt maybe?

GiteaMirror commented

2025-11-02 04:39:26 -06:00

@stale[bot] commented on GitHub (Mar 10, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 10, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:39:27 -06:00

@stale[bot] commented on GitHub (Mar 24, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Mar 24, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:10:47 -06:00

[PR #2524] [MERGED] Automatically regenerate indexer for incompatible versions #16444

Sign in to join this conversation.