Dashing Icinga2 - no icingaweb data shown


Hello there,

i just set up dashing-icinga2 and followed the installation guide step by step:

I installed it on a raspberry pi 3.
Icingaweb2 is running with https and I already added the certificate authority to the chromium browser on the pi.

The API data are shown correctly but it seems, that there is a problem with data from icingaweb?
This is what it looks like:

This is how it should look like:

On my icinga master, the icinga2.log shows:

[2019-03-27 10:13:30 +0100] information/ApiListener: New client connection from []:40562 (no client certificate)
[2019-03-27 10:13:30 +0100] information/HttpServerConnection: Request: GET /v1/status/CIB (from []:40562), user: dashing)
[2019-03-27 10:13:30 +0100] information/HttpServerConnection: HTTP client disconnected (from []:40562)

the /usr/share/dashing-icinga2/log/thin.log shows:

First trying to read environment variables
Environment variables not found, falling back to configuration file config/icinga2.json
Detecting local config file ‘/usr/share/dashing-icinga2/config/icinga2.local.json’.
Using config file ‘/usr/share/dashing-icinga2/config/icinga2.local.json’.
Reading config{“icinga2”=>{“api”=>{“host”=>“”, “port”=>5665, “user”=>“dashing”, “password”=>“MyPassword”}}, “icingaweb2”=>{“url”=>“”}} - - [27/Mar/2019 08:48:04] “GET /icinga2 HTTP/1.1” 200 3715 0.0274 - - [27/Mar/2019 08:48:04] “GET /events HTTP/1.1” 200 - 442.9936 - - [27/Mar/2019 08:48:05] “GET /views/list.html HTTP/1.1” 200 613 0.0028 - - [27/Mar/2019 08:48:05] “GET /views/meter.html HTTP/1.1” 200 375 0.0062 - - [27/Mar/2019 08:48:05] “GET /views/simplelist.html HTTP/1.1” 200 358 0.0040 - - [27/Mar/2019 08:48:05] “GET /views/iframe.html HTTP/1.1” 200 52 0.0032

Any ideas? Any help is much appreciated!

My Versions:

dashing (1.3.7)
ruby 2.3.3p222 (2016-11-21) [arm-linux-gnueabihf]
icinga2 - The Icinga 2 network monitoring daemon (version: r2.10.2-1)
git show -1
commit 69f40895bab9219e3a03b4ebbe25534cea0cb892
Author: Michael Friedrich michael.friedrich@icinga.com
Date: Thu Mar 21 16:44:57 2019 +0100


It has been a while since I set up a dashing instance.
Something in the back of my head says “iframes don’t support login information” but normally there was just the login interface of icingaweb2 visible.
Is there anything blocking/rejecting the connection to the webserver?

I’m neither an expert for dashing nor webservers, so sorry for the lame answer :smiley:

1 Like

Yes, it is definately an iFrame issue:

I was able to “solve” this by installing a chrome plugin which completely disables any iFrame Header checks.
So it works for now, but as soon as the plugin will not be available anymore, it will break i guess