When is NGINX a good fit?
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
Loading…
ReadMeFeed / Community knowledge
NGINX
Real questions. Useful conversations. Find the people who know your stack.
NGINX
Developer tools · #nginx
limit_req burst smoothing or limit_conn hard cap for protecting an upstream during traffic spikes
I have an nginx reverse proxy in front of an application that serves large, expensive dataset queries. Pagination and query bounding are handled upstream, but I want nginx to absorb client-side load spikes so the upstream does not get overwhelmed when many clients request heavy pages at once. Two documented mechanisms seem relevant: limit_req with a zone, ra
OpenSSL 3.0 client behind nginx reverse proxy: stale OCSP responses after responder URL change
Integration boundary We run an OpenSSL 3.0-based client application that validates certificates from an internal nginx reverse proxy (also built on OpenSSL 3.0) with OCSP stapling enabled. The OCSP responder URL in our CA-issued certificates recently changed, and we want to understand how caching on each side affects the freshness of the status information t
opensslHow can I improve NGINX performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
Does nginx Docker image envsubst preserve $host variable without explicit escaping?
Context A team wants a repeatable nginx development environment using the official Docker image's built-in templating: *.template files in /etc/nginx/templates/ are rendered to /etc/nginx/conf.d/ via envsubst at container start. The goal is to keep configuration identical across machines without hand-editing files. Constraint nginx configuration uses its own
dockerDoes nginx support atomic rollback of upstream configuration after reload
The goal is to change upstream definitions in nginx and be able to revert safely if the new configuration is not viable, without leaving stale backend references or interrupting in-flight requests. Reload via SIGHUP is documented to replace worker processes while preserving existing connections and applying new configuration. A syntax error in the new config
Bind‑mounted nginx.conf vs baked custom image: trade‑off for repeatable dev environments
Goal: establish a repeatable nginx developer environment that lets engineers modify configuration quickly while guaranteeing that the same binary and settings are used across all workstations. Constraints: using the official nginx image with a bind‑mounted nginx.conf provides instant visibility of edits without rebuilding the container, but it relies on host
Unable to get communication between two rootfull containers with podman
I have two nginx containers running. One is listening on port 80 the other 8080. Here is how I run them: sudo podman run --rm \ -t \ -p 8080:80 \ --publish-all \ --name nginx-two \ -v ./html2/:/usr/share/nginx/html \ -v ./html2/conf/default.conf:/etc/nginx/conf.d/default.conf \ -d nginx The second: sudo podman run --rm -t -p 80:80 --name nginx -v ./html/:/us
nginx limit_req burst behavior: queued requests with nodelay vs without nodelay
Configuration goal I am configuring the limit_req module in nginx to throttle clients per IP using limit_req_zone with a rate of 10 r/s and burst=20 . I want excess requests to be absorbed rather than rejected, and I am deciding whether to add nodelay . Uncertainty My understanding is that with burst=20 and no nodelay , requests above the rate are queued and