Page 2 of 2
Re: Dashboard Issues
Posted: Mon Mar 31, 2025 9:02 am
by TheCooDave
Agreement here. I rolled back because they were broken.
Any updates on this issue?
Re: Dashboard Issues
Posted: Mon Mar 31, 2025 9:26 am
by sgardil
gregbeyer wrote: ↑Mon Mar 24, 2025 9:27 am
I can corroborate that upgrade to 2024R1.4.1 has totally hosed my dashboards.
Thank God I tried it out on DEV first. PITA to have to rebuild my DEV box and restore from backup, but better than having my PROD box hosed.
In my home dashboard only Host Status Summary and Service Status summary are somewhat readable, tho they did reduce in size. All other dashlets are shrunk down to 1/2 postage stamp size. So small cannot access dashlet controls to bring them back up to size.
Another dashboard, when I open it, red message at top " Error: Access denied due to cross-origin policy or content security policy." I'm an admin, of course so what gives?. And all of that dashboard's dashlets are scaled to huge and moved around. Or are they just so huge that they just
look like they moved? IDK.
Yeah, not upgrading PROD 'til this is fixed. Apologies to Forrest Gump. Nagios is like a box of chocolates . . .
For the cors issues, do you know if it persists after restarting your apache server? Also I'm assuming this only started happening after the update? It is a weird issue and im not sure what exactly is causing it. If it just recently happened I can take a look at some of the changes that were done and see if something is causing cors issues there. Unfortunately I don't have an update yet for the dashboard issue yet. I can't go into details for the dashboard changes that were made but we apologize for the inconvenience.
Re: Dashboard Issues
Posted: Mon Mar 31, 2025 11:16 am
by gregbeyer
"cors " <-- IDK what you're referring to.
My usual 1st go-to when having Nagios trouble is restarting nagios, httpd, mysqld and nrpe, but to be honest, I'm not sure that I cycled httpd in this case -- so don't want to mislead you.
Correct -- this manifested after update to ver 1.4.1. Dashboards were (and are again) fine in ver 1.3. In the meantime I have restored my dev to v1.3.
Thanks for the update. It sound like there are a number of folks who would like to see updates as progress is made.
Re: Dashboard Issues
Posted: Tue Apr 01, 2025 9:25 am
by bpennin
Any timeline on fixing this issue?
Re: Dashboard Issues
Posted: Tue Apr 01, 2025 10:30 am
by sgardil
So CORS is a system that allows browsers to access things from different origins. I'm assuming you have a custom url dashlet that is giving this error? We know of an issue for the dashlet when even accessing same origin requests. One of the recent changes made it so we display an error rather than display a page cannot be reached screen. Out of curiosity do you have SSL set up and are getting this issue? The issue should be fixed with issue number #1781 in our changelog.
Unfortunately I can't give a timeline for fixing the dashboard issues that are mentioned.
Re: Dashboard Issues
Posted: Tue Apr 01, 2025 10:41 am
by bpennin
My issues are host group dashboards that re-size on their own regardless of using the corner re-size drag or browser. I can change everything on the dashboard and log out and back in and all changes are gone and random re-sizing happens.
Re: Dashboard Issues
Posted: Tue Apr 01, 2025 2:30 pm
by gregbeyer
I'm assuming you have a custom url dashlet that is giving this error?
I am using the custom URL dashlet to call a URL
within Nagios,namely BPI (https://<FQDN>/nagiosxi/includes/components/nagiosbpi/index.php)
So you're saying that CORS handling explains the error message "Error: Access denied due to cross-origin policy or content security policy? And #1781 is the answer to that.
I take it there's something else going on that breaks other dashlets too? (in my case used BBMap and Gauge).
Reading the change log, it appears that 2024R1.3.3 was the last version before dashlets were altered. Hard to say at what ver thereafter this dashlet breakage happens. Holding off on upgrading until this issue is resolved.
Re: Dashboard Issues
Posted: Wed Apr 02, 2025 9:47 am
by sgardil
gregbeyer wrote: ↑Tue Apr 01, 2025 2:30 pm
I'm assuming you have a custom url dashlet that is giving this error?
I am using the custom URL dashlet to call a URL
within Nagios,namely BPI (https://<FQDN>/nagiosxi/includes/components/nagiosbpi/index.php)
So you're saying that CORS handling explains the error message "Error: Access denied due to cross-origin policy or content security policy? And #1781 is the answer to that.
I take it there's something else going on that breaks other dashlets too? (in my case used BBMap and Gauge).
Reading the change log, it appears that 2024R1.3.3 was the last version before dashlets were altered. Hard to say at what ver thereafter this dashlet breakage happens. Holding off on upgrading until this issue is resolved.
Correct, there is an issue currently with the custom url dashlet pointing to internal sources and that issue should fix it when released. The confusing part is that when an error happens its displaying a CORS error even when its an internal source.
Yeah dashboards and dashlets have been the focus of recent releases and there has been some changes that were made that changed the resizing functionality to also scale the contents of the dashlets which is very likely causing the issues users are seeing with dashboards being changed and resized.
Feel free to post any breaking changes you see with your dashboards so we can be sure to check for them for a potential fix.