Connection can no longer be established

[011V32]

Describe the bug
I switched from the old repo to the new repo and thus from 1.6.0 to 1.6.2.
With the new version I can no longer connect to my Mac.

To Reproduce
I deleted the old version and then installed the new version straight away. Then I re-entered the data (which I had previously copied) and tried to connect.
Normally, the connection was successfully connected with the password in the configuration.
When I enter something in the dialog, the following error appears.
(Previously, no additional dialog appeared at all)

Error message

Ein Fehler ist aufgetreten:

Cannot read properties of undefined (reading 'importKey')
TypeError: Cannot read properties of undefined (reading 'importKey')
at AESECBCipher._importKey (http://homeassistant.local:8123/api/hassio_ingress/ESchz347LQg8DJKlC152P9l-Qk_1kL372Wbw_kcDr8w/core/crypto/aes.js:17:48)
at AESECBCipher.importKey (http://homeassistant.local:8123/api/hassio_ingress/ESchz347LQg8DJKlC152P9l-Qk_1kL372Wbw_kcDr8w/core/crypto/aes.js:12:22)
at LegacyCrypto.importKey (http://homeassistant.local:8123/api/hassio_ingress/ESchz347LQg8DJKlC152P9l-Qk_1kL372Wbw_kcDr8w/core/crypto/crypto.js:50:20)
at RFB._negotiateARDAuthAsync (http://homeassistant.local:8123/api/hassio_ingress/ESchz347LQg8DJKlC152P9l-Qk_1kL372Wbw_kcDr8w/core/rfb.js:1737:43)

Logs

s6-rc: info: service noVNC: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service noVNC successfully started
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
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
[10:29:46] INFO: Set some defaults
[10:29:46] INFO: Prepare noVNC for Home Assistant ingress
s6-rc: info: service legacy-services successfully started
[10:29:46] INFO: Inject vnc connection password
[10:29:46] INFO: Start noVNC
[10:29:46] INFO: Connecting to VNC 10.10.10.10:5900
Warning: could not find self.pem
Using installed websockify at /usr/local/bin/websockify
Starting webserver and WebSockets proxy on port 6080
WebSocket server settings:

• Listen on :6080
• Web server. Web root: /noVNC
• No SSL/TLS support (no cert file)
• proxying from :6080 to 10.10.10.10:5900
  Navigate to this URL:
  http://68413af6-vnc-viewer:6080/vnc.html?host=68413af6-vnc-viewer&port=6080
  Press Ctrl-C to exit
  172.30.32.2 - - [14/Nov/2024 10:29:54] 172.30.32.2: Plain non-SSL (ws://) WebSocket connection
  172.30.32.2 - - [14/Nov/2024 10:29:54] 172.30.32.2: Path: '/websockify'
  172.30.32.2 - - [14/Nov/2024 10:29:54] connecting to: 10.10.10.10:5900
  172.30.32.2 - - [14/Nov/2024 10:30:33] 172.30.32.2: Plain non-SSL (ws://) WebSocket connection
  172.30.32.2 - - [14/Nov/2024 10:30:33] 172.30.32.2: Path: '/websockify'
  172.30.32.2 - - [14/Nov/2024 10:30:33] connecting to: 10.10.10.10:5900

Expected behavior
Successful connection without entering additional user data.

Screenshots

System

• Core: 2024.11.1
• Supervisor: 2024.11.2
• Operating System: 13.2
• Frontend: 20241106.2
• Host hardware: Intel NUC