No flux when https enabled

Hello,
once https is enabled FLUX is not available: “the current source doesn’t support Flux”

Please help

Thank you

Hi @monitoring.it.ak,

Just to confirm, is this with InfluxDB 2?

Hello, rawcode.

No, it’s 1.X as 2.0 is in beta

Influxdata team,
any ideas, please? I just want to find pros for your product to find it’s place in my company. If we don’t have FLUX enabled we need to find something else.

-AK

Even more:

grep “insecure” /etc/influxdb/influxdb.conf
insecure-skip-verify = true

~$ influx -ssl -unsafeSsl -type=flux -username=monitoring -password=monitoring -host=monitoring2
Connected to https://monitoring2:8086 version 1.7.9 InfluxDB shell version: 1.7.9 from (bucket:"telegraph") Error: Post https://monitoring2:8086/api/v2/query: x509: certificate signed by unknown authority

~$ sudo sed -i -s “s/insecure-skip-verify = true/insecure-skip-verify = false/” /etc/influxdb/influxdb.conf

~$ grep “insecure” /etc/influxdb/influxdb.conf
insecure-skip-verify = false

~$ influx -ssl -unsafeSsl -type=flux -username=monitoring -password=monitoring -host=monitoring2
Connected to https://monitoring2:8086 version 1.7.9 InfluxDB shell version: 1.7.9

from(bucket:"telegraf") Error: Post https://monitoring2:8086/api/v2/query: x509: certificate signed by unknown authority aggregateWindow

So, here is the same answer with insecure_skip_verify = false/true

This one works fine:

`~$ curl -k “https://monitoring2:8086/api/v2/query?u=monitoring&p=monitoring” -XPOST -sS -H ‘accept:application/csv’ -H ‘content-type:application/vnd.flux’ -d ‘from(bucket:“telegraf”) |> range(start:-5m) |> filter(fn:® => r._measurement == “cpu”)’ | more
#datatype,string,long,dateTime:RFC3339,dateTime:RFC3339,dateTime:RFC3339,double,string,string,string,string
#group,false,false,true,true,false,false,true,true,true,true
#default,_result,
,result,table,_start,_stop,_time,_value,_field,_measurement,cpu,host
,0,2020-01-26T10:52:32.731603758Z,2020-01-26T10:57:32.731603758Z,2020-01-26T10:52:42Z,0,usage_guest,cpu,cpu-total,monitoring2
,0,2020-01-26T10:52:32.731603758Z,2020-01-26T10:57:32.731603758Z,2020-01-26T10:52:52Z,0,usage_guest,cpu,cpu-total,monitoring2
,0,2020-01-26T10:52:32.731603758Z,2020-01-26T10:57:32.731603758Z,2020-01-26T10:53:02Z,0,usage_guest,cpu,cpu-total,monitoring2

Ok,
answergin to my question by myself:

You have a bug in 1.7: