Skip to Content
Browse documentation

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

FieldAccepted value
Application TemplateGlobal selector: Hybrid, Proxy or Nginx. The selected supplied template must exist.
SSL ProtocolsRequired expression, up to 200 characters.
Maximum Request BodyWhole number followed by lowercase m, such as 10m; maximum 20 characters.
Request Body BufferWhole number followed by lowercase k, such as 16k; maximum 20 characters.
Keep-Alive RequestsInteger 1–20000.
Keep-Alive TimeoutWhole number followed by lowercase s, such as 30s; maximum 20 characters.
HTTP/2, HTTP/3Individual on/off switches.
HSTS, UserDir, Directory ListingIndividual on/off switches.
Pseudo FLV, Pseudo MP4Individual on/off switches.
Access Log BufferingOn/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

FieldAccepted value
Proxy BufferingOn/off.
Proxy HTTP Version1.0 or 1.1.
Connection HeaderOn/off switch selecting template behavior.
Connect Timeout, Send Timeout, Read TimeoutEach uses a whole number plus lowercase s, maximum 20 characters.
Header BufferWhole number plus lowercase k, maximum 20 characters.
Buffer CountInteger 1–20000.
Buffer Size, Busy Buffer Size, Temporary File Write SizeEach 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:

FieldTemplate setting controlled
OCSP StaplingCertificate-status stapling.
Prefer Server CiphersServer cipher preference.
Hotlink ProtectionHotlink rules.
ModSecurityModSecurity integration when available.
Range ProtectionRange-request protection.
Method RestrictionRequest-method restrictions.
User-Agent FilteringUser-agent filtering rules.
Scanner ProtectionScanner rules.
XSS ProtectionXSS-related template protection.
Clickjacking ProtectionFraming-related protection.
SQL Injection ProtectionSQL-injection rules.
File Injection ProtectionFile-injection rules.
Cookie Exploit ProtectionCookie-exploit rules.
Referrer Spam ProtectionReferrer-spam rules.
Symlink ProtectionSymlink-related restrictions.
XML-RPC ProtectionXML-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

FieldAccepted value
Connection LimitsOn/off.
Connection Limits: Per IP, Per DomainEach integer 1–20000.
Request LimitsOn/off.
Request Limits: Per IP, Per DomainEach integer 1–20000.
Slowloris ProtectionOn/off.
Header Timeout, Body TimeoutEach 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:

FieldAccepted value
Enable cacheOn/off.
RevalidateOn/off.
Cache LockOn/off.
Use StaleOn/off.
Minimum UsesInteger 1–20000.
Cache ValidityWhole 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

  1. Record current values and review domain overrides.
  2. Click Save Settings after editing.
  3. Resolve validation errors and check the saved values.
  4. Use the page's virtual-host rebuild action when the defaults must be incorporated into generated sites.
  5. Confirm the action and check taskd progress and logs.
  6. 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.