Messages

More information from my setup as well.

I have configured an external ES DB after upgrading Zenarmor to 1.14.2. It basically works but some reports don't display data.

These reports are:

• Egress New Connections by App Over Time
• Egress New Connections by Source Over Time
• New Connections & Unique Remote Hosts
• Unique Local Hosts
• Facts/Connections is set to NaN
• Facts/unique Local Devices is set to 0
• HTTP Transactions by Source Over Time
• Top Egress Users
• Top Ingress Users
• Top OS
• Top Session Creators Over Time
• Top Servers Over Time

I would expect to see data in at least some of them.
One more factor that can make a difference is the fact I use custom lifecycle policy and custom index names in ES. However I've made sure all mappings are defined exactly the same way as indices created by Zenarmor during the installation process.

Hey there,

same thing in my router. I believe the problem is that the frontend now tries to access the zenarmor API using the router LAN IP address instead of the URL address of the router GUI.

In my case I access the router with the URL: https://my.awesome.router which is secured with a letsencrypt certificate. The Zenarmor client though tries to use the URL https://192.168.1.1/api/zenarmor which of course leads to an invalid certificate error and prevents the client from getting to an access token.

Is there any configuration setting available which allows us to set the URL of the Zenarmor API backend?