-
Notifications
You must be signed in to change notification settings - Fork 114
Description
Describe the bug
Following the documentation to add an instance, there is no mention of the need to configure stub_status, but when running the curl command listed in the docs, the following message is displayed:
- Checking if stub_status is configured ... no stub_status in nginx config, please check https://nginx.org/en/docs/http/ngx_http_stub_status_module.html
A few checks have failed - please read the warnings above!
Additional context
The link provided gives an overview of the command, and we know we need to add it based on the error message, but there isn't enough information provided to understand the relevance or potential additional configuration parameters.
After adding the configuration, the error goes away but when viewing the instance in the dashboard, there's an error stating that stub_status should have an access control list defined. This requires that the user then go search for things like "stub_status acl" to figure out what this should look like.
Creating something like the following appears to work:
location /nginx_status {
stub_status on;
allow 127.0.0.1;
deny all;
}
Sensitive Information
Remember to redact any sensitive information such as authentication credentials or license keys.