Hi @CrookedJ was just replying to another post and was going to make this one next…Glad you have this solved…Although seems weird that only working in Chrome, as I have a dashboard running at work on my windows 10 PC using IIS and as users are remote desktop only have IE I am forced to use that, and my dashboards work fine.
Sometimes clearing cache can help, or starting stopping the site. More than happy to help you investigate this further if you want but just to let you know it should work in IE.
If you could open the dev tools in IE (F12), you should be able to see if there is an error present. It could be a single control that is causing some weird IE issue.
In terms of IIS hosting, I’m looking to improve that experience. This type of question comes up a lot and I’d rather that it just worked than relying on documenting the correct rain dance you need to perform to get IIS working: https://github.com/ironmansoftware/universal-dashboard/issues/1106
If there are particular documentation items that you found out of date, please let me know. We try to keep the documentation up to date but it’s easy to miss stuff.
Hey thanks for the replies, what tipped me off was the fact that I could get to it remotely (but got the message about not being able to view dashboards remotely in the trial). So I went ahead and installed Chrome and tried that.
It is IE11 on Server 2016. No errors in Console or Network.