I need help with our NGINX set up

Z
zen
  • 19 Apr '24
Good day!

We have an Institutional Repository server that uses NGINX as load balancer
but we encountered problem when trying to upload documents to the
repository. 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.

Here are our NGINX configuration files

*/etc/nginx/nginx.conf*

worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

events {
       worker_connections 768;
       # multi_accept on;
}

http {

       # Basic Settings

       sendfile on;
       tcp_nopush on;
       types_hash_max_size 2048;
       client_max_body_size 500M;
       # server_tokens off;

       # server_names_hash_bucket_size 64;
       # server_name_in_redirect off;

       include /etc/nginx/mime.types;
       default_type application/octet-stream;

       ##
       # SSL Settings
       ##

       ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref:
POODLE
       ssl_prefer_server_ciphers on;

       ##
       # Logging Settings
       ##

       access_log /var/log/nginx/access.log;
       error_log /var/log/nginx/error.log;

       ##
       # Gzip Settings
       ##

       gzip_vary on;

       # gzip_vary on;
       # gzip_proxied any;
       # gzip_comp_level 6;
       # gzip_buffers 16 8k;
       # gzip_http_version 1.1;
       # gzip_types text/plain text/css application/json
application/javascript text/xml application/xml application/xml+rss
text/javascript;

       ##
       # Virtual Host Configs
       ##

       include /etc/nginx/conf.d/*.conf;
       include /etc/nginx/sites-enabled/*;
}

*/etc/nginx/site-available/test.edu.ph <http://test.edu.ph/>*

server {
   server_name test.edu.ph;

   location / {
       proxy_pass https://192.168.8.243;
       proxy_set_header Host $host;
       proxy_set_header X-Real-IP $remote_addr;
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_set_header X-Forwarded-Proto $scheme;
       client_max_body_size 500M;
   }

   listen 443 ssl; # managed by Certbot
   ssl_certificate /etc/letsencrypt/live/test.edu.ph/fullchain.pem; #
managed by Certbot
   ssl_certificate_key /etc/letsencrypt/live/test.edu.ph/privkey.pem; #
managed by Certbot
   include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
   ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
   client_max_body_size 500M;

}

server {
   if ($host = test.edu.ph) {
       return 301 https://$host$request_uri;
   } # managed by Certbot

   listen 80;
   server_name test.edu.ph;
   return 404; # managed by Certbot
   client_max_body_size 500M;
}

Need help with this one. Thank you!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20240419/523c681b/attachment.htm>
R
Reinis
  • 19 Apr '24
> 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
Z
zen
  • 23 Apr '24
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 at 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 at nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20240423/26c7d0f9/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: error eprints on nginx.jpg
Type: image/jpeg
Size: 307084 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20240423/26c7d0f9/attachment-0001.jpg>
  • Page 1 of 1
Reply