Nginx

NGINX 413 Request Entity Too Large

While trying to upload a file to a web app using NGINX as a reverse proxy, I encountered the following error: ... Save(<data/c5ceb2d914>) returned error, retrying after 19.847451977s: client.PutObject: <html>Documents/Fonts/FiraCode.zip <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.20.1</center> </body> </html> Save(<data/d194099394>) returned error, retrying after 36.899440019s: client.PutObject: <html>Documents/Fonts/FiraCode.zip <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.20.1</center> </body> </html> ... It turned out that NGINX has default value for file upload limit to 1 MB set in client_max_body_size variable. Therefore, I need to increase the file upload size to something bigger, says 50 MB. Where to update this file? Well, we can apply this change to the main NGINX’s configuration file, e.g. /etc/nginx/nginx.conf or specifically in the configuration file for the web app. I chose the latter for my case. ...

Installing Ingress-Nginx Controller with Helm

In my previous post, I showed how to install helm CLI on a server/instance running AlmaLinux 9. Now, I will share how to use helm to install the Ingress-Nginx Controller for a Kubernetes cluster. We install a package known as “chart” from a Helm repository. Initially, there is no repo, and can be seen below: $ helm repo list Error: no repositories to show In order to install Ingress-Nginx Controller, I first need to add a new repository. ...

Nginx Redirect One Path to Another

Nginx is probably my favorite web server up to this moment, and it runs and serves websites on all of my servers. I should say, I also like Apache web server too, but not as much as Nginx. Today, I need to redirect from one url path to another. It took me a while to get it right, and I’d better write it down before it’s forgotten. This is what I want: https://demo.example.com/login -> https//demo.example.com/demo/login. ...