regilero

We can try several things. - First, do you have any HTTP Authorization in place? user/password requested? - Next thing, does a manual HTTP connect from the monitoring server works,...

Yes, shinken is irrevelant. Plugins should be able to run with command line without any problem. So it looks more like a bug with https connection managmenet in perl's LWP...

But it's like your SSL certificate was not using the right name. Which is not the case, I think. So it's more that Perl doesn't know how to check for...

From an external server I get a 403 erverytime. Verify that your nginx virtualhosts are defined on the same IP. Could be that the virtualhost working on port 80 works...

Yes, thanks for details. But a wildcard certificate is maybe a good hint on the problem. SSL negociation, by default, works better with single name virtualhosts, as it happens before...

OK, thanks for the detective work. I hope you have a working configuration, at least.

Note that your /status url reports php_fpm status and not nginx status. See my other nagios script https://github.com/regilero/check_phpfpm_status for php_fpm report analysis. This nginx check should instead request the nginx...

Could you please test the latest commit fix : https://github.com/regilero/check_nginx_status/commit/75d8e5c72525a613c520bc3cf6c3cb3e87ecdac0 And still tests it on the bad status url to see if the divide by zero crash is removed?

Maybe we should add somme command line options, to rename metrics, or to add one prefix on all metrics.

Sauf que à ce niveau là on peut se dire que l'erreur vient du collecteur de données, qui devrait être capable de former plusieurs graphes à partir d'une collecte de...