On Tuesday, November 22, 2016 at 7:40:41 PM UTC+2, [email protected] wrote: > I've got my influxdb process reverse-proxied by nginx to provide SSL > authentication. On the host, I'm redirecting host:443 to localhost:8086. So > for instance, this works: > > $ curl --negotiate -u : 'https://<hostname>/query?pretty=true' > --data-urlencode "db=mydb" --data-urlencode "q=SELECT * FROM test" > { > "results": [ > { > "series": [ > { > "name": "test", > "columns": [ > "time", > "value" > ], > "values": [ > [ > "2016-11-22T17:16:20.639034968Z", > 0.6 > ] > ] > } > ] > } > ] > } > > However, this fails (doesn't help to use -unsafeSsl): > > $ ./influx -host <hostname> -port 443 -ssl > > with 'Failed to check token:' > > The authentication scheme is SPNEGO & Kerberos. > > The (deprecated) web console works fine with <hostname>, port=443, and ssl > checked. > > Any thoughts welcome -
Hi, Is the version of Influx cli installed on your system the same as InfluxDB on the server? We've seen this error when trying to connect with older versions of the influx cli (e.g. v0.11) to new installations (v1+). -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/2c4d3793-8abe-4a16-9f27-c7a83316557e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
