Nginx Settings
Configure every WAP Nginx field, including connection units, proxy buffers, protection switches and cache settings.
Open Web Servers → Nginx → Nginx Settings.
The form loads saved preferences, falling back to installed defaults when absent. All fields below are required by the server form, including dependent numeric values when a related switch is off.
General and connection settings
| Field | Accepted value |
|---|---|
| Application Template | Global selector: Hybrid, Proxy or Nginx. The selected supplied template must exist. |
| SSL Protocols | Required expression, up to 200 characters. |
| Maximum Request Body | Whole number followed by lowercase m, such as 10m; maximum 20 characters. |
| Request Body Buffer | Whole number followed by lowercase k, such as 16k; maximum 20 characters. |
| Keep-Alive Requests | Integer 1–20000. |
| Keep-Alive Timeout | Whole number followed by lowercase s, such as 30s; maximum 20 characters. |
| HTTP/2, HTTP/3 | Individual on/off switches. |
| HSTS, UserDir, Directory Listing | Individual on/off switches. |
| Pseudo FLV, Pseudo MP4 | Individual on/off switches. |
| Access Log Buffering | On/off. |
These unit checks are specific to this panel: do not replace them with other Nginx-compatible units. A switch does not install missing protocol support or a module.
Proxy settings
| Field | Accepted value |
|---|---|
| Proxy Buffering | On/off. |
| Proxy HTTP Version | 1.0 or 1.1. |
| Connection Header | On/off switch selecting template behavior. |
| Connect Timeout, Send Timeout, Read Timeout | Each uses a whole number plus lowercase s, maximum 20 characters. |
| Header Buffer | Whole number plus lowercase k, maximum 20 characters. |
| Buffer Count | Integer 1–20000. |
| Buffer Size, Busy Buffer Size, Temporary File Write Size | Each uses a whole number plus lowercase k, maximum 20 characters. |
The form validates individual values, not all Nginx buffer-size relationships or upstream compatibility. Keep a consistent set and validate the generated configuration before reload.
TLS and protection switches
Every item below is an independent on/off setting:
| Field | Template setting controlled |
|---|---|
| OCSP Stapling | Certificate-status stapling. |
| Prefer Server Ciphers | Server cipher preference. |
| Hotlink Protection | Hotlink rules. |
| ModSecurity | ModSecurity integration when available. |
| Range Protection | Range-request protection. |
| Method Restriction | Request-method restrictions. |
| User-Agent Filtering | User-agent filtering rules. |
| Scanner Protection | Scanner rules. |
| XSS Protection | XSS-related template protection. |
| Clickjacking Protection | Framing-related protection. |
| SQL Injection Protection | SQL-injection rules. |
| File Injection Protection | File-injection rules. |
| Cookie Exploit Protection | Cookie-exploit rules. |
| Referrer Spam Protection | Referrer-spam rules. |
| Symlink Protection | Symlink-related restrictions. |
| XML-RPC Protection | XML-RPC restrictions. |
These are switches for generated policy, not proof of complete attack prevention. Inspect the selected template and test application compatibility.
Limits and timeouts
| Field | Accepted value |
|---|---|
| Connection Limits | On/off. |
| Connection Limits: Per IP, Per Domain | Each integer 1–20000. |
| Request Limits | On/off. |
| Request Limits: Per IP, Per Domain | Each integer 1–20000. |
| Slowloris Protection | On/off. |
| Header Timeout, Body Timeout | Each integer 1–20000; these fields take bare integers, unlike the s-suffixed proxy timeouts. |
The selected template determines how limit values become directives. The form does not provide a full capacity model or a complete cross-field check.
Cache fields
Proxy Cache and FastCGI Cache each have:
| Field | Accepted value |
|---|---|
| Enable cache | On/off. |
| Revalidate | On/off. |
| Cache Lock | On/off. |
| Use Stale | On/off. |
| Minimum Uses | Integer 1–20000. |
| Cache Validity | Whole number followed by lowercase m or h, such as 30m or 2h; maximum 20 characters. |
Cacheable File Extensions and TLS Cipher Suites are required text fields, each up to 2000 characters. Preserve the syntax expected by the installed template. The form does not fully validate their generated configuration.
Review site behavior before broad application
Caching can expose inappropriate content if the selected template and application rules are incompatible. UserDir and directory listing change access paths; HSTS and filtering rules can affect browser and application behavior. Test representative requests before applying across sites.
Save, reset and apply
- Record current values and review domain overrides.
- Click Save Settings after editing.
- Resolve validation errors and check the saved values.
- Use the page's virtual-host rebuild action when the defaults must be incorporated into generated sites.
- Confirm the action and check taskd progress and logs.
- Validate the resulting configuration and verify sites after the intended service operation.
Saving writes global preferences only. Reset restores installed defaults; its helper can report success even if the preference write fails, so reload and verify. Neither operation automatically rebuilds all virtual hosts.
The all-virtual-host rebuild is a shared task, not a single-domain operation. Acceptance is not completion. The restart-labeled service action currently calls reload on the Eenos Nginx service and then checks status; it does not explicitly stop/start it.
Demo sessions cannot save, reset, rebuild or reload. Inspect generated configuration and service errors before retrying a failed operation.