Update to 2023.12 can not be finish on Synology OVA

[KILLTROY83]

The problem

Unfortunately, the current update cannot be installed, HOS is running on a synology with ova.

What version of Home Assistant Core has the issue?

2023.12.0

What was the last working version of Home Assistant Core?

2023.11.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

Supervisor:

23-12-07 20:02:23 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNING
23-12-07 20:02:23 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
23-12-07 20:03:17 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2023.12.0
23-12-07 20:03:17 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2023.11.3 to ghcr.io/home-assistant/qemux86-64-homeassistant:2023.12.0
23-12-07 20:03:17 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2023.12.0.
23-12-07 20:07:13 INFO (SyncWorker_2) [supervisor.docker.manager] Stopping homeassistant application
23-12-07 20:07:46 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning homeassistant application
23-12-07 20:07:47 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
23-12-07 20:07:52 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2023.12.0
23-12-07 20:07:52 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
**23-12-07 20:07:57 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-07 20:08:05 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
23-12-07 20:08:05 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!**
23-12-07 20:08:05 INFO (MainThread) [supervisor.resolution.module] Create new issue update_rollback - core / None
23-12-07 20:08:05 INFO (MainThread) [supervisor.homeassistant.core] A backup of the logfile is stored in /config/home-assistant-rollback.log
23-12-07 20:08:05 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2023.11.3
23-12-07 20:08:05 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2023.12.0 to ghcr.io/home-assistant/qemux86-64-homeassistant:2023.11.3
23-12-07 20:08:05 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2023.11.3.
23-12-07 20:08:06 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning homeassistant application
23-12-07 20:08:07 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
23-12-07 20:08:12 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2023.11.3

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration (hassio) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `hassio` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign hassio` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

hassio documentation hassio source _{^{(message by IssueLinks)}}

[dasb00ter]

I am also seeing this. I am trying to update from 2023.11.3 also. I am using synology virtual machine manager and home assistant has been running a couple of years like that. I hope more people chime in. I dont see anything in the logs but I am a manager. Maybe its something fundamental like the version of python

Oh I see read your issue more carefullly its in the supervisor log was expecting in the core log.

[KILLTROY83]

2023.12.1 fails also :(

23-12-09 08:00:44 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-12-09 08:00:44 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
23-12-09 08:00:44 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-12-09 08:02:05 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-12-09 08:02:06 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-12-09 08:02:08 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/thomasmauerer/hassio-addons repository
23-12-09 08:02:08 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/brenner-tobias/ha-addons repository
23-12-09 08:02:08 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
23-12-09 08:02:08 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
23-12-09 08:02:08 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
23-12-09 08:02:09 INFO (MainThread) [supervisor.store] Loading add-ons from store: 73 all - 0 new - 0 remove
23-12-09 08:02:09 INFO (MainThread) [supervisor.store] Loading add-ons from store: 73 all - 0 new - 0 remove
23-12-09 08:32:06 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/system
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
23-12-09 09:00:44 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-12-09 09:02:06 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-12-09 09:18:59 INFO (MainThread) [supervisor.backups.manager] Backup 7c83c9f8 starting stage addon_repositories
23-12-09 09:18:59 INFO (MainThread) [supervisor.backups.manager] Backup 7c83c9f8 starting stage docker_config
23-12-09 09:18:59 INFO (MainThread) [supervisor.backups.manager] Creating new partial backup with slug 7c83c9f8
23-12-09 09:18:59 INFO (MainThread) [supervisor.backups.manager] Backup 7c83c9f8 starting stage home_assistant
23-12-09 09:19:01 INFO (MainThread) [supervisor.homeassistant.module] Backing up Home Assistant Core config folder
23-12-09 09:19:39 INFO (MainThread) [supervisor.homeassistant.module] Backup Home Assistant Core config folder done
23-12-09 09:19:39 INFO (MainThread) [supervisor.backups.manager] Backup 7c83c9f8 starting stage finishing_file
23-12-09 09:19:39 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug 7c83c9f8 completed
23-12-09 09:19:39 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2023.12.1
23-12-09 09:19:39 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2023.11.3 to ghcr.io/home-assistant/qemux86-64-homeassistant:2023.12.1
23-12-09 09:19:39 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2023.12.1.
23-12-09 09:21:52 INFO (SyncWorker_4) [supervisor.docker.manager] Stopping homeassistant application
23-12-09 09:22:23 INFO (SyncWorker_4) [supervisor.docker.manager] Cleaning homeassistant application
23-12-09 09:22:25 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
23-12-09 09:22:30 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2023.12.1
23-12-09 09:22:30 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
23-12-09 09:22:37 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
23-12-09 09:22:38 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-12-09 09:22:38 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/thomasmauerer/hassio-addons repository
23-12-09 09:22:38 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/brenner-tobias/ha-addons repository
23-12-09 09:22:38 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
23-12-09 09:22:38 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
23-12-09 09:22:38 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
23-12-09 09:22:38 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: Server disconnected
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/core/state: [Errno 104] Connection reset by peer
23-12-09 09:22:40 INFO (MainThread) [supervisor.store] Loading add-ons from store: 73 all - 0 new - 0 remove
23-12-09 09:22:40 INFO (MainThread) [supervisor.store] Loading add-ons from store: 73 all - 0 new - 0 remove
23-12-09 09:22:48 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
23-12-09 09:22:48 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
23-12-09 09:22:48 INFO (MainThread) [supervisor.homeassistant.core] A backup of the logfile is stored in /config/home-assistant-rollback.log
23-12-09 09:22:48 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2023.11.3
23-12-09 09:22:48 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2023.12.1 to ghcr.io/home-assistant/qemux86-64-homeassistant:2023.11.3
23-12-09 09:22:48 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2023.11.3.
23-12-09 09:22:49 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning homeassistant application
23-12-09 09:22:50 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
23-12-09 09:22:55 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2023.11.3
23-12-09 09:22:55 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
23-12-09 09:23:06 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to NOT_RUNNING
23-12-09 09:23:08 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
23-12-09 09:23:08 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-12-09 09:23:09 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-12-09 09:23:09 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/thomasmauerer/hassio-addons repository
23-12-09 09:23:09 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/brenner-tobias/ha-addons repository
23-12-09 09:23:09 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
23-12-09 09:23:09 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
23-12-09 09:23:09 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
23-12-09 09:23:09 INFO (MainThread) [supervisor.store] Loading add-ons from store: 73 all - 0 new - 0 remove
23-12-09 09:23:09 INFO (MainThread) [supervisor.store] Loading add-ons from store: 73 all - 0 new - 0 remove
23-12-09 09:24:18 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNING
23-12-09 09:24:18 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
23-12-09 09:24:18 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2023.11.3
23-12-09 09:24:19 INFO (SyncWorker_1) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/qemux86-64-homeassistant:2023.12.1']

why does he want to connect to this Ip address ??? http://172.30.32.1:8123 my internel is 192.168.0.x

[KILLTROY83]

The ip address comes from the virtual adapter and it looks like it can't be communicated with, which I don't understand because I haven't changed anything in the configuration.

[KILLTROY83]

Have now tried to import a backup a month ago, unfortunately with the same result. I have checked the network configuration without success, and have tried to update via cli without success. With my knowledge I am unfortunately at a standstill here.

[dasb00ter]

I believe this is docker network. http://172.30.32.1:8123/ Do you have any http config in your configuration yaml? Like a long time ago I remember messing with my proxy to get it to work. I use duckdns and caddy. Not sure my problem is related but feels similar. I can see that at least one Synology guy/girl responded that they could update in the update discussion

[KILLTROY83]

Yes, I agree, the ip comes from the docker container, My yaml is very simple and has only two essential entries. As dns I use cloudflair with my domain, which has never caused any problems.

Cloudflare

http: cors_allowed_origins:

• https://google.com
• https://www.home-assistant.io ip_ban_enabled: true login_attempts_threshold: 5 use_x_forwarded_for: true trusted_proxies:
• 172.30.33.0/24

climate:

• platform: smart_thermostat name: Smart Thermostat pool unique_id: smart_thermostat_pool heater: switch.wp_pool_socket_1 target_sensor: sensor.ibs_th2_p01b_044f_temperature min_temp: 20 max_temp: 32 ac_mode: False target_temp: 20 keep_alive: seconds: 60 away_temp: 14 kp: 5 ki: 0.01 kd: 500 pwm: 00:00:05

I also tried to deactivate everything and install the update, unfortunately without success.

PS: Thank you for trying to help me! BR, Peter

[dasb00ter]

Oops yes was going to try to deactivate that to update must be the way we set up the VM. Drastic but could do a clean install and then move everything. I don't have the time with a new family member here now. Stuck between a rock and a hard place on this

[Killtroy]

Yes I will try this next days! I came back to you asap.

[KILLTROY83]

Hi, I have now set up a blank Home Assistant on my synology using the OVA file haos_ova-11.2.

Import started and booted. HOS boots to the landing page see log:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
INFO: Using udev information from host
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
INFO: Starting local supervisor watchdog...
s6-rc: info: service legacy-services successfully started
[__main__] Initializing Supervisor setup
[supervisor.docker.network] Can't find Supervisor network, creating a new network
[supervisor.bootstrap] Seting up coresys for machine: qemux86-64
[supervisor.docker.supervisor] Attaching to Supervisor ghcr.io/home-assistant/amd64-hassio-supervisor with version 2023.11.6
[supervisor.docker.supervisor] Connecting Supervisor to hassio-network
[supervisor.resolution.evaluate] Starting system evaluation with state initialize
[supervisor.resolution.evaluate] System evaluation complete
[__main__] Setting up Supervisor
[supervisor.api] Starting API on 172.30.32.2
[supervisor.hardware.monitor] Started Supervisor hardware monitor
[supervisor.dbus.manager] Connected to system D-Bus.
[supervisor.dbus.agent] Load dbus interface io.hass.os
[supervisor.dbus.hostname] Load dbus interface org.freedesktop.hostname1
[supervisor.dbus.logind] Load dbus interface org.freedesktop.login1
[supervisor.dbus.network] Load dbus interface org.freedesktop.NetworkManager
[supervisor.dbus.rauc] Load dbus interface de.pengutronix.rauc
[supervisor.dbus.resolved] Load dbus interface org.freedesktop.resolve1
[supervisor.dbus.systemd] Load dbus interface org.freedesktop.systemd1
[supervisor.dbus.timedate] Load dbus interface org.freedesktop.timedate1
[supervisor.host.services] Updating service information
[supervisor.host.sound] Updating PulseAudio information
[supervisor.host.sound] Can't update PulseAudio data: Failed to connect to pulseaudio server
[supervisor.host.network] Updating local network information
[supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
[supervisor.docker.monitor] Started docker events monitor
[supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
[supervisor.docker.interface] Found ghcr.io/home-assistant/amd64-hassio-cli versions: []
[supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-cli with version 2023.10.0
[supervisor.plugins.cli] Starting CLI plugin
[supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/amd64-hassio-cli with version 2023.10.0 - 172.30.32.5
[supervisor.docker.interface] Found ghcr.io/home-assistant/amd64-hassio-dns versions: []
[supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2
[supervisor.plugins.dns] Starting CoreDNS plugin
[supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2023.06.2 - 172.30.32.3
[supervisor.plugins.dns] Updated /etc/resolv.conf
[supervisor.docker.interface] Found ghcr.io/home-assistant/amd64-hassio-audio versions: []
[supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-audio with version 2023.10.0
[supervisor.plugins.audio] Starting Audio plugin
[supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/amd64-hassio-audio with version 2023.10.0 - 172.30.32.4
[supervisor.docker.interface] Found ghcr.io/home-assistant/amd64-hassio-observer versions: []
[supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-observer with version 2023.06.0
[supervisor.plugins.observer] Starting observer plugin
[supervisor.docker.observer] Starting Observer ghcr.io/home-assistant/amd64-hassio-observer with version 2023.06.0 - 172.30.32.6
[supervisor.docker.interface] Found ghcr.io/home-assistant/amd64-hassio-multicast versions: []
[supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-multicast with version 2023.06.2
[supervisor.plugins.multicast] Starting Multicast plugin
[supervisor.docker.multicast] Starting Multicast ghcr.io/home-assistant/amd64-hassio-multicast with version 2023.06.2 - Host
[supervisor.plugins.manager] cli does not have the latest version 2023.11.0, updating
[supervisor.docker.interface] Updating image ghcr.io/home-assistant/amd64-hassio-cli:2023.10.0 to ghcr.io/home-assistant/amd64-hassio-cli:2023.11.0
[supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/amd64-hassio-cli with tag 2023.11.0.
[supervisor.docker.manager] Stopping hassio_cli application
[supervisor.docker.manager] Cleaning hassio_cli application
[supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/amd64-hassio-cli:2023.10.0']
[supervisor.plugins.cli] Starting CLI plugin
[supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/amd64-hassio-cli with version 2023.11.0 - 172.30.32.5
[supervisor.homeassistant.secrets] Loaded 0 Home Assistant secrets
[supervisor.docker.interface] No version found for ghcr.io/home-assistant/qemux86-64-homeassistant
[supervisor.homeassistant.core] No Home Assistant Docker image ghcr.io/home-assistant/qemux86-64-homeassistant found.
[supervisor.docker.interface] Attaching to ghcr.io/home-assistant/qemux86-64-homeassistant with version landingpage
[supervisor.homeassistant.core] Using preinstalled landingpage
[supervisor.homeassistant.core] Starting HomeAssistant landingpage
[supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
[supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version landingpage
[supervisor.os.manager] Detect Home Assistant Operating System 11.2 / BootSlot A
[supervisor.store.git] Cloning add-on https://github.com/esphome/home-assistant-addon repository
[supervisor.store.git] Cloning add-on https://github.com/hassio-addons/repository repository
[supervisor.store.git] Cloning add-on https://github.com/home-assistant/addons repository
[supervisor.store] Loading add-ons from store: 71 all - 71 new - 0 remove
[supervisor.addons] Found 0 installed add-ons
[supervisor.backups.manager] Found 0 backup files
[supervisor.discovery] Loaded 0 messages
[supervisor.ingress] Loaded 0 ingress sessions
[supervisor.resolution.check] Starting system checks with state setup
[supervisor.resolution.check] System checks complete
[supervisor.resolution.evaluate] Starting system evaluation with state setup
[supervisor.resolution.evaluate] System evaluation complete
[supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - setup
[supervisor.resolution.evaluate] Starting system evaluation with state setup
[supervisor.resolution.evaluate] System evaluation complete
[__main__] Running Supervisor
[supervisor.os.manager] Rauc: A - marked slot kernel.0 as good
[supervisor.addons] Phase 'initialize' starting 0 add-ons
[supervisor.addons] Phase 'system' starting 0 add-ons
[supervisor.addons] Phase 'services' starting 0 add-ons
[supervisor.core] Skipping start of Home Assistant
[supervisor.addons] Phase 'application' starting 0 add-ons
[supervisor.misc.tasks] All core tasks are scheduled
[supervisor.core] Supervisor is up and running
[supervisor.homeassistant.core] Home Assistant setup
[supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:landingpage to ghcr.io/home-assistant/qemux86-64-homeassistant:2023.12.1
[supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2023.12.1.
[supervisor.host.info] Updating local host information
[supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
[supervisor.resolution.check] Starting system checks with state running
[supervisor.resolution.checks.base] Run check for no_current_backup/system
[supervisor.resolution.module] Create new suggestion create_full_backup - system / None
[supervisor.resolution.module] Create new issue no_current_backup - system / None
[supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
[supervisor.resolution.checks.base] Run check for free_space/system
[supervisor.resolution.checks.base] Run check for pwned/addon
[supervisor.resolution.checks.base] Run check for multiple_data_disks/system
[supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
[supervisor.resolution.checks.base] Run check for docker_config/system
[supervisor.resolution.checks.base] Run check for trust/supervisor
[supervisor.resolution.checks.base] Run check for security/core
[supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
[supervisor.resolution.check] System checks complete
[supervisor.resolution.evaluate] Starting system evaluation with state running
[supervisor.host.services] Updating service information
[supervisor.host.network] Updating local network information
[supervisor.resolution.evaluate] System evaluation complete
[supervisor.resolution.fixup] Starting system autofix at state running
[supervisor.resolution.fixup] System autofix complete
[supervisor.host.sound] Updating PulseAudio information
[supervisor.host.manager] Host information reload completed

HOS updates to 2023.12.1 from this point the docker does not reboot and the landing page hangs although the docker is still running see screenshot.

A manual reboot of the docker now shows the new version 2023.12.1 but it can no longer access the website of HOS (no host found). There is no error displayed on the cli when booting the docker which I find very strange.

Attached is my synology data, i know it's not up to date but that's how it should be.

[upais]

Same problem. I am creating a new virtual machine from "haos_ova-11.2.ova", after some time the UI is unavailable. If you rollback to 2023.11.3 (ha supervisor update --version 2023.11.3), then there is no problem, but the update to 2023.12.0/1 is not completed.

[dasb00ter]

I'm on DSM 7.1.1. I'm running on xpenology. If u can't just whip up another VM and transpose I'm out of ideas.

[Killtroy]

I'm on DSM 7.1.1. I'm running on xpenology. If u can't just whip up another VM and transpose I'm out of ideas.

Ok, on your Synology it works with clean install via ova Virtual Maschine?

[dasb00ter]

I'm sorry I cant try right now. Have new member of house 😉 and they take up all my time. Plus I unexpectedly ended up in a production system. "hey Google turn on my bottle warmer"

[KILLTROY83]

For now i run Hassio in HyperV without issues on 2023.12.1.

[upais]

For now i run Hassio in HyperV without issues on 2023.12.1.

In the CPU settings in VMM? I can't do it, same error.

[Killtroy]

For now i run Hassio in HyperV without issues on 2023.12.1.

In the CPU settings in VMM? I can't do it, same error.

Sry I run it out of the box without synology vmm, I install a x86maschine with win10 & HyperV to go productive now. On synology i can’t go online with a native installation. From my opinion there must be a change in the image 2023.12 with ssl connections?? Is there any person from Hassio Team that can be confirming?

[vansyi]

I test in DVA3221,also encountered the same problem. The VMM on DVA322 could not be updated from 2023.11. to 2023.12.1. but DS1823xs+ VMM is ok to install haos_ova-11.2.ova.

[upais]

I test in DVA3221,also encountered the same problem. The VMM on DVA322 could not be updated from 2023.11. to 2023.12.1.

but DS1823xs+ VMM is ok to install haos_ova-11.2.ova.

I also have DVA3221, DSM version 7.2.1 update 3. It is very strange that the work depends on the synology model. Isn't the VMM version different?

[vansyi]

I test in DVA3221,also encountered the same problem. The VMM on DVA322 could not be updated from 2023.11. to 2023.12.1. but DS1823xs+ VMM is ok to install haos_ova-11.2.ova.

I also have DVA3221, DSM version 7.2.1 update 3. It is very strange that the work depends on the synology model. Isn't the VMM version different? DVA3221 VMM is 2.6.1.12139，DS1823xs+ VMM is 2.6.5-12202.Maybe it’s the difference in this version.

[vansyi]

I tried to install VMM 2.6.5-12202 on DVA3221 and then installed haos_ova-11.2, but HA could not be started. After looking at the supervisor log, there is still an error on host 172.30.32.1:8123.

[upais]

I tried to install VMM 2.6.5-12202 on DVA3221 and then installed haos_ova-11.2, but HA could not be started. After looking at the supervisor log, there is still an error on host 172.30.32.1:8123.

Also VMM 2.6.5-12202 on DVA 3221. You have Xpenology? If so, what bootloader does the DS1823xs+ have? I have already encountered that the bootloader affects virtualization.

[dasb00ter]

If it helps I'm using expenology ds918+ bootloader

[upais]

If it helps I'm using expenology ds918+ bootloader

Not really:) It's a very strange situation. There's another error somewhere and the reason is it.

[dasb00ter]

Didn't think so. Trying to remember who the guy was who made the Synology package that let you use hassos. I think it installed the supervisor natively and you could use add-ons regularly. He seems like a guy who might know. I switched from the package to the virtual machine quite awhile ago. Can't remember his handle

[upais]

As far as I remember, there was no supervisor in that package, it was HA core. Or we're talking about different things.

[dasb00ter]

It was different it was deprecated. The maintainer had trouble keeping it up. I remember the script downloaded all the dependencies and everything. Bearded tinkerer was the video I watched to switch over from that system to the VM. It was cool to see all of your add-ons as containers in docker once upon a time

On Tue, 12 Dec 2023, 11:25 am upais, @.***> wrote:

As far as I remember, there was no supervisor in that package, it was HA core. Or we're talking about different things.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/105254#issuecomment-1852483487, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CMVCD5R2TJ6Y4L7LBHBLYJCHRLAVCNFSM6AAAAABALSVJOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSGQ4DGNBYG4 . You are receiving this because you commented.Message ID: @.***>

[vansyi]

I tried to install VMM 2.6.5-12202 on DVA3221 and then installed haos_ova-11.2, but HA could not be started. After looking at the supervisor log, there is still an error on host 172.30.32.1:8123.

Also VMM 2.6.5-12202 on DVA 3221. You have Xpenology? If so, what bootloader does the DS1823xs+ have? I have already encountered that the bootloader affects virtualization.

Today I tried to install DS918+, but haos_ova-11.2 could not be installed and enabled. Changing to DS1821+ and installing haos_ova-11.2 can start HA.

[KILLTROY83]

I also use Xpenology but still with 6.5 DSM, it's time to switch to unraid because somehow the fundament is like a grave by Xpenology :(

[dasb00ter]

I tried to install VMM 2.6.5-12202 on DVA3221 and then installed haos_ova-11.2, but HA could not be started. After looking at the supervisor log, there is still an error on host 172.30.32.1:8123.

Also VMM 2.6.5-12202 on DVA 3221. You have Xpenology? If so, what bootloader does the DS1823xs+ have? I have already encountered that the bootloader affects virtualization.

Today I tried to install DS918+, but haos_ova-11.2 could not be installed and enabled. Changing to DS1821+ and installing haos_ova-11.2 can start HA.

What is processor for 1821+ and is it sataportmap or device tree for the HDD? I suppose I could switch over but apollo lake has good support for encoding video not to mention drive mapping. I mean DVA is basically a security camera box isnt it, with tensor possibilities? Switching is a possible solution but not great for allot of people. I mean something has changed with HA and it would be great to know if it is a breaking change that wont be reversed. I wonder if regular 918+ user are affected on there synologies?

[dasb00ter]

So I'm guessing we are too small a population to get a resolution here.

[upais]

A supervisor update has been released. Installed from a new image - same problem.

[sairon]

The Supervisor seems to work as expected and there are no clues what is wrong, but the problem seems to be in the Core container itself (homeassistant in Docker). Could anyone provide also ha core logs (obtained around or after that time when Error on call ... messages appear in the Supervisor logs)?

[upais]

The Supervisor seems to work as expected and there are no clues what is wrong, but the problem seems to be in the Core container itself (homeassistant in Docker). Could anyone provide also ha core logs (obtained around or after that time when Error on call ... messages appear in the Supervisor logs)? Looks like there's something wrong with the database.

[phase3]

Here is my fault log for core trying to upgrade 11.3 to 12.2 if that helps. home-assistant.log.fault.log

[sairon]

@phase3 Thank you, that was actually very helpful!

Here's the interesting part of the stack trace:

Fatal Python error: Illegal instruction                                                                                                                                                                                    

(...)

Current thread 0x00007f02d915dab0 (most recent call first):                                           
  File "/usr/local/lib/python3.11/site-packages/aiohttp/compression_utils.py", line 68 in compress_sync
  File "/usr/local/lib/python3.11/site-packages/aiohttp/compression_utils.py", line 83 in compress     
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_response.py", line 786 in _do_start_compression
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_response.py", line 406 in _start_compression   
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_response.py", line 445 in _prepare_headers       
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_response.py", line 421 in _start                 
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_response.py", line 763 in _start                 
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_response.py", line 415 in prepare                                                                                                                              
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 630 in finish_response                                                                                                                      
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 477 in _handle_request                                                                                                                      
  File "/usr/local/lib/python3.11/asyncio/events.py", line 80 in _run                                                                                                                                                      
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1925 in _run_once                                                                                                                                          
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 607 in run_forever                                                                                                                                         
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 640 in run_until_complete                                                                                                                                  
  File "/usr/src/homeassistant/homeassistant/runner.py", line 188 in run                                                                                                                                                   
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209 in main                                                                                                                                                
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 221 in <module>                                                                                                                                            
  File "<frozen runpy>", line 88 in _run_code                                                                                                                                                                              
  File "<frozen runpy>", line 198 in _run_module_as_main                                                                                                                                                                   

Extension modules: yaml._yaml, _cffi_backend, multidict._multidict, yarl._quoting_c, ciso8601, _brotli, aiohttp._helpers, aiohttp._http_writer, aiohttp._http_parser, aiohttp._websocket, frozenlist._frozenlist, ulid_tran
sform._ulid_impl, markupsafe._speedups, zlib_ng.zlib_ng, PIL._imaging, charset_normalizer.md, simplejson._speedups, sqlalchemy.cyextension.collections, sqlalchemy.cyextension.immutabledict, sqlalchemy.cyextension.proces
sors, sqlalchemy.cyextension.resultproxy, sqlalchemy.cyextension.util, greenlet._greenlet, fnv_hash_fast._fnv_impl, dbus_fast.signature, dbus_fast._private.marshaller, dbus_fast.message, dbus_fast.service, dbus_fast._pr
ivate.address, dbus_fast.unpack, dbus_fast.message_bus, dbus_fast._private.unmarshaller, dbus_fast.aio.message_reader, home_assistant_bluetooth.models, zeroconf._utils.time, zeroconf._dns, zeroconf._protocol.outgoing, z
eroconf._protocol.incoming, zeroconf._cache, zeroconf._record_update, zeroconf._updates, zeroconf._handlers.record_manager, zeroconf._services, zeroconf._services.info, zeroconf._services.registry, zeroconf._listener, z
eroconf._handlers.answers, zeroconf._handlers.multicast_outgoing_queue, zeroconf._history, zeroconf._handlers.query_handler, zeroconf._services.browser (total: 51)

It ends in aiohttp/compression_utils.py#L68 where it calls the zlib compressor, which would be zlib-ng after this change. And since zlib-ng is compiled with all the flags allowing the use of modern instruction sets, some of them are probably not available on the CPUs used on the problematic Synology NAS models.

cc @bdraco - it seems that (aiohttp-)zlib-ng introduction sadly makes 2023.12.0+ incompatible with some of the older CPUs, got any thoughts on it?

[dasb00ter]

Hmmm. Is this a problem on regular Synology boxes running Apollo or denverton?

Seems like most problems here are people using Xpenenology. I'm personally running this on Intel Core i5-7500 processor 7th gen processor in a HP G3 800 SFF.... Which doesn't seem that old?

[upais]

I have i5 11400 and dva3221. But I think that in VMM the processor works differently, maybe limited to the original.

[phase3]

Maybe to add to my log - I am on xpenology 6.2.3 with VMM with an Intel 10100 with an upgrade attempted. I have also tried the same thing on xpenology 7.2 VMM on an Intel 6700k with the same results on a fresh 12.3 install. I can repeat the problem easily enough by attempting the upgrade and then after rollback fetch the fault log. Edit: Adding cpu flags from host and VM: HOST: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 165 model name : Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz stepping : 3 microcode : 0xcc cpu MHz : 3601.000 cache size : 6144 KB physical id : 0 siblings : 8 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb invpcid_single intel_pt ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs bogomips : 27068.90 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management:

VM: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 165 model name : Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz stepping : 3 microcode : 0x1 cpu MHz : 13534.448 cache size : 6144 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti intel_ppin ssbd ibrs ibpb fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds mmio_stale_data retbleed gds bogomips : 27068.89 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management:

[bdraco]

I think that’s fixed in the new zlib ng but I’m waiting for a new release via https://github.com/pycompression/python-zlib-ng/pull/15

[bdraco]

In the mean time if we have a way a programatic way to detect the missing cpu flag we can arrange for the python code to not load zlib_ng

[bdraco]

I had an old DS918+ lying around to test on. https://github.com/home-assistant/core/pull/106193 should fix the issue while we are waiting for a new upstream release of python-zlib-ng

[dasb00ter]

I had an old DS918+ lying around to test on. #106193 should fix the issue while we are waiting for a new upstream release of python-zlib-ng

Lol You had one laying around. Brilliant

[bdraco]

for the other machines, can you post the result of

# python3 -m pip install cpufeature
# python3 -c "import cpufeature; cpufeature.print_features()"

Here is what I see on the DS918+

root@testsyno:~/aiohttp-zlib-ng# python3 -c "import cpufeature; cpufeature.print_features()"
=== CPU FEATURES ===
    VendorId                : GenuineIntel
    num_virtual_cores       : 4
    num_physical_cores      : 4
    num_threads_per_core    : 1
    num_cpus                : 0
    cache_line_size         : 64
    cache_L1_size           : 32768
    cache_L2_size           : 4194304
    cache_L3_size           : 0
    OS_x64                  : True
    OS_AVX                  : False
    OS_AVX512               : False
    MMX                     : True
    x64                     : True
    ABM                     : False
    RDRAND                  : True
    BMI1                    : False
    BMI2                    : False
    ADX                     : False
    PREFETCHWT1             : False
    MPX                     : True
    SSE                     : True
    SSE2                    : True
    SSE3                    : True
    SSSE3                   : True
    SSE4.1                  : True
    SSE4.2                  : True
    SSE4.a                  : False
    AES                     : True
    SHA                     : True
    AVX                     : False
    XOP                     : False
    FMA3                    : False
    FMA4                    : False
    AVX2                    : False
    AVX512f                 : False
    AVX512pf                : False
    AVX512er                : False
    AVX512cd                : False
    AVX512vl                : False
    AVX512bw                : False
    AVX512dq                : False
    AVX512ifma              : False
    AVX512vbmi              : False
    AVX512vbmi2             : False
    AVX512vnni              : False
root@testsyno:~/aiohttp-zlib-ng# 

[bdraco]

Upstream released zlib-ng 0.3.0 which should fix the issue.

It will get pulled into 2023.12.4 when its built.

If its still a problem for some boards, the linked PR will likely fix it, which will be in next week's beta.

Please let me know which one solves it for you. If everyone is working on 2023.12.4 we won't have to use the slower version on these platforms. If I don't hear back, I'll assume we need the slower version on the older chip which likely means it will be slow forever since we won't know when its safe to remove the workaround.

[emerysteele]

Confirm same issue on Xpenology DSM 6.2.3 & 7.2.1 after updating HA Core to 12.3.

Exported VM to main computer & running fine in VirtualBox.

Tried downgrading core to 11.2, but doesn't work. Says update completed but stays at version 12.3

Made a brand new HAOS instance, downgraded core to 11.2 & restored from backup file. Then imported back to DSM VMM. Running fine again.

Will test when update 12.4 comes out.

[upais]

@bdraco Updated to 2023.12.4 - problem solved. Xpenology DVA3221 (Denverton)

Thank you very much!

[emerysteele]

Just updated core to 12.4 as well. Confirm issue resolved.

[bdraco]

Thanks for confirming. I'll get the extra check reverted in 2023.1.x so the old syno boxes can still use the fastest possible code path https://github.com/bdraco/aiohttp-zlib-ng/pull/5 as the problem is fixed in zlib_ng 0.3.0+

[feron81]

I have the exact same problem. This version 2023.11.3 works without problems. What is the easiest solution, that also the new version works? I also have this 2 IP in virtual machine manager 172.30.32.1 and 172.30.232.1. Should I trust this IPs to the trusted_proxies? I updated to the newest version, but I still have the same problem.

At the moment I still have version 2023.11.3 installed. With this it worked without problems. I installed also the newest one 2024.1.1 and still have the same problem. And yesterday I also updated to the version 11.3.