lolodomo
commented
1 year ago Please run this command in your console and show us the result: bundle:list -s | grep ui | grep openhab
While I am running a 4.0 snapshot, I get this result:
183 x Active x 80 x 4.0.0.202303170310 x org.openhab.core.io.rest.ui
213 x Active x 80 x 4.0.0.202303170309 x org.openhab.core.ui
214 x Active x 80 x 4.0.0.202303170310 x org.openhab.core.ui.icon
216 x Active x 80 x 4.0.0.202303172211 x org.openhab.ui
217 x Active x 80 x 4.0.0.202303172206 x org.openhab.ui.iconset.classic
274 x Active x 80 x 4.0.0.202303191029 x org.openhab.ui.basicYou should have all these 6 bundles active and all from the same OH version.
Your first log message (enhab.ui.internal.UIErrorPageServlet) is logged by MainUI so I understand that you start Basic UI from MainUI. Can you try to start Basic UI directly, just by entering the URL in your browser ? Something like http://192.xxx.xxx.xxx:8080/basicui/app
PaulL1
wezzix
wborn
Refer this discussion on the community pages: https://community.openhab.org/t/basicui-not-loading-any-css-or-icons-after-reboot/145424
I'm running on a RaspberryPi with Debian and an apt install, currently on 4.0.0.M1.
My install was operating fine, after a reboot the basic UI wasn't delivering any CSS, Javascript or icons, and this is consistent across Safari and Chrome, and both on my laptop and on my phone (unlikely to be a cookie or cache issue). It is delivering the index page, but for all other pages there's a message in the log along the lines of:
Reviewing the javascript console I can see that for files such as manifest.json and the javascript files the actual content returned is the index.html (which is also what the error from the log above says that it's doing).
At that point I suspect I was on an earlier build, but I don't know what exact earlier build. I ran a full upgrade, bringing me to 4.0.0.M1, in the hopes of correcting the issue, but the problem continues to occur.
The iOS app is still rendering properly.
The icon bundle is installed and active, no bundles are reporting inactive. I'm assuming the icon bundle isn't the problem, as javascript and css also are not returned.
These lines from the debug log on startup were the only other things I found in the log that looked maybe relevant. They actually look OK to me, but it did fail to find an activate method - which may be because there isn't supposed to be one, or may be because something is broken.
I suspect a reinstall will fix the problem, but that wouldn't avoid other people getting the same problem. Are there more diagnostics I can usefully perform? I'm assuming the files themselves must be unpacked in a cache somewhere that I could look at to see if the files are potentially missing?