Upgrade from 3.2 to 4.1 -> web requests from local network to 8080 are denied

Hi
I just tried to upgrade from 3.2 to 4.x (latest, I think 4.1 that is).

My Environment

Problem.
When I start the container everything seems to look fine, although I cannot connect to openhab from local network like it was possible before the update. http://192.168.178.32:8080 returns:

Die Website ist nicht erreichbar

192.168.178.32 hat die Verbindung abgelehnt.

I can connect other docker containers via the same browser in the same network though.

Analysis

chrome_2023-12-27_12-49-48

chrome_2023-12-27_12-50-15

When I configured it to use bridge I set the 8080 container port to local port 8080.

image

putty_2023-12-27_12-53-32

chrome_2023-12-27_12-54-05

chrome_2023-12-27_12-54-23

Contents of the upgrade log:

Image and userdata versions differ! Starting an upgrade.
You can find backup of userdata in /openhab/userdata/backup/userdata-2023-12-27T09-23-34.tar

################################################
          openHAB Docker update script          
################################################

The script will attempt to update openHAB to version 4.1.0
Please read the following e[32mnotese[m and e[31mwarningse[m:

Important notes for version 3.3.0:
  e[31mWarning:e[m  BMW ConnectedDrive Binding: BMW replaced ConnectedDrive Smartphone App with MyBMW Application. Underlying API is now disabled and the Binding isn't working anymore. Switch to new introduced MyBMW Binding recommended.
  e[31mWarning:e[m  Daikin Binding: The channel 'specialmode-powerful' has been removed, and a r/w channel 'streamer' added. The channel 'specialmode' changed to read/write to control eco/powerful mode.
  e[31mWarning:e[m  DanfossAirUnit Binding: The type of the channel 'humidity' was updated. You may need to remove and create your things again in case your things were previously created using UI and you want to use this channel.
  e[31mWarning:e[m  Helios Binding: Firmware versions older than v2.21 are no longer supported.
  e[31mWarning:e[m  JS Scripting Automation: 'item.history.lastUpdate()' returns 'time.ZonedDateTime' instead of 'Date'
  e[31mWarning:e[m  JS Scripting Automation: 'addItem(...)' and 'updateItem(...)' use new itemConfig as parameter and 'createItem(...)' was removed
  e[31mWarning:e[m  MQTT Binding: Support for the MQTT System Broker has been removed. Replace 'mqtt:systemBroker' things with 'mqtt:broker' things.
  e[31mWarning:e[m  Netatmo Binding: Things hierarchy and organization has changed as well as channel namings. You will need to remove and create again these things.
  e[31mWarning:e[m  OmniLink Binding: The channel 'sysdate' has been renamed to 'system_date', and is now read only, to make these changes visible you may need to remove and recreate the `controller` thing. To synchronize the controller time there is now a new action synchronizeControllerTime that can be used with a time zone input (e.g. 'America/Denver').
  e[31mWarning:e[m  Opentherm Gateway Binding: The 'otgw' Thing has been removed and split into a new 'openthermgateway' Bridge, and a new 'boiler' Thing. You will need to change your Thing and respective Item definitions.
  e[31mWarning:e[m  RFXCOM Binding: The channel 'fanSpeed' of 'fan_lucci_dc' and 'fan_novy' has been renamed to 'fanSpeedControl', and 'fan_lucci_dc' has a new numeric channel 'fanSpeed'. You may need to remove and create your things again.
  e[31mWarning:e[m  TapoControl Binding: L510_Series and L530_Series Things were renamed to L510 and L530 because of manufacturer changed naming with new HW-rev. You may need to remove and create again these things.
  e[31mWarning:e[m  WLED Binding: Binding now uses Bridge and Thing structure. Delete and add a new bridge, and at least 1 thing for each segment you require.

Important notes for version 3.4.0:
  e[31mWarning:e[m  CORE: Default units have been added for all dimensions. A state description defining the unit should be added to each item that uses a different unit.
  e[31mWarning:e[m  Automower Binding: Due to Husqvarna Authentication API change, bridge now requires application secret instead of username and password. Delete any existing bridge and re-add it, please make sure to update all automower things to use the newly added bridge.
  e[31mWarning:e[m  JavaScript Scripting Automation: 'setTimeout' and 'setInterval' return a timerId (a positive integer value) as in standard JS instead of an openHAB Timer.
  e[31mWarning:e[m  JavaScript Scripting Automation: ItemHistory min/max between/since returns now a number instead of a string.
  e[31mWarning:e[m  JavaScript Scripting Automation: openHAB JavaScript library versions < 3.1.2 are not fully compatible anymore. If you have manually installed the JS library, please upgrade to a version >= 3.1.2.
  e[31mWarning:e[m  JRuby Scripting Automation: The default `RUBYLIB` directory has changed to OPENHAB_CONF/automation/ruby/lib. Either explicitly configure the add-on to use the previous value, or move any files to the new location.
  e[31mWarning:e[m  Konnected Binding: Things needs to be recreated because of added Konnected Pro panel support and manual configuration of things.
  e[31mWarning:e[m  LG webOS Binding: The undocumented action "sendRCButton" was removed while it is possible to achieve the same action with "sendButton"
  e[31mWarning:e[m  Miele@home Binding: The channel 'start' now contains date and time for start of scheduled program. Previously it was counting down duration until the program would start.
  e[31mWarning:e[m  Miele@home Binding: The channels 'duration', 'elapsed' and 'finish' are now Number:Time. You may need to remove and create your things again in case your things were previously created using UI and you want to use these channels. Linked items need to be recreated.
  e[31mWarning:e[m  Resol Binding: Item Type of solar controllers channels using time and weekday format changed from Date to String. Items need to be adjusted accordingly.
  e[31mWarning:e[m  Systeminfo Binding: Multiple Number channels now have a dimension added. You may need to remove and create your things again in case your things were previously created using UI and you want to use these channels. Linked items need to be recreated.
  e[31mWarning:e[m  Systeminfo Binding: The default state description for DataAmount channels is now MiB. If you relied on MB, you may need to adjust.
  e[31mWarning:e[m  Velux Binding: On window things the semantic category of the position channel has been corrected from 'blinds' to 'window'. Window things with such channels that had been created via the UI will need to be deleted and re-created.
  e[31mWarning:e[m  Xiaomi Wifi devices (Mi IO) Binding: Channel Type change for some yeelights. The brightness channels with the Number type now have the Dimmer type. This affects only nightlight and ambilight channels for some models.

Important notes for version 4.0.0:
  e[31mWarning:e[m  CORE: core.GenericEventTrigger and core.GenericEventCondition parameters have have changed. See https://www.openhab.org/docs/configuration/rules-ng.html#system-module-types.
  e[31mWarning:e[m  CORE: Rules are now triggered by ItemStateUpdatedEvent instead of ItemStateEvent. If you use JSR223 scripting without helper libraries and expect a certain Java type, code changes might be needed.
  e[31mWarning:e[m  CORE: The syntax for an item category/icon in a textual configuration file no longer accepts a value enclosed in quotes. So <temperature> is valid but not <"temperature">. Please update the definition of your items if necessary.
  e[31mWarning:e[m  CORE: SCRIPT transformation has been removed and replaced with language-specific transformations: JS, RB, PY, DSL, GROOVY, etc. See https://www.openhab.org/docs/configuration/transformations.html#script-transformation
  e[31mWarning:e[m  CORE: UoM has been refactored. Please consult https://www.openhab.org/docs/concepts/units-of-measurement.html and https://www.openhab.org/docs/installation/#upgrading BEFORE starting openHAB, otherwise your persisted data may be corrupted.
  e[31mWarning:e[m  Airthings Binding: The channels `radon_st_avg` and `radon_lt_avg` are now of dimension `RadiationSpecificActivity` instead of `Density`. Please update your linked items accordingly.
  e[31mWarning:e[m  Bosch Indego Binding: Due to changes in the cloud services, the authentication method has changed. Please follow the authorization flow described in the documentation. Furthermore, a bridge is now required and must be assigned to the `indego` thing. Configuration of username and password is no longer required/supported.
  e[31mWarning:e[m  ComfoAir Binding: The channel `enthalpy#enthalpyTime` now represents the set time (in minutes) instead of the internal number value that is sent to the device (`minutes / 12`).
  e[31mWarning:e[m  DanfossAirUnit Binding: The deprecated channel 'manual_fan_speed' has been removed. Please use channel 'manual_fan_step' introduced in 3.2.
  e[31mWarning:e[m  Dark Sky Binding: Due to EOL of their API, this add-on has been removed.
  e[31mWarning:e[m  Generac MobileLink Binding: Due to an API change, existing Generator Things will need to be deleted and added again. Additionally, existing Items will need to be adjusted to reflect the updated Generator Thing channels.
  e[31mWarning:e[m  HomeKit: Add-on wide configuration of mappings for thermostat modes is no longer supported. Please use item-level configuration as described in the README.
  e[31mWarning:e[m  Hue emulation: The uniqueid value has been changed to resolve discovery issues with Alexa. You may need to rediscover "devices" in all services that use the hue emulation (Amazon Echo, Logitech Harmony, etc).
  e[31mWarning:e[m  Hunter Douglas (Luxaflex) PowerView Binding: Deprecated scene channels have been removed. Please use the scene channels introduced in 3.2 (in channel group 'scenes').
  e[31mWarning:e[m  JavaScript: JavaScript engines have changed their MIME types: NashornJS is application/javascript:version=ECMAScript-5.1 and GraalJS is application/javascript. Please update your scripts to either make them compatible with GraalJS or change the MIME type to continue to use NashornJS. For Blockly migration, visit the Blockly documentation.
  e[31mWarning:e[m  JavaScript NashornJS: NashornJS has been removed from core and isn't included by default. If you still need or want to use it, you can install it as an addon.
  e[31mWarning:e[m  JavaScript Scripting Automation: The old "metadata" and "itemchannellink" APIs have been replaced by a new API with extended functionality on the "items" namespace.
  e[31mWarning:e[m  JavaScript Scripting Automation: ItemHistory: historicState, maximumBetween, maximumSince, minimumBetween, minimumSince & previousState now return a HistoricItem instead of just the state. previousStateTimestamp has been removed, the timestamp is available on the HistoricItem.
  e[31mWarning:e[m  KNX Binding: Units of Measurements have been introduced, make sure you use correct units in the state description. Rules may need to be adapted. Several items changed from PercentType to QuantityType, i.e. raw values increase by a factor of 100.
  e[31mWarning:e[m  LuftdatenInfo Binding: The binding was renamed to Sensor.Community Binding to match the new naming of the service. Things need to be recreated.
  e[31mWarning:e[m  Netatmo Binding: Due to API authorization process change scheduled on the 2023/04/17 - refresh Token is no more stored in thing configuration, thus can be removed from things config files. If it remains, it'll be ignored.
  e[31mWarning:e[m  Netatmo Binding: New scope has been added for the introduction of the Carbon Monoxide Alarm. Authorization process has to be replayed (and former refreshToken can be removed from things config files -- see above).
  e[31mWarning:e[m  Windcentrale Binding: The binding has been reworked to support the new API that requires authentication. Delete old 'mill' Things, add an 'account' Bridge and add new 'windmill' Things using the 'account' as Bridge. The channel names now follow the naming conventions. Items must be adapted for these changes.

Important notes for version 4.1.0:
  e[31mWarning:e[m  Action Template Interpreter: removed from the distribution, functionality is covered by the Standard Interpreter.
  e[31mWarning:e[m  Energi Data Service Binding: The channels 'net-tariff' and 'transmission-net-tariff' have been renamed to 'grid-tariff' and 'transmission-grid-tariff' respectively. Items should be relinked to the new channels.
  e[31mWarning:e[m  Hue Binding: The auto update policy for API v2 light channels has been changed to avoid multiple state updates. For this to work, you may need to remove and create your things again in case your things were previously created using UI.
  e[31mWarning:e[m  JavaScript Scripting Automation: The "useIncludedLibrary" configuration parameter has been renamed to "injectionCachingEnabled". In case you changed it, make sure to apply that change to the new parameter.
  e[31mWarning:e[m  JDBC Persistence: The add-on now uses H2 database 2.2. If you use H2 for storing data, your database needs to be migrated as described in https://h2database.com/html/migration-to-v2.html. It is also required to add '
  e[31mWarning:e[m  LuxtronikHeatpump Binding: The channel 'controlSignalCirculatingPump' has been changed to type 'Number:Dimensionless'. Items linked to this channel will need to have their Type manually updated.
  e[31mWarning:e[m  Miele@home Binding: The channel 'powerConsumption' has been renamed to 'energyConsumption'. Items should be relinked to the new channel.
  e[31mWarning:e[m  MQTT EspMilightHub Binding: Colour bulbs no longer have a `level` channel. You may need to re-add your things for it to be removed. Link to the `colour` channel instead, even for `Dimmer` items.
  e[31mWarning:e[m  MyBMW Binding: Vehicle channels "charge-info" and "motion" removed, "charge-remaining", "last-fetched", "estimated-fuel-l-100km" and "estimated-fuel-mpg" added. Image options changed - now "VehicleStatus", "FrontView", "RearView", "FrontLeft" and "FrontRight" are available.
  e[31mWarning:e[m  Porcupine Keyword Spotter: removed from the distribution, it was unmaintained.
  e[31mWarning:e[m  Twitter Binding has become X. All related references to Twitter and Tweets have been replaced, please check your configuration (rules, actions, channels etc).


Performing pre-update tasks for version 4.0.2:
  Adding '.bak' to /openhab/userdata/etc/log4j2.xml
  Using default file /openhab/userdata/etc/log4j2.xml
Replacing userdata system files with newer versions...
Clearing cache...

Performing post-update tasks for version 3.3.0:

Performing post-update tasks for version 3.4.0:

Performing post-update tasks for version 4.0.0:
  Replacing: String ,javascript to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String javascript, to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String javascript to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String ,cometvisu-php to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String cometvisu-php, to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String cometvisu-php to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String ,innogysmarthome to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String innogysmarthome, to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String innogysmarthome to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String ,imperihome to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String imperihome, to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String imperihome to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String ,darksky to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String darksky, to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String darksky to  in file /openhab/userdata/config/org/openhab/addons.config

Performing post-update tasks for version 4.1.0:
  Replacing: String actiontemplatehli, to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String ,actiontemplatehli to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String actiontemplatehli to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String ,porcupineks to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String porcupineks, to  in file /openhab/userdata/config/org/openhab/addons.config
  Replacing: String porcupineks to  in file /openhab/userdata/config/org/openhab/addons.config

Starting JSON database update...
[main] INFO org.openhab.core.tools.internal.Upgrader - Copying item unit from state description to metadata in database '/openhab/userdata/jsondb/org.openhab.core.items.Item.json'
[main] INFO org.openhab.core.tools.internal.Upgrader - Stereoanlage1_Power: Could not find thing for channel 'tapocontrol:P110:b305cd4052:54AF977CB69A:energy#actualPower'. Check if you need to set unit metadata.
[main] INFO org.openhab.core.tools.internal.Upgrader - Stereoanlage1_TodayUsage: Could not find thing for channel 'tapocontrol:P110:b305cd4052:54AF977CB69A:energy#todayEnergyUsage'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@737996a0'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Synology_TodayRuntime: Could not find thing for channel 'tapocontrol:P110:c69109542a:energy#todyRuntime'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@61dc03ce'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Kaffeemaschine_EnergyUsage: Could not find thing for channel 'tplinksmarthome:hs110:C689B4:energyUsage'. Check if you need to set unit metadata.
[main] INFO org.openhab.core.tools.internal.Upgrader - Stereoanlage1_TodayRuntime: Could not find thing for channel 'tapocontrol:P110:b305cd4052:54AF977CB69A:energy#todyRuntime'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@50f8360d'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Stereoanlage2_Power: Could not find thing for channel 'tapocontrol:P110:b305cd4052:54AF977CBAB8:energy#actualPower'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@737996a0'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Synology_TodayUsage: Could not find thing for channel 'tapocontrol:P110:c69109542a:energy#todayEnergyUsage'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@12843fce'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Subwoofer_Power: Could not find thing for channel 'tplinksmarthome:hs110:C6A524:power'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@50f8360d'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Stereoanlage2_TodayRuntime: Could not find thing for channel 'tapocontrol:P110:b305cd4052:54AF977CBAB8:energy#todyRuntime'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@50f8360d'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Stereoanlage2_TodayUsage: Could not find thing for channel 'tapocontrol:P110:b305cd4052:54AF977CBAB8:energy#todayEnergyUsage'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@61dc03ce'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Kaffeemaschine_Power: Could not find thing for channel 'tplinksmarthome:hs110:C689B4:power'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@737996a0'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Synology_Power: Could not find thing for channel 'tapocontrol:P110:c69109542a:energy#actualPower'. Check if you need to set unit metadata.
[main] ERROR org.openhab.core.storage.json.internal.JsonStorage - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@12843fce'. Root cause is: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at path $.channels[0]
[main] INFO org.openhab.core.tools.internal.Upgrader - Subwoofer_EnergyUsage: Could not find thing for channel 'tplinksmarthome:hs110:C6A524:energyUsage'. Check if you need to set unit metadata.
[main] INFO org.openhab.core.tools.internal.Upgrader - Upgrading JS profile configuration in database '/openhab/userdata/jsondb/org.openhab.core.thing.link.ItemChannelLink.json'
JSON database updated successfully.


SUCCESS: openHAB updated from 3.2.0 to 4.1.0

Contents of the Protokoll display while runing the container (looks good to me)
I exported the protokoll and converted resulting openhab.html to openhab.txt
openhab.txt (21.0 KB)

Contents from docker inspect openhab:
docker_inspect.txt (15.4 KB)

All logs are empty:
image

What I did already try

  • Removed the container and reinstalled it.
  • I also tried to add openhab container to the network “bridge” as other containers use that also successfully. Then I set the local port 8080 for the container port 8080. No success though

Questions
I already invested hours of investigation and yes I am newbie regarding docker and openhab. I desperately seek help.

  • What could I analyse?
  • I’ve still no clue where I could inspect logs to see what’s happening at the webserver level.

Please use code fences so that it is easier for us to read your long post.
Did you update your OS to bullseye and did you update Java to version 17?

Hi Oliver2,

thanks for your quick response:

As for “code fences”. I put them now in place. Sorry for the wrong edit

As for Update OS to bullseye:
I am not expert, but I work on Synology using DSM and I set the OS to auto update , so yes I think I use the most recent version. And I am not sure whether this is called bullseye?

As for updating to Java 17: From what I understand, the docker image includes all necessary libs. Therefore there should also be java17 be included? Please correct me if I’m wrong.

Furthermore I added some images to my posting to show more details on my setup

Best regards
Hannes

at least it is stated in the openhab.txt/openhab.html file ( + JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64 ).

What about the content of the openhab.log file ?

There is one warning

adduser: Warning: The home directory `/openhab' does not belong to the user you are currently creating.

I am not using docker this is why I do not know if this could have impact: my question would be what are the permissions that are set for this directory ? Does the user have the permissions that are required for that directory ?

All log files are empty:

image

I added openhab user to /openhab:

But this didn’t resolve the issue.

Here are the permissions for the other directories (which were already as shown):
addons:

userdata

only delete right is not given to the user

conf:

same as userdata (only delete is not allowed)

Are you using the „official“ docker image? I yes, that image brings along everything you need, OS, java jdk, openhab. If your script only updated openhab, then it is clear that your instance is not running. You also need to update to bullseye and java 17.

Hi Oliver,

yes I use the official docker image, at least I got it this way:

when clicking on the icon I get here:

image

How would I update to bullseye? Can you point me to a installation instruction for docker? How can I check to be on bullseye?

if your docker container is up to date then according to Docker you are either on debian or on alpine.

Distributions:

  • debian for Debian 11 “bullseye” (default when not specified in tag) (Dockerfile)
  • alpine for Alpine 3.19 (Dockerfile)

Get a linux shell on your synology.
From there do

docker exec -it openhab bash

now you should be in shell in the docker environment. There do

java --version

and

/usr/lib/jvm/java-17-openjdk-amd64/bin/java --version

This should show the default java version and the java version to be found in the JAVA_HOME path.

I tried it but received:

but I can open bash via docker on openhab and execute it there . resulting: in

/usr/lib/jvm/java-17-openjdk-amd64/bin/java --version resulting in
image

Regarding linux distribution in the docker container:

image

That looks good.
Could you double check your users?
I see in one of your screenshots that user openhab is listed twice. Could you also check that user openhab‘s ID is 1031?

Which list are you referring to? Perhaps you see the name openhab twice, one as a group and one as a user like this?

This one

Now I set the privileges to the following:

for openhab directory:

and then for the subdirectories addons, userdata and conf like this:

by taking over the privileges from the openhab directory like this:

Furthermore I ssh’ed on my synology and made sure that there is only one user openhab by:
image

and I checked the openhab group by this:

image

I restarted the openhab server: Makes no difference, still not access on 192.168.178.32:8080

Just to be 100% sure, could you tap and hold on openhab directory until context menu appears, and click on „Auf diesen Ordner, die Unterordner und Dateien anwenden“.
And openhab user‘s id is 1032, right?
Please also run menu 14 of openhabian console which fixes permissions of your project data.
Could you stop openhab.service from command line and start it manually so that we might see some more error messages?

Did as you told me (right click on folder /docker/openhab Eigenschaften → “Auf diesen Ordner, die Unterordner und Dateien anwenden”:

also 1031 is the right user id NOT 1032
image

Regarding “menu 14 of openhabian console”. I run this on docker on synology. I don’t know where to find this?

sudo openhabian-config

run this from command-line

I tried this while ssh’ing on the synology:

image

and in the container:

openhabian-config is NOT available in a standard docker installation. Would be new to me.

1 Like

so I cannot use openhabian-config right?