Setup reverse proxy with NGINX
Start by installing the NGINX HTTP server using
Once NGINX is installed, create the following configuration file in /etc/nginx/sites-available/glassfish.conf
:
1
|
vim /etc/nginx/sites-available/glassfish.conf
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
upstream glassfish {
server 127.0.0.1:8080 weight=100 max_fails=5 fail_timeout=5;
}
server {
listen 80;
server_name domain.tld;
location / {
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://glassfish/appname/;
}
}
|
Next, navigate to /etc/nginx/sites-enabled
and create a symbolic link to the glassfish.conf
configuration file you just created:
1
2
|
cd /etc/nginx/sites-enabled
ln -s /etc/nginx/sites-available/glassfish.conf
|
Now, check if Nginx configuration syntax is OK by running:
and restart and enable NGINX on your virtual server startup using:
1
2
|
service nginx restart
update-rc.d -f nginx enable
|
NGINX multiple server blocks
Create separately two files (you don’t have to, but it will be much clearer) in /etc/nginx/sites-available/www.example.com
and /etc/nginx/sites-available/www.example.net
.
As an example to redirect the second one to the first one
1
2
3
4
5
|
server {
listen 80;
server_name www.example.net;
return 301 http://www.example.com/;
}
|
SSL/TLS Certificate
Install certbot
1
|
apt-get install python-certbot-nginx
|
Generate certificates with the NGINX plug‑in
1
|
sudo certbot --nginx -d example.com -d www.example.com
|
verify the syntax of the configuration and restart NGINX
1
|
nginx -t && nginx -s reload
|
Automatically Renew Certificates
Open the crontab file
Add the certbot command to run every day at noon. The command checks to see if the certificate on the server will expire within the next 30 days, and renews it if so. The –quiet directive tells certbot not to generate output.
1
|
0 12 * * * /usr/bin/certbot renew --quiet
|
Save and close the file. All installed certificates will be automatically renewed and reloaded.
Stop and Remove
1
2
3
4
5
6
|
#to stop
sudo service nginx stop
#to remove (removes all package files)
sudo apt-get remove nginx
#or (removes all package files and the configuration files that package had installed)
sudo apt-get purge nginx
|
Errors
413 Request Entity Too Large
Solution: Increase client_max_body_size
. Default is 1M.
You can update this value by three different way
- Set in
http
block which affects all server blocks (virtual hosts).
1
2
3
4
|
http {
...
client_max_body_size 100M;
}
|
- Set in
server
block, which affects a particular site/app.
1
2
3
4
|
server {
...
client_max_body_size 100M;
}
|
- Set in
location
block, which affects a particular directory (uploads) under a site/app.
1
2
3
4
|
location /uploads {
...
client_max_body_size 100M;
}
|