nginx-reverse-proxy

Nginx reverse proxy 502 and 504 errors often stem from misconfigurations in nginx.conf or sites-available. Static analysis against a checklist identifies bad upstream definitions or timeout settings, providing precise diffs to resolve the failures.

Configuring WebSocket upgrades in an Nginx reverse proxy requires correct proxy_set_header directives for the Upgrade and Connection headers. The Skill reviews your configuration to ensure upgrade handling is properly set and provides diffs for any missing rules.

Enforcing security headers and TLS best practices in Nginx requires validating your conf.d files against strict standards. The Skill performs static analysis to identify insecure defaults and outputs actionable configuration diffs to harden your setup.

Nginx reverse proxy validation fails when configuration files contain syntax errors or invalid directives. The Skill enforces an nginx -t validation step after generating precise diffs, ensuring your TLS, rate limiting, and WebSocket changes deploy safely without breaking the server.

Reviewing Nginx rate limiting across multiple sites involves checking conf.d and sites-available directories for correct limit_req_zone and limit_req directives. The Skill analyzes these files using a checklist to spot misconfigurations and suggests safe, actionable corrections.

The Nginx reverse proxy checklist workflow supports on-demand reloads after configuration changes. Once you approve the generated diffs and the nginx -t validation passes, the Skill can perform a server reload to safely apply the TLS, WebSocket, and security header updates.