I installed InfluxDB 2.7.6 on Rocky Linux , every thing works fine except for Web UI. I checked http://hostname:8086, but its not working, not trace on logs as well.
Is there any specific config to enable web ui?
Thank You
Manu
@vmanojv The UI is enabled by default, but it can be disabled using the ui-disabled config option. Are you setting this option in your configuration at all?
What error code do you get in your browser when you visit http://hostname:8086?
I installed using rpm, did not use any option to disable UI.
Below error on browser:
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.
Thank You
Manoj
Ok, that’s just the messaged generated by the browser. Just to make sure, can you provide the response from the following command (assuming you have cURL installed)?
curl http://hostname:8086/health
I am getting ready message, as below:
{“name”:“influxdb”, “message”:“ready for queries and writes”, “status”:“pass”, “checks”:, “version”: “v2.7.6”, “commit”: “3c58c06206”}
Ok, InfluxDB is indeed running. What are the contents of /etc/influxdb/config.toml?
cat /etc/influxdb/config.toml
bolt-path = “/data/influxdb/influxd.bolt”
engine-path = “/data/influxdb/engine”
tls-cert = “/etc/ssl/certs/influx.crt”
tls-key = “/etc/ssl/certs/influx.key”
Ok, so based on the information you’ve provided above, you’re running on a non-default host (localhost), so I think you need to configure the hostname to use in your InfluxDB configuration file using the http-bind-address configuration option:
bolt-path = "/data/influxdb/influxd.bolt"
engine-path = "/data/influxdb/engine"
tls-cert = "/etc/ssl/certs/influx.crt"
tls-key = "/etc/ssl/certs/influx.key"
http-bind-address = "hostname:8086"
After updating your configuration file, restart the InfluxDB service to apply the change and see if the UI works.
Stil no luck, also dont see any error trace in logs.
I tried in one more box, same result.
Anyone ever get a resolution to this? I’m encountering the same issue. Here’s some detail for my setup:
# influx server-config --skip-verify --host https://influx.lan:8086
{
"assets-path": "",
"bolt-path": "/var/lib/influxdb/influxd.bolt",
"e2e-testing": false,
"engine-path": "/var/lib/influxdb/engine",
"feature-flags": null,
"flux-log-enabled": false,
"hardening-enabled": false,
"http-bind-address": ":8086",
"http-idle-timeout": 180000000000,
"http-read-header-timeout": 10000000000,
"http-read-timeout": 0,
"http-write-timeout": 0,
"influxql-max-select-buckets": 0,
"influxql-max-select-point": 0,
"influxql-max-select-series": 0,
"instance-id": "",
"log-level": "info",
"metrics-disabled": false,
"nats-max-payload-bytes": 0,
"nats-port": 0,
"no-tasks": false,
"pprof-disabled": false,
"query-concurrency": 1024,
"query-initial-memory-bytes": 0,
"query-max-memory-bytes": 0,
"query-memory-bytes": 0,
"query-queue-size": 1024,
"reporting-disabled": false,
"secret-store": "bolt",
"session-length": 60,
"session-renew-disabled": false,
"sqlite-path": "/var/lib/influxdb/influxd.sqlite",
"storage-cache-max-memory-size": 1073741824,
"storage-cache-snapshot-memory-size": 26214400,
"storage-cache-snapshot-write-cold-duration": "10m0s",
"storage-compact-full-write-cold-duration": "4h0m0s",
"storage-compact-throughput-burst": 50331648,
"storage-max-concurrent-compactions": 0,
"storage-max-index-log-file-size": 1048576,
"storage-no-validate-field-size": false,
"storage-retention-check-interval": "30m0s",
"storage-series-file-max-concurrent-snapshot-compactions": 0,
"storage-series-id-set-cache-size": 0,
"storage-shard-precreator-advance-period": "30m0s",
"storage-shard-precreator-check-interval": "10m0s",
"storage-tsm-use-madv-willneed": false,
"storage-validate-keys": false,
"storage-wal-fsync-delay": "0s",
"storage-wal-max-concurrent-writes": 0,
"storage-wal-max-write-delay": 600000000000,
"storage-write-timeout": 10000000000,
"store": "disk",
"strong-passwords": false,
"template-file-urls-disabled": false,
"testing-always-allow-setup": false,
"tls-cert": "/etc/ssl/influxdb-selfsigned.crt",
"tls-key": "/etc/ssl/influxdb-selfsigned.key",
"tls-min-version": "1.2",
"tls-strict-ciphers": false,
"tracing-type": "",
"ui-disabled": false,
"vault-addr": "",
"vault-cacert": "",
"vault-capath": "",
"vault-client-cert": "",
"vault-client-key": "",
"vault-client-timeout": 0,
"vault-max-retries": 0,
"vault-skip-verify": false,
"vault-tls-server-name": "",
"vault-token": ""
}
I would like to point out that this command works from the local influx machine using skip-verify and https arguments.
journalctl -u influxdb.service
Oct 14 19:44:55 influx influxd[124]: ts=2024-10-14T19:44:55.650543Z lvl=info msg="http: TLS handshake error from 192.168.1.54:57594: remote error: tls: bad certificate" log_id=0sDqkZh0000 service=http
Connecting to the server via curl on a remote system:
curl --verbose --insecure https://192.168.1.54:8086/api/v2/ping
* Trying 192.168.1.54:8086...
* Connected to 192.168.1.54 (192.168.1.54) port 8086
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: C=US; ST=State; L=Town; O=Organization; OU=IT Department; CN=domain.com
* start date: Oct 9 20:31:52 2024 GMT
* expire date: Jul 30 20:31:52 2027 GMT
* issuer: C=US; ST=State; L=Town; O=Organization; OU=IT Department; CN=domain.com
* SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://192.168.1.54:8086/api/v2/ping
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: 192.168.1.54:8086]
* [HTTP/2] [1] [:path: /api/v2/ping]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET /api/v2/ping HTTP/2
> Host: 192.168.1.54:8086
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/2 401
< content-type: application/json; charset=utf-8
< x-influxdb-build: OSS
< x-influxdb-version: 2.7.10
< x-platform-error-code: unauthorized
< content-length: 55
< date: Mon, 14 Oct 2024 19:48:27 GMT
<
* Connection #0 to host 192.168.1.54 left intact
{"code":"unauthorized","message":"unauthorized access"}
It connects and is unauthorized, but TLS error “bad certificate” isn’t present on this request.
Oct 14 19:48:27 influx influxd[124]: ts=2024-10-14T19:48:27.603520Z lvl=info msg=Unauthorized log_id=0sDqkZh0000 error="token required"
Connecting from a web browser, on the same machine as the curl command above:
Safari Can't Open the Page
Safari can't open the page "https://192.168.1.54:8086" because Safari can't establish a secure connection to the server "192.168.1.54".
Log messages:
Oct 14 19:53:33 influx influxd[124]: ts=2024-10-14T19:53:33.505929Z lvl=info msg="http: TLS handshake error from 192.168.1.44:54138: remote error: tls: illegal parameter" log_id=0sDqkZh0000 service=http
Oct 14 19:53:33 influx influxd[124]: ts=2024-10-14T19:53:33.650810Z lvl=info msg="http: TLS handshake error from 192.168.1.44:54140: remote error: tls: illegal parameter" log_id=0sDqkZh0000 service=http
Oct 14 19:53:33 influx influxd[124]: ts=2024-10-14T19:53:33.797609Z lvl=info msg="http: TLS handshake error from 192.168.1.44:54141: remote error: tls: illegal parameter" log_id=0sDqkZh0000 service=http
Oct 14 19:53:33 influx influxd[124]: ts=2024-10-14T19:53:33.950257Z lvl=info msg="http: TLS handshake error from 192.168.1.44:54142: remote error: tls: illegal parameter" log_id=0sDqkZh0000 service=http
Oct 14 19:53:34 influx influxd[124]: ts=2024-10-14T19:53:34.096421Z lvl=info msg="http: TLS handshake error from 192.168.1.44:54143: remote error: tls: illegal parameter" log_id=0sDqkZh0000 service=http
Oct 14 19:53:34 influx influxd[124]: ts=2024-10-14T19:53:34.243543Z lvl=info msg="http: TLS handshake error from 192.168.1.44:54144: remote error: tls: illegal parameter" log_id=0sDqkZh0000 service=http
Oct 14 19:53:34 influx influxd[124]: ts=2024-10-14T19:53:34.390152Z lvl=info msg="http: TLS handshake error from 192.168.1.44:54145: remote error: tls: illegal parameter" log_id=0sDqkZh0000 service=http
Oct 14 19:53:34 influx influxd[124]: ts=2024-10-14T19:53:34.536808Z lvl=info msg="http: TLS handshake error from 192.168.1.44:54146: remote error: tls: illegal parameter" log_id=0sDqkZh0000 service=http
❯ telnet 192.168.1.54 8086
Trying 192.168.1.54...
Connected to influx.lan.
Escape character is '^]'.
GET /
HTTP/1.0 400 Bad Request
Client sent an HTTP request to an HTTPS server.
Connection closed by foreign host.
I’m running this in development for a large service provider proof of concept that might lead to an enterprise purchase. But this is a pretty minor thing to have go so terribly wrong.
