Troubleshooting NGINX Configuration

Troubleshooting may be necessary when configuring your HTTP or TCP/UDP proxy services with NGINX directives. Due to the large and complex dictionary of directives supported by NGINX and their complex grammatical structure, the device assists you by validating your configured directives. It does this only once you have applied them (i.e., clicked the Apply button) in the HTTP Directives table (see Configuring HTTP Directives).

In addition, the device generates the following NGINX configuration files:

■

nginx.conf: This file contains the currently active configuration, which is valid.

■

temp_nginx.conf: This file is generated if you have invalid configuration (directive errors). It is a temporary file and contains your new configuration, which is invalid. It is applied only if the device is restarted.

■

nginx.errors: This file is generated if you have invalid configuration (directive errors). This file contains all the error messages, indicating the line on which the error exists in the temp_nginx.conf file.

If you have modified your configuration and errors occur, the device continues running with the previous, valid NGINX configuration, unless the device is restarted, in which case it applies and uses the modified configuration.

In addition, if an NGINX validation error exists during configuration or if the device restarts with an invalid NGINX configuration, the device indicates this by the following:

■

Sends an alarm to the Active Alarms table ("NGINX configuration file is not valid")

■

Sends the error to syslog, which is marked with "http_app"

To send the NGINX files to a remote destination in tar fiel format (.tar), use the following CLI command:

# copy nginx-conf-files to <Protocol>://<Address>/<filename>.tar

To view the NGINX files in CLI, use the following command:

show network http-proxy conf active|errors|new