We ran into an interesting issue. And I don’t know if this is common or not. We upgraded our check_mk instance from v1.6 to v2.0.0p1 and created a shiny new Grafana server as well.
Our check_mk is not yet running https. Our new Grafana server is/was.
This caused the check_mk datasource plugin to not work. And come up with the following message when testing the datasource:
“Could not read API response, make sure the URL you provided is correct.” Nothing else in grafana logging (even with verbosity enabled).
When I disable https in the grafana config, the datasource magically works again. (both check_mk and grafana “unsecure” http)
Have I missed something in documentation or do we have a “weird” config setup (http/https)?
We have put requesting ssl certificates for our check_mk instance higher on our backlog and hopefully this will fix the “issue”.
Mixed content occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.
And e.g. Google Chrome is blocking mixed content since a few versions.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact @fayepal if you think this should be re-opened.