scrape insecure not working about nginx-vts-exporter HOT 5 CLOSED

Accessing localhost over HTTPS doesn't make a ton of sense. I would access it over HTTP by running prometheus_nginx_exporter -insecure -nginx.scrape_uri http://localhost/nginx_status_vts.

Accessing a localhost endpoint never leaves the host, so you don't need to worry about unencrypted network traffic. If you're concerned about exposing an unencrypted endpoint on the nginx host, just make sure that the VTS module stats is only listening on localhost.

from nginx-vts-exporter.

Of course you are correct, scraping localhost via ssl doesn't make much sense. I just assumed the error would be the same as scraping some self-signed ssl endpoint.

from nginx-vts-exporter.

Maybe we could consider using -k like curl to do insecure https request?

from nginx-vts-exporter.

yes, i thought thats what the -insecure was for... isn't it?

from nginx-vts-exporter.

support -insecure now, please check the latest release.

from nginx-vts-exporter.