Kibana: weird Error: Parse Error at Error (native)

[talevy]

Kibana version: 5.2.1

Elasticsearch version: 5.2.0

Server OS version: Mac OS 10.12.3

Browser version: Google Chrome 55.0.2883.95

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.):

downloaded MAC from the downloads page

Description of the problem including expected versus actual behavior:

kibana-5.2.1-darwin-x86_64 $ bin/kibana
  log   [23:18:29.303] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [23:18:29.369] [info][status][plugin:[email protected]] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [23:18:29.394] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [23:18:29.419] [warning] You're running Kibana 5.2.1 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatib
ility issues: v5.2.0 @ 127.0.0.1:9200 (127.0.0.1)
  log   [23:18:29.560] [info][status][plugin:[email protected]] Status changed from uninitialized to green - Ready
  log   [23:18:29.566] [info][listening] Server running at http://localhost:5601
  log   [23:18:29.567] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is yellow
  log   [23:18:29.577] [info][status][plugin:[email protected]] Status changed from yellow to green - Kibana index ready
  log   [23:18:29.578] [info][status][ui settings] Status changed from yellow to green - Ready
  log   [23:18:36.928] [error][client][connection] Error: Parse Error
    at Error (native)

Steps to reproduce:

1. launch Elasticsearch
2. launch Kibana
3. hit http://localhost:5601 in browser and look at logs

[talevy]

I just deleted some files, and returned Elasticsearch from

[WARN ][o.e.c.r.a.DiskThresholdMonitor] [TUCZjHQ] high disk watermark [90%] exceeded

to

[INFO ][o.e.c.r.a.DiskThresholdMonitor] [TUCZjHQ] low disk watermark [85%] exceeded on

and now everything runs smoothly

[talevy]

Closing, this was actually caused by accessing https when there was no ssl configured on the Kibana server