Nginx - Revision history

Leaky: /* Custom error pages */

2018-11-13T12:25:48Z

‎Custom error pages

Leaky: /* Custom error pages */

2018-11-13T12:25:32Z

‎Custom error pages

Leaky: nginx proxying and handling unavailable backend servers

2018-11-13T12:25:17Z

nginx proxying and handling unavailable backend servers

Leaky: added note about gitea and buffering

2017-08-16T08:41:10Z

added note about gitea and buffering

Leaky: Using nginx as a proxy during server migrations

2014-01-23T23:03:50Z

Using nginx as a proxy during server migrations

New page

To use nginx as a proxy - for example from an old server to a new one during a migration, you need to set the Host header to be $host

There are also some other headers that could be useful so just set the whole lot in the global part of /etc/nginx/conf.d/default.conf

proxy_set_header Host $host;
proxy_set_header Connection "";
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Port $server_port;

Setup the server to listen either on every interface port 80, or a specific IP on port 80 using the listen directive.

server {
listen 80 default_server;
listen [2a02:af8:3:2000::7982]:80 default_server;
server_name _;

And make sure that the entire site from / downwards is proxied through to the new IP address

location / {
proxy_pass http://213.229.84.27;
}
}

@@ Line 58: / Line 58: @@
          location / {
                  try_files $uri @starman;
+         }

@@ Line 55: / Line 55: @@
          root /var/www/html;
-−
          location / {
                  try_files $uri @starman;
+         }
-−
          location @starman {
                  proxy_set_header X-Real-IP $remote_addr;
@@ Line 78: / Line 78: @@
          error_page 503 =503 @proxyisdown;
          error_page 502 =502 @proxyisdown;
-−
          location @proxyisdown {
                  rewrite ^.*$ /error.html break;

← Older revision		Revision as of 12:25, 13 November 2018
Line 49:		Line 49:
	}		}
	}		}
		+
		+	== Custom error pages ==
		+
		+	Proxying to a backend server (such as Catalyst+starman) but returning any files which actually exist in /var/www/html such as CSS or JavaScript files.
		+
		+	root /var/www/html;
		+
		+	location / {
		+	try_files $uri @starman;
		+
		+	}
		+
		+	location @starman {
		+	proxy_set_header X-Real-IP $remote_addr;
		+	proxy_set_header X-Forwarded-For $remote_addr;
		+	proxy_set_header SSL on;
		+	proxy_set_header X-Forwarded-Proto https;
		+	proxy_set_header Host $host;
		+	proxy_pass http://127.0.0.1:3003;
		+	}
		+
		+	If there's an error (for example the backend server is down) you'll get a "502 Bad Gateway" response from nginx. To output a static HTML page, you can use the error_page directive
		+
		+	error_page 502 /error.html
		+
		+	This works fine except that the response code 502 is replaced with a 200 and this will cause your error page to be cached by Google etc. Instead of the above, add a section as follows.
		+
		+	error_page 503 =503 @proxyisdown;
		+	error_page 502 =502 @proxyisdown;
		+
		+	location @proxyisdown {
		+	rewrite ^.*$ /error.html break;
		+	add_header Retry-After 600;
		+	expires 1s;
		+	}
		+
		+	This causes the status code to be returned still, but outputs the content from the page error.html (located in the root). The rewrite to ignore any path is required otherwise a valid url handled by the backend (e.g. /login) will return a "404 Not found" if the backend is down. This is because it attempts to return the content of /var/www/html/login which doesn't exist.

@@ Line 20: / Line 20: @@
          proxy_pass http://213.229.84.27;
+     }
+  }