[Solved] Can't run reports from Remote Elasticsearch DB

Started by FullyBorked, October 05, 2020, 02:46:39 AM

Previous topic - Next topic
October 05, 2020, 02:46:39 AM Last Edit: October 08, 2020, 12:12:03 AM by FullyBorked
Just reinstalled Sensei to move the Elastisearch DB load to a remote server on my LAN.  The setup went well without error, I can see network traffic into my Elastisearch DB, so it appears to be connecting without issue.  But when I try and run a report it errors out saying that the service isn't running.  However if you navigate to the status page it shows status as 'Running'.  I'm a bit confused on why this isn't working.  Any ideas?

October 05, 2020, 03:01:34 AM #1 Last Edit: October 05, 2020, 03:10:42 AM by FullyBorked
Maybe I don't understand this.  So when you send report data to an external Elasticsearch server it doesn't query that data for reports locally?  It's expected you'll view that data with Kibana?  Why?  Why can't you query reports on the remote Elasticsearch server just as you would remotely. 

Feel like I may have just blown an afternoon here...

EDIT: Looks like based on the replies in this thread https://forum.opnsense.org/index.php?topic=19266.0 it should work just fine and not require Kibana.  So I guess it's just broken for some reason.  Maybe reporting is still pointed at the local Elasticsearch instance?

Hi @FullyBorked,

This might be related to a bug in TLS authentication /w Elasticsearch.

Stay tuned. 1.6.1 is shipping today/tomorrow with fixes.

Quote from: mb on October 05, 2020, 05:19:41 PM
Hi @FullyBorked,

This might be related to a bug in TLS authentication /w Elasticsearch.

Stay tuned. 1.6.1 is shipping today/tomorrow with fixes.
Ok thanks.  I'll hold tight and be patient [emoji16].

Sent from my GM1917 using Tapatalk


I can confirm 1.6.1 fixed my reporting issue.