fatal: the remote end hung up unexpectedly fatal: the remote end hung up unexpectedly #2700

Closed
opened 2025-11-02 04:44:54 -06:00 by GiteaMirror · 13 comments
Owner

Originally created by @yb3616 on GitHub (Dec 31, 2018).

  • Gitea version (or commit ref):
  • 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

I guess it's gitea's bug, cause i found it done well in gogs.

Screenshots

default

Originally created by @yb3616 on GitHub (Dec 31, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - 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) - [ ] No - [x] Not relevant - Log gist: ## Description I guess it's gitea's bug, cause i found it done well in gogs. ## Screenshots ![default](https://user-images.githubusercontent.com/8839021/50553245-eae9b000-0cdd-11e9-90db-1ba212241662.PNG) <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/confirmedissue/needs-feedback labels 2025-11-02 04:44:54 -06:00
Author
Owner

@lafriks commented on GitHub (Jan 1, 2019):

Did you migrate from gogs?

@lafriks commented on GitHub (Jan 1, 2019): Did you migrate from gogs?
Author
Owner

@yb3616 commented on GitHub (Jan 6, 2019):

@lafriks No, Gitea and gogs are independent on my vps

@yb3616 commented on GitHub (Jan 6, 2019): @lafriks No, Gitea and gogs are independent on my vps
Author
Owner

@stale[bot] commented on GitHub (Mar 7, 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 7, 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.
Author
Owner

@lunny commented on GitHub (Mar 17, 2019):

Could you give more logs here?

@lunny commented on GitHub (Mar 17, 2019): Could you give more logs here?
Author
Owner

@Evsio0n commented on GitHub (Feb 26, 2020):

Seems I have a same issue here at:

Enumerating objects: 11, done.
Counting objects: 100% (11/11), done.
Delta compression using up to 12 threads
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 926 bytes | 926.00 KiB/s, done.
Total 9 (delta 6), reused 0 (delta 0)
error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date

@Evsio0n commented on GitHub (Feb 26, 2020): Seems I have a same issue here at: >Enumerating objects: 11, done. Counting objects: 100% (11/11), done. Delta compression using up to 12 threads Compressing objects: 100% (9/9), done. Writing objects: 100% (9/9), 926 bytes | 926.00 KiB/s, done. Total 9 (delta 6), reused 0 (delta 0) error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 fatal: the remote end hung up unexpectedly fatal: the remote end hung up unexpectedly Everything up-to-date
Author
Owner

@zeripath commented on GitHub (Feb 26, 2020):

@Evsio0n: We need some more information:

  • What version of Gitea?
  • What platform?
  • What do the server logs say?

If you are running 1.11.1 please upgrade to the head of release/v1.11 as there are several critical bugs in that release. We will get 1.11.2 out very soon.

@zeripath commented on GitHub (Feb 26, 2020): @Evsio0n: We need some more information: * What version of Gitea? * What platform? * What do the server logs say? If you are running 1.11.1 please upgrade to the head of release/v1.11 as there are several critical bugs in that release. We will get 1.11.2 out very soon.
Author
Owner

@francipvb commented on GitHub (Apr 6, 2020):

Hello,

I am registered in the server version 1.12.0+dev-82-g3723b0647. I don't have administrative access to the server so I cannot provide logs.

Cheers,

@francipvb commented on GitHub (Apr 6, 2020): Hello, I am registered in the server version 1.12.0+dev-82-g3723b0647. I don't have administrative access to the server so I cannot provide logs. Cheers,
Author
Owner

@zeripath commented on GitHub (Apr 6, 2020):

@francipvb that's quite an old version of 1.12 I recommend your team updates.

Without logs or further information there is little we can do to help. Anything could be going wrong.

@zeripath commented on GitHub (Apr 6, 2020): @francipvb that's quite an old version of 1.12 I recommend your team updates. Without logs or further information there is little we can do to help. Anything could be going wrong.
Author
Owner

@guillep2k commented on GitHub (Apr 8, 2020):

@francipvb You mean try.gitea.io?

@guillep2k commented on GitHub (Apr 8, 2020): @francipvb You mean `try.gitea.io`?
Author
Owner

@francipvb commented on GitHub (Apr 8, 2020):

Hello,

Sorry, my problem was a very big request. I got an HTTP 413 error and
that was causing it. This may be the same problem on the original issue
report...

Cheers,

--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

@francipvb commented on GitHub (Apr 8, 2020): Hello, Sorry, my problem was a very big request. I got an HTTP 413 error and that was causing it. This may be the same problem on the original issue report... Cheers, -- Cuando tus fuerzas terminan, las de mi Dios comienzan.
Author
Owner

@francipvb commented on GitHub (Apr 8, 2020):

Hello, Sorry, my problem was a very big request. I got an HTTP 413 error and that was causing it. This may be the same problem on the original issue report... Cheers,

My Fault... The reporter was pushing via SSH...

@francipvb commented on GitHub (Apr 8, 2020): > Hello, Sorry, my problem was a very big request. I got an HTTP 413 error and that was causing it. This may be the same problem on the original issue report... Cheers, My Fault... The reporter was pushing via SSH...
Author
Owner

@guillep2k commented on GitHub (Apr 9, 2020):

Glad you've found the solution, @francipvb

Closing for the time being. If anyone happen to find a similar issue, please try our Discord channel for help or open a new issue.

@guillep2k commented on GitHub (Apr 9, 2020): Glad you've found the solution, @francipvb Closing for the time being. If anyone happen to find a similar issue, please try our Discord channel for help or open a new issue.
Author
Owner

@bool64-llc commented on GitHub (Nov 5, 2020):

anyone who has this issue, try to increase ~nginx/like client_max_body_size

@bool64-llc commented on GitHub (Nov 5, 2020): anyone who has this issue, try to increase ~nginx/like `client_max_body_size`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2700