Troubleshooting - Nginx
To troubleshoot Nginx Server Monitor, follow the below steps:
- Verify Accessibility: Ensure that the Nginx server instance is accessible from the Applications Manager server.
- Check Host and Port: Make sure you’ve entered the correct host and port number for your Nginx server.
- SSL Configuration: Retry adding the monitor with the "SSL is enabled" option both enabled and disabled.
- Test Nginx server API Accessibility: Verify that the Nginx server API (http(s)://[HOST]:[PORT]/nginx_status) is accessible from the Applications Manager server.
- Proxy Server Configuration: If your environment requires the use of a proxy server to access the Nginx server API, configure the proxy in Applications Manager. Click here to learn how to configure the proxy.
- Bypass Proxy for Nginx server: If you have configured a proxy in Applications Manager but want to bypass it for the Nginx server host/IP, add the host/IP under the "Do not use proxy for addresses beginning with" section in the "Configure Proxy" page: Navigate to Settings > Product Settings > Proxy Server Settings.
- Check Authentication Details: If authentication credentials are missing or incorrect, you’ll encounter an authentication error. To resolve this:
- Enable the "Is Authentication Required" option in the monitor configuration page.
- Provide the correct authentication credentials.
Upon adding the Nginx server, why am I getting a "Please configure the stub status module in Nginx server conf file" warning message?
This warning appears because the stub status module is not enabled in your Nginx configuration, which is required for Applications Manager to monitor the Nginx server. To enable the stub status module in Nginx:
- Navigate to '<NGINX_HOME>/conf' directory and open 'nginx.conf' file present there,
- Add the following code snippet within the scope of the server :
- location /nginx_status {
- stub_status on;
- access_log off;
- allow all;
- # deny all;
- }
Making the above changes will open the /nginx_status handler with no restrictions. To restrict access only to the Applications Manager, make the following changes to the configuration:location /nginx_status {
stub_status on;
access_logs off;
allow <ip_of_apm_installed_machine>;
deny all;
}
- Save and restart the Nginx web server to apply the changes.
After completing these steps, the stub status module will be activated, and the warning in Applications Manager should no longer appear.
Still facing issues?
If the problem persists, contact our support team along with the following details:
- A screenshot of the "Add Monitor" page.
- The URL debug tool response for the Nginx server monitor.
- Reproduce the issue and share the latest Support Information File (SIF) from Applications Manager, with the "Print all logs" option enabled. To do this, go to Settings > Logging, and choose "Print all logs".
New to ADSelfService Plus?
Related Articles
Troubleshooting - Nginx Plus
To troubleshoot Nginx Plus Server Monitor, follow the below steps: Verify Accessibility: Ensure that the Nginx Plus server instance is accessible from the Applications Manager server. Check Host and Port: Make sure you’ve entered the correct host and ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...Troubleshooting Server error responses
When encountering the following server error responses—Bad Gateway (502), Service Unavailable (503), and Gateway Timeout (504)—it typically indicates issues with the server hosting the URL. Troubleshooting Review your server's access logs for the 30 ...How can I execute SybaseDebug.bat/SybaseDebug.sh?
This file is used to check if the connectivity and the Discovery of the Sybase Server is possible from the Applications Manager installed server. This standalone program is a excerpt of the same process we use to add the Sybase Server monitor. The ...PHP Monitor Troubleshooting
PHP Monitor Errors and Troubleshooting Guide Check if the phpstats.php file in the webserver's document root. Ensure there are no modifications done in phpstats.php file Check if the given PHP path is correct. Retry with the "SSL is enabled" option ...