You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a self-signed HTTPS certificate as indicated in https://docs.influxdata.com/influxdb/v2/admin/security/enable-tls/ making sure to include an IP.1 = 10.1.2.3 line between the alt_names and indicate the location of .key and .crt files in /etc/influxdb/config.toml
Restart influxd
Connect (in my case I am connecting to https://10.1.2.3:8086), follow the tutorial and click to Quick Start at its end.
Expected behavior:
Either:
Nothing happens
or:
A scraper gets created and it works. The scraper should get the location of the .crt file as it was indicated in the /etc/influxdb/config.toml file.
Actual behavior:
A "new target" scraper gets created, but it fails due to the certificate.
The scraper gets created by the handleQuickStart function in the src/onboarding/components/CompletionStep.tsx file here.
If the IP.1 line is missing from the OpenSSL config file, this error is flooding the logs every 10 seconds:
host influxd-systemd-start.sh[11782]: ts=2024-09-25T10:13:42.054832Z lvl=error msg="Unable to gather" log_id=0rr6jG30000 service=scraper scraper-name="new target" error="Get "https://10.1.2.3:8086/metrics\": tls: failed to verify certificate: x509: cannot validate certificate for 10.1.2.3 because it doesn't contain any IP SANs"
host influxd-systemd-start.sh[11782]: ts=2024-09-25T10:13:42.054669Z lvl=info msg="http: TLS handshake error from 10.1.2.3:35328: remote error: tls: bad certificate" log_id=0rr6jG30000 service=http
The scraper is filling the system logs with errors like:
host influxd-systemd-start.sh[15260]: ts=2024-09-25T15:53:06.463054Z lvl=error msg="Unable to gather" log_id=0rrOi2Hl000 service=scraper scraper-name="new target" error="Get "https://10.1.2.3:8086/metrics\": tls: failed to verify certificate: x509: certificate signed by unknown authority"
host influxd-systemd-start.sh[15260]: ts=2024-09-25T15:53:06.462927Z lvl=info msg="http: TLS handshake error from 10.1.2.3:52166: remote error: tls: bad certificate" log_id=0rrOi2Hl000 service=http
Visual Proof:
About your environment
Environment info:
# uname -srm
Linux 5.10.180-olimex aarch64
# influxd version
InfluxDB v2.7.10 (git: f302d9730c) build_date: 2024-08-16T20:19:39Z
About the bug
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
IP.1 = 10.1.2.3
line between thealt_names
and indicate the location of .key and .crt files in/etc/influxdb/config.toml
Expected behavior:
Either:
Nothing happens
or:
A scraper gets created and it works. The scraper should get the location of the .crt file as it was indicated in the
/etc/influxdb/config.toml
file.Actual behavior:
A "new target" scraper gets created, but it fails due to the certificate.
The scraper gets created by the
handleQuickStart
function in thesrc/onboarding/components/CompletionStep.tsx
file here.If the IP.1 line is missing from the OpenSSL config file, this error is flooding the logs every 10 seconds:
host influxd-systemd-start.sh[11782]: ts=2024-09-25T10:13:42.054832Z lvl=error msg="Unable to gather" log_id=0rr6jG30000 service=scraper scraper-name="new target" error="Get "https://10.1.2.3:8086/metrics\": tls: failed to verify certificate: x509: cannot validate certificate for 10.1.2.3 because it doesn't contain any IP SANs"
host influxd-systemd-start.sh[11782]: ts=2024-09-25T10:13:42.054669Z lvl=info msg="http: TLS handshake error from 10.1.2.3:35328: remote error: tls: bad certificate" log_id=0rr6jG30000 service=http
The scraper is filling the system logs with errors like:
host influxd-systemd-start.sh[15260]: ts=2024-09-25T15:53:06.463054Z lvl=error msg="Unable to gather" log_id=0rrOi2Hl000 service=scraper scraper-name="new target" error="Get "https://10.1.2.3:8086/metrics\": tls: failed to verify certificate: x509: certificate signed by unknown authority"
host influxd-systemd-start.sh[15260]: ts=2024-09-25T15:53:06.462927Z lvl=info msg="http: TLS handshake error from 10.1.2.3:52166: remote error: tls: bad certificate" log_id=0rrOi2Hl000 service=http
Visual Proof:
About your environment
Environment info:
Config:
Logs:
The text was updated successfully, but these errors were encountered: