If your nginx doesn’t listen http (e.g. 127.0.0.1 port 80), if it’s only SSL, then the subject needs to be fully qualified in order to match the certificate presented SSL wise.
Hello @cjcox and @mace, @cjcox Yep i know the what is the reason and nginx is listening on both HTTP and HTTPS, but i need a way to bypass it because it’s not logical …, @mace i tried your pull request the error is gone but the plugin is not returning any data, even tho if i do wget -qO - http://127.0.0.1/nginx_status
the answer is:
Active connections: 20
server accepts handled requests
130935 130935 196748
Reading: 0 Writing: 1 Waiting: 19
Found the issue the script was trying to auto discover nginx on localhost:443 and not localhost:80, even tho the configuration in nginx is on port 80.
It was not noticing the nginx_status.cfg because i was calling it nginx_status.conf lol… devs… some wants to call the file cfg and other wants to call it conf and we system engineers have to suffer