-
-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openHAB 2.5 initial dashboard stops if openhab2-addons is installed #1031
Comments
I would assume that this is likely to be a duplicate of #961. Planning to have a closer look at it soon. |
Closing as a duplicate of #961. I hope the workaround explained in #961 (comment) is acceptible for existing 2.5 users. |
It is only acceptable if the Linux Installation and the Download pages are updated with the workaround. When this was discovered as broken months ago the pages should have at least been updated to warn users of breakage. |
The de-installation is not directly related to #961, so I re-open it as it isn't really an exact duplicate, just closely related. I have created openhab/openhab-webui#164 and #1041, which fixes this issue, once 2.5.1 is released. |
Fixed with #1041. |
Does this mean there may be a new snapshot or milestone? |
Even a release. See #961 (comment) and https://community.openhab.org/t/development-of-openhab-3-0-0-and-2-5-x/89376. |
openHAB 2.5 initial dashboard stops if openhab2-addons is installed in a fresh installation
From my testing, it appears this broke sometime between Milestone 1 and Milestone 2.
I tested this with apt packages and manual installs on a Raspberry Pi 3B+.
Removing the addons & OH and then reinstalling OH appears to allow OH to run. In my quick testing I was able to upgrade from M1 to M2 to M3 and still have OH work so this appears to be a fresh installation issue.
We have had several users run into this issue recently. The openhab log just shows the dashboard stopping either before or after LSP starts. OH keeps running but Jetty gives a 404 error for /start/index.
The text was updated successfully, but these errors were encountered: