Closed BastienDurel closed 1 year ago
(I removed TLS errors from logs : it turns ou it was from a co-worker browser using the IP of the server instead of its FQDN, therefore the certificate was invalid)
hey @BastienDurel we have manged to reproduce this I believe. Working on a fix now
Fixed in latest commit just need to create a new release
Thanks ! :)
The workaround to this bug is to ensure you have configured the logging options in the meerkat config. The icinga logging check has faulty logic.
Thanks ! :)
Hello, a newly installed meerkat on a newly-installed debian 12 panics after a few requests
When I'm starting the meerkat server, I can refresh my dashboard once, and after that http2 crashes and it's broken
Logs
Browser console :
Desktop
Additional context As long as I don't reload the dashboard page, updates flows correctly, but the first reload causes the panic, and every subsequent load shows the broken page & panics in logs. (even with another browser) The crash happens too if I open the dashboard in another browser