After updating to Grafana version 4.6.2 (from 4.5.2) datasources became unreachable because of a TLS certificate error, which was resolved by switching on “Skip TLS Verification (Insecure)”.
The error message is as follows:
**redacted** grafana-server: 2017/11/16 15:11:22 http: proxy error: x509: certificate is valid for **hostname redacted**, not localhost **redacted** influxd: 2017/11/16 15:11:22 http: TLS handshake error from [::1]:44042: remote error: tls: bad certificate
We are running grafana + influxdb on a single host. We are using TLS for the connection to the datasource (on localhost), with a selfsigned certificate that is indeed not signed to ‘localhost’, but to the fqdn of the server. In this sense, the error message makes sense. The problem is that the behaviour seems to have changed after the update.
Is this a behaviour that was changed on purpose, and is the intended behavior the one as exhibited in v4.6.2? Or are we dealing with a bug here (as this change effectively temporarily broke our grafana setup)? If this is not intended, i will be glad to file a GitHub issue.
How do i define the “Skip TLS verification” setting through the datasource API? I could not find any documentation on this, but perhaps i overlooked something.
Thanks in advance for looking into this.