ioBroker.admin
ioBroker.admin copied to clipboard
System settings window does not close after hitting button "save and close"
Describe the bug
After a new, fresh installation of ioBroker.admin, the "sytem settings"-window does not close after hitting button "save and close". This behavior happens only after a new installation.
Expected behavior
"sytem settings"-window close after hitting button "save and close"
Screenshots & Logfiles
https://github.com/ioBroker/ioBroker.admin/assets/69053781/98f18d83-cb96-4d9d-85be-61dec211a271
Versions:
- Adapter version: v6.3.5
- JS-Controller version: v4.0.24
- Node version: v18.16.0
- Operating system: iobroker.docker
I cannot reproduce this with v6.6.0, can you tell me exactly what you are changing? For me it closes and a toast appears in the lower left corner stating Settings saved
. Does a error in browser console appear?
This phenomen appears only after a fresh installation of ioBroker. I‘ll check again with admin v6.6.0
Ah okay, so it appears exactly one time? Then hopefully there is something in the browser console
Only one time. After a manual reload of ioBroker everything works as expected. I‘ll check again ASAP.
Error in Console (but with ioBroker.admin v.6.3.5) I can't simulate with v6.6.0 because I have to save and close the window to change the repository to beta
, reload the page manually and then the issue does no longer appear. But I assume that the error will also appear with v6.6.0:
Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure element '<URL>'. This request was automatically upgraded to HTTPS, For more information see <URL>
:8081/#tab-adapters/system:1 Mixed Content: The page at 'https://192.168.1.168:8081/#tab-adapters/system' was loaded over HTTPS, but requested an insecure element 'http://c.tile.osm.org/14/8191/8191.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
:8081/#tab-adapters/system:1 Mixed Content: The page at 'https://192.168.1.168:8081/#tab-adapters/system' was loaded over HTTPS, but requested an insecure element 'http://a.tile.osm.org/14/8192/8191.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
:8081/#tab-adapters/system:1 Mixed Content: The page at 'https://192.168.1.168:8081/#tab-adapters/system' was loaded over HTTPS, but requested an insecure element 'http://a.tile.osm.org/14/8191/8192.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
:8081/#tab-adapters/system:1 Mixed Content: The page at 'https://192.168.1.168:8081/#tab-adapters/system' was loaded over HTTPS, but requested an insecure element 'http://b.tile.osm.org/14/8192/8192.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
:8081/#tab-adapters/system:1 Mixed Content: The page at 'https://192.168.1.168:8081/#tab-adapters/system' was loaded over HTTPS, but requested an insecure element 'http://b.tile.osm.org/14/8190/8191.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
:8081/#tab-adapters/system:1 Mixed Content: The page at 'https://192.168.1.168:8081/#tab-adapters/system' was loaded over HTTPS, but requested an insecure element 'http://b.tile.osm.org/14/8193/8191.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
:8081/#tab-adapters/system:1 Mixed Content: The page at 'https://192.168.1.168:8081/#tab-adapters/system' was loaded over HTTPS, but requested an insecure element 'http://c.tile.osm.org/14/8190/8192.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
:8081/#tab-adapters/system:1 Mixed Content: The page at 'https://192.168.1.168:8081/#tab-adapters/system' was loaded over HTTPS, but requested an insecure element 'http://c.tile.osm.org/14/8193/8192.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
instrument.ts:124 [2023-07-10T06:23:23.355Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:124
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:124 [2023-07-10T06:23:23.356Z] Start reconnect 0
instrument.ts:124 [2023-07-10T06:23:23.424Z] Try to connect
socket.io.js:140 WebSocket connection to 'wss://192.168.1.168:8081/?sid=1688970203425&name=admin' failed:
SocketClient.connect @ socket.io.js:140
(anonymous) @ socket.io.js:428
vt @ helpers.ts:98
instrument.ts:124 [2023-07-10T06:23:25.455Z] Start reconnect 1
instrument.ts:124 [2023-07-10T06:23:25.455Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:124
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:124 [2023-07-10T06:23:25.455Z] Reconnect is already running 1
instrument.ts:124 [2023-07-10T06:23:26.469Z] Try to connect
socket.io.js:140 WebSocket connection to 'wss://192.168.1.168:8081/?sid=1688970206469&name=admin' failed:
SocketClient.connect @ socket.io.js:140
(anonymous) @ socket.io.js:428
vt @ helpers.ts:98
instrument.ts:124 [2023-07-10T06:23:28.505Z] Start reconnect 2
instrument.ts:124 [2023-07-10T06:23:28.505Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:124
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:124 [2023-07-10T06:23:28.506Z] Reconnect is already running 2
instrument.ts:124 [2023-07-10T06:23:30.505Z] Try to connect
socket.io.js:140 WebSocket connection to 'wss://192.168.1.168:8081/?sid=1688970210506&name=admin' failed:
SocketClient.connect @ socket.io.js:140
(anonymous) @ socket.io.js:428
vt @ helpers.ts:98
instrument.ts:124 [2023-07-10T06:23:32.539Z] Start reconnect 3
instrument.ts:124 [2023-07-10T06:23:32.539Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:124
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:124 [2023-07-10T06:23:32.539Z] Reconnect is already running 3
instrument.ts:124 [2023-07-10T06:23:35.552Z] Try to connect
instrument.ts:124 Stored version: 6.3.5, new version: 6.3.5
here we go with ioBroker.admin v6.6.0:
instrument.ts:132 [2023-07-10T07:00:23.922Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:132
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:132 [2023-07-10T07:00:23.923Z] Start reconnect 0
instrument.ts:132 [2023-07-10T07:00:23.991Z] Try to connect
socket.io.js:140 WebSocket connection to 'wss://192.168.1.168:8081/?sid=1688972423991&name=admin' failed:
SocketClient.connect @ socket.io.js:140
(anonymous) @ socket.io.js:428
o @ helpers.ts:98
instrument.ts:132 [2023-07-10T07:00:26.038Z] Start reconnect 1
instrument.ts:132 [2023-07-10T07:00:26.038Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:132
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:132 [2023-07-10T07:00:26.038Z] Reconnect is already running 1
instrument.ts:132 [2023-07-10T07:00:27.052Z] Try to connect
socket.io.js:140 WebSocket connection to 'wss://192.168.1.168:8081/?sid=1688972427052&name=admin' failed:
SocketClient.connect @ socket.io.js:140
(anonymous) @ socket.io.js:428
o @ helpers.ts:98
instrument.ts:132 [2023-07-10T07:00:29.070Z] Start reconnect 2
instrument.ts:132 [2023-07-10T07:00:29.070Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:132
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:132 [2023-07-10T07:00:29.071Z] Reconnect is already running 2
instrument.ts:132 [2023-07-10T07:00:31.070Z] Try to connect
socket.io.js:140 WebSocket connection to 'wss://192.168.1.168:8081/?sid=1688972431071&name=admin' failed:
SocketClient.connect @ socket.io.js:140
(anonymous) @ socket.io.js:428
o @ helpers.ts:98
instrument.ts:132 [2023-07-10T07:00:33.105Z] Start reconnect 3
instrument.ts:132 [2023-07-10T07:00:33.105Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:132
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:132 [2023-07-10T07:00:33.106Z] Reconnect is already running 3
instrument.ts:132 [2023-07-10T07:00:36.118Z] Try to connect
instrument.ts:132 Stored version: 6.6.0, new version: 6.6.0
ioBroker.admin v6.9.2:
[2023-09-03T12:34:08.967Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:139
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:139 [2023-09-03T12:34:08.968Z] Start reconnect 0
instrument.ts:139 [2023-09-03T12:34:09.039Z] Try to connect
socket.io.js:140 WebSocket connection to 'wss://192.168.1.168:8081/?sid=1693744449039&name=admin' failed:
SocketClient.connect @ socket.io.js:140
(anonymous) @ socket.io.js:428
o @ helpers.ts:98
instrument.ts:139 [2023-09-03T12:34:11.113Z] Start reconnect 1
instrument.ts:139 [2023-09-03T12:34:11.113Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:139
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:139 [2023-09-03T12:34:11.114Z] Reconnect is already running 1
instrument.ts:139 [2023-09-03T12:34:12.127Z] Try to connect
socket.io.js:140 WebSocket connection to 'wss://192.168.1.168:8081/?sid=1693744452127&name=admin' failed:
SocketClient.connect @ socket.io.js:140
(anonymous) @ socket.io.js:428
o @ helpers.ts:98
instrument.ts:139 [2023-09-03T12:34:14.196Z] Start reconnect 2
instrument.ts:139 [2023-09-03T12:34:14.196Z] ws connection error: CLOSE_ABNORMAL
(anonymous) @ instrument.ts:139
error @ socket.io.js:68
socket.onclose @ socket.io.js:177
instrument.ts:139 [2023-09-03T12:34:14.196Z] Reconnect is already running 2
instrument.ts:139 [2023-09-03T12:34:16.209Z] Try to connect
instrument.ts:139 Stored version: 6.9.2, new version: 6.9.2