The clue is with the URL which failed.
From first look, you appear to be using a FAST CGI URL with PHP?
Just a wild guess, but try using:
```
fastcgi_param PHP_VALUE "upload_max_filesize = 500M \n post_max_size=500M"
```
Here is a reference link mentioning it:
https://serverfault.com/a/704209
On Tue, Apr 23, 2024, 4:49 AM zen zenitram <quickfire28@gmail.com> wrote:
> Good day!
>
> Here is what happen when we try to upload file more than 128 kb. Too check
> if it is on server side we run the server without nginx and it can upload
> larger size files.
>
> Thank you!
>
>
>
> On Fri, Apr 19, 2024 at 6:18 PM Reinis Rozitis via nginx <nginx@nginx.org>
> wrote:
>
>> > It only accepts maximum of 128 kb of data, but the client_max_body_size
>> 500M;. Is there a way to locate the cause of error.
>>
>> Can you actually show what the "error" looks like?
>>
>> The default value of client_max_body_size is 1M so the 128Kb limit most
>> likely comes from the backend application or server which handles the POST
>> request (as an example - PHP has its own post_max_size /
>> upload_max_filesize settings).
>>
>>
>>
>> p.s. while it's unlikely (as you specify the settings in particular
>> location blocks) since you use wildcard includes it is always good to check
>> with 'nginx -T' how the final configuration looks like. Maybe the request
>> isn't handled in server/location block where you expect it ..
>>
>> rr
>> _______________________________________________
>> nginx mailing list
>> nginx@nginx.org
>> https://mailman.nginx.org/mailman/listinfo/nginx
>>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
