Nginx reverse proxy guides - Page 3

Run Nginx in front of backend services with upstreams, proxy headers, WebSockets, backend ports, timeouts, and failure checks.

Curated guides

Nginx reverse proxy guides

32 matched guides, best match first. Page 3 of 3.

Nginx logo with rate limiting gauge and traffic barrier protecting server infrastructure

Configure Nginx Rate Limiting with limit_req

A login form, search endpoint, or API route can overload a backend long before the rest of the site looks busy. Nginx rate limiting caps request frequency at...

Updated ( Published )

Nginx HTTP/3 over QUIC diagram showing a browser, UDP 443, TLS 1.3, and upstream server

How to Enable HTTP/3 and QUIC in Nginx

HTTP/3 in Nginx is a version and build check before it is a configuration change. To enable HTTP/3 and QUIC in Nginx, the running binary must support the...

Published

NGINX CORS headers diagram showing allowed and blocked browser responses from an origin request

How to Configure CORS in Nginx

CORS becomes a server problem as soon as a browser app at one origin needs to read an API, font, image, or JSON response from another origin. To...

Published

Nginx logo with 504 timeout warning and upstream server routing diagram

How to Fix Nginx 504 Gateway Timeout Errors

An Nginx 504 Gateway Timeout error means Nginx waited too long for the next upstream step to complete. The upstream might be a reverse-proxied application, a PHP-FPM pool,...

Published

Nginx try_files routing diagram showing file checks and fallback paths.

Nginx try_files Directive Explained

Nginx try_files decides what happens after a request matches a server or location block. It can serve a real file, check for a directory, send the request to...

Published

Nginx logo with 403 gate and web file diagram for Forbidden troubleshooting

How to Fix Nginx 403 Forbidden

An Nginx 403 Forbidden error means the request reached the server, but Nginx or an upstream layer refused to serve the requested resource. The most common causes are...

Published

Nginx logo with broken upstream flow and 502 alert for Bad Gateway troubleshooting

How to Fix Nginx 502 Bad Gateway

An Nginx 502 Bad Gateway error means Nginx accepted the client request but could not get a valid response from the upstream service. The upstream might be a...

Published