Influx command does not work with TLS enabled

InfluxDB 2
1

Hi! I activated the TLS for influxdb and now i’m getting

influx ping
Error: 400 Bad Request: unable to decode response content type ""

as soon as i disable TLS everything is ok:

influx ping
OK

influx bucket ls
ID                      Name            Retention       Shard group duration    Organization ID         Schema Type
cf35cf3aa13be582        ISS-DC          87600h0m0s      168h0m0s                f358a0d0eae1f003        implicit
b5a214364898ba30        _monitoring     168h0m0s        24h0m0s                 f358a0d0eae1f003        implicit
31a24a3490c2d3c5        _tasks          72h0m0s         24h0m0s                 f358a0d0eae1f003        implicit

is there any special setting for usage of the cli client when TLS is active?
Thanks a lot!

2

Hi @AdrianSevcenco, I have the same issue in a new InfluxDBv2 OSS installation. I’m stuck at this point; I can’t find the problem. As a year has passed, have you been able to fix it? Do you have any hints that you can share with me? I appreciate any help you can provide.

Thanks!

3

Hi, I found the solution in this post: Error: failed to xxxxxxxx : 400 Bad Request: unable to decode response content type "" · Issue #337 · influxdata/influx-cli · GitHub I’m using self-signed certs. I had to modify my config file ( ~/.influxdbv2/configs ), changing the URL parameter to https instead of http and using the --skip-verify argument for the influx command. Now it works.