releases.attachment Request Entity Too Large #2797

New Issue

GiteaMirror · 2025-11-02T04:48:50-06:00

GiteaMirror commented

2025-11-02 04:48:50 -06:00

Originally created by @yuelwish on GitHub (Jan 23, 2019).

Gitea version 8006b1b

Platform: Debian GNU/Linux 9

I want to publish a go compilation file of 1.8M, upload failed

error message:

<html>
 <head><title>413 Request Entity Too Large</title></head>
 <body bgcolor="white">
 <center><h1>413 Request Entity Too Large</h1></center>
 <hr><center>nginx/1.10.3</center>
 </body>
 </html>
 <!-- a padding to disable MSIE and Chrome friendly error page -->
 <!-- a padding to disable MSIE and Chrome friendly error page -->
 <!-- a padding to disable MSIE and Chrome friendly error page -->
 <!-- a padding to disable MSIE and Chrome friendly error page -->
 <!-- a padding to disable MSIE and Chrome friendly error page -->
 <!-- a padding to disable MSIE and Chrome friendly error page -->

app.ini

[attachment]
ENABLED        = true
ALLOWED_TYPES  = */*
MAX_SIZE       = 200
MAX_FILES      = 100

Originally created by @yuelwish on GitHub (Jan 23, 2019). Gitea version 8006b1b Platform: Debian GNU/Linux 9 I want to publish a go compilation file of 1.8M, upload failed > error message: ``` <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.10.3</center> </body> </html>       ``` > app.ini ``` [attachment] ENABLED = true ALLOWED_TYPES = */* MAX_SIZE = 200 MAX_FILES = 100 ```

GiteaMirror closed this issue

2025-11-02 04:48:50 -06:00

GiteaMirror commented

2025-11-02 04:48:51 -06:00

@zeripath commented on GitHub (Jan 23, 2019):

That error appears to be coming from nginx not Gitea.

Is it possible that nginx is rejecting the upload?

@zeripath commented on GitHub (Jan 23, 2019): That error appears to be coming from nginx not Gitea. Is it possible that nginx is rejecting the upload?

GiteaMirror commented

2025-11-02 04:48:51 -06:00

@yuelwish commented on GitHub (Jan 23, 2019):

Thank you.

I added the following to nginx

client_header_timeout 120s;         
client_body_timeout 120s;           
client_max_body_size 200m;

@yuelwish commented on GitHub (Jan 23, 2019): Thank you. I added the following to nginx ``` client_header_timeout 120s; client_body_timeout 120s; client_max_body_size 200m; ```

GiteaMirror commented

2025-11-02 04:48:51 -06:00

@rom111419 commented on GitHub (Mar 28, 2019):

NginX as a reverse proxy
If you are using multiple domains / web services on the same server (port 80), the request must be redirected to the appropriate service / port. For this you use reverse proxy. My NginX works here on an arched box.

server {
    listen 80;
    server_name git.xxxx.de;
    client_max_body_size 100M; # Push large objects to gitea

    location / {
        proxy_pass http://127.0.0.1:3000;
    }
}

@rom111419 commented on GitHub (Mar 28, 2019): **NginX as a reverse proxy** If you are using multiple domains / web services on the same server (port 80), the request must be redirected to the appropriate service / port. For this you use reverse proxy. My NginX works here on an arched box. ``` server { listen 80; server_name git.xxxx.de; client_max_body_size 100M; # Push large objects to gitea location / { proxy_pass http://127.0.0.1:3000; } } ```

GiteaMirror referenced this issue

2025-11-02 12:16:01 -06:00

[PR #2937] [MERGED] Fix files/commits of merged PRs #16671

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2797