The problem after the update to 2025.11.2

Installation
1

I use Debian 12 and Supervised. I have updated the current Debian updates and update Home assistant to 2925.11.2. Now I have a problem: the Home Assistant interface shows that no addon is running. There is also no access to the web interfaces of all addons. I use addons: Zigbee2mqtt (two addons), Mosquito, File Editor and Studio Code Server. I can see that the addons themselves are working, as the data is sent to the Home Assistant via Z2M and Mosquito, and I can also see the logs.
I see this in the Supervisor’s log, it wasn’t there before:
2025-11-15 22:47:40.638 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘Glances’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.642 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘Nginx Proxy Manager’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.653 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘MQTT IO’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.679 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘Overseerr’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.688 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘Studio Code Server’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.700 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘Folding@home’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.703 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘Log Viewer’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.706 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘Grocy’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.716 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘InfluxDB’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.722 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘Tailscale’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

2025-11-15 22:47:40.725 WARNING (SyncWorker_3) [supervisor.addons.validate] Add-on ‘Traccar’ uses deprecated ‘codenotary’ field in config. This field is no longer used and will be ignored. Please report this to the maintainer.

What could be the problem? How can I fix this?
Please help me.

2

I would do an issue with each of those GitHub Repo’s and have them update their stuff to match current HA Base requirements. (That is assuming you are using current versions of these addons and it is their fault not yours that they are out of date)

CodeNotary went offline like a year ago or more, so there has been plenty of time.

It is also possible that the fact that you are using supervised install method which is also deprecated might contribute to the problem.

2 Likes
3

THIS might help.

4

I’m facing the same issue. After Supervisor 2025.11.2 update, at least visually no addon is or can be started. For example, Mosquitto Broker (post HA reboot, should start on boot):

image
image1032×542 28.9 KB

If I try to start it, the Supervisor logs say that it’s already running:

2025-11-15 22:40:10.414 WARNING (MainThread) [supervisor.addons.addon] core_mosquitto is already running!

And I can actually connect to it so yeah, it’s running. I believe that indicates that the issue is not related to the addons themselves, as the behavior is the same for all. I didn’t see any warnings for deprecated fields on my side.

5

The issue comes with the latest containerd. Hence you might need to downgrade

docker-ce
docker-ce-cli
containerd.io

until that issue has been resolved.

1 Like
6

Since Supervised is ending, I was planning to use HAOS, if I now finally perform a transfer (recovery) of the current backup (which has this problem) will everything work well?

7

Which versions of
docker-ce
docker-ce-cli

are currently working for Debian 12?

8

Just follow the link I have provided above to learn more about the latter.

9

Thank you for bringing that up. I was facing the exact same issue, suddenly my Add-Ons refused to start.

Fingers crossed the issue will be fixed, my supervised is deprecated now but I hope to use my installation for a bit longer. :slight_smile:

10

Yes, it helped. I have made a downgrade to:
apt install docker-ce=5:28.5.1-1~debian.12~bookworm
apt install docker-ce-cli=5:28.5.1-1~debian.12~bookworm
apt install containerd.io=1.7.28-1~debian.12~bookworm
Then I did a reboot and now everything is working again.
Thanks for the help!
PS: Now I need to switch to HAOS before the new year.

2 Likes