I'll reply on the GitHub issue thread as well, but I wanted to follow up here for the rest of the community.
It sounds like the primary issue occurs when HTTPS is enabled for the admin interface (running on 8083), but not for the write/query API (port 8086). This means that your browser running on a secure connection has to make a non-secure call to issue queries. This is blocked by most browsers for security reasons, and will result in different error messages depending on the browser. The guidance here is that if you enable HTTPS for your admin interface, you should always also enable it on your API. (Besides, if you don't enable it on both, you're still operating over an insecure connection.) Furthermore, once you enable HTTPS on the admin UI, trying to load the page over plain HTTP will result in an empty response. Some browsers will respond with the 0-byte `download` file you mentioned. This is because the server is expecting an HTTPS connection, which the browser is not initiating. I created a self-signed cert and verified that everything works correctly when HTTPS is respected properly, so I don't think there's anything to be fixed here. The quick summary is that if you're going to enable HTTPS anywhere, you should probably enable it everywhere. Let me know if there are any issues I missed here. Todd On Monday, June 6, 2016 at 11:56:00 PM UTC-7, Willem D'Haese wrote: > > Sean, > > Made the issue. https://github.com/influxdata/influxdb/issues/6797 > > Just wanted to say that I did enable https for 8086 and which does make it > possible to connect from the admin gui, but only when checking the ssl > checkbox. > > Grtz > > On Monday, 6 June 2016 17:32:26 UTC+2, Sean Beckett wrote: >> >> Sounds to me like a bug with HTTPS and the admin interface. Can you open >> a new issue on GitHub <https://github.com/influxdata/influxdb/issues/new> >> ? >> >> On Mon, Jun 6, 2016 at 7:45 AM, Willem D'Haese <[email protected]> >> wrote: >> >>> Just a little more information. it seems after a shift-refresh the http >>> admin gui is no longer reachable. Although it does results in a weird >>> behaviour I haven't seen before: >>> >>> In Chrome a 'download' file is downloaded with contents (see screenshot) >>> and in Firefox it shown in the browser as seen in the second part of the >>> screenshot.. >>> >>> >>> <https://lh3.googleusercontent.com/-chVRvMzewuA/V1V-jHwYlpI/AAAAAAAAFdU/2CSS9xwKGtY9pGzuAk9lqlYdqA7UR78MgCLcB/s1600/InfluxDB_Admin2.PNG> >>> >>> >>> I'm on InfluxDB version v0.13.0. >>> >>> Grtz >>> >>> Willem >>> >>> >>> On Monday, 6 June 2016 15:08:09 UTC+2, Willem D'Haese wrote: >>>> >>>> Hello, >>>> >>>> I configured ssl for my InfluxDB admin interface. We have a private pki >>>> and generated our own certificates. This is the InfluxDB relevant config >>>> part: >>>> >>>> [admin] >>>> enabled = true >>>> bind-address = ":8083" >>>> https-enabled = true >>>> # https-certificate = "/etc/ssl/influxdb.pem" >>>> https-certificate = "/etc/ssl/certs/certidb_2016_sha256_full.pem" >>>> >>>> [http] >>>> enabled = true >>>> bind-address = ":8086" >>>> auth-enabled = true >>>> log-enabled = true >>>> write-tracing = false >>>> pprof-enabled = false >>>> https-enabled = false >>>> https-certificate = "/etc/ssl/influxdb.pem" >>>> >>>> The above config effectively enabled me to login the admin web >>>> interface over HTTPS. But whatever I do in the 'connection settings' >>>> panel, >>>> I seem unable to connect to my server on port 8086. When I browse to the >>>> admin interface over http, I can connect to the server with the same >>>> credentials.... >>>> >>>> As I would like to wait a bit before enabling https for 8086, I was >>>> wondering if it's normal that I can't connect from admin interface over >>>> https to 8086. >>>> >>>> Another small question I had while debugging this => Is there a way to >>>> disable the 'http' (non-ssl) admin interface? I was expecting it would >>>> redirect once I set enabled to true. >>>> >>>> >>>> <https://lh3.googleusercontent.com/-4FkB6IGNfzQ/V1V1gBqY-0I/AAAAAAAAFbg/uZdweQpjzpYgvGOqI8_vvq8coTaKHzQPgCLcB/s1600/InfluxDB_Admin.PNG> >>>> >>>> >>>> Grtz >>>> >>>> -- >>> Remember to include the InfluxDB version number with all issue reports >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "InfluxDB" 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/5521dd8a-8513-4bc5-9cfe-20c29fb8ba42%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/influxdb/5521dd8a-8513-4bc5-9cfe-20c29fb8ba42%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Sean Beckett >> Director of Support and Professional Services >> InfluxDB >> > -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" 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/6a26860d-31fa-4ed6-9625-c87a5f46c863%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
