NEWS
[gelöst] Samsung Internet Browser Problem mit ioBroker
-
@sigi234 ja
iobroker.admin@5.1.28 socket.io.js:59 [2021-12-04T12:10:21.256Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619821257&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ Connection.ts:239 u @ runtime.js:63 (anonymous) @ runtime.js:294 (anonymous) @ runtime.js:119 n @ asyncToGenerator.js:3 i @ asyncToGenerator.js:25 (anonymous) @ asyncToGenerator.js:32 (anonymous) @ asyncToGenerator.js:21 (anonymous) @ 5.fdbcba88.chunk.js:2 (anonymous) @ Connection.ts:99 socket.io.js:59 [2021-12-04T12:10:21.344Z] Start reconnect 0 socket.io.js:61 [2021-12-04T12:10:21.345Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:21.345Z] Reconnect is already running 0 socket.io.js:59 [2021-12-04T12:10:21.368Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619821370&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:21.429Z] Start reconnect 1 socket.io.js:61 [2021-12-04T12:10:21.430Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:21.430Z] Reconnect is already running 1 socket.io.js:59 [2021-12-04T12:10:22.430Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619822432&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:22.520Z] Start reconnect 2 socket.io.js:61 [2021-12-04T12:10:22.521Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:22.521Z] Reconnect is already running 2 socket.io.js:59 [2021-12-04T12:10:24.521Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619824521&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:24.582Z] Start reconnect 3 socket.io.js:61 [2021-12-04T12:10:24.583Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:24.583Z] Reconnect is already running 3 socket.io.js:59 [2021-12-04T12:10:27.583Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619827584&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:27.674Z] Start reconnect 4 socket.io.js:61 [2021-12-04T12:10:27.674Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:27.675Z] Reconnect is already running 4 socket.io.js:59 [2021-12-04T12:10:31.675Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619831676&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:31.764Z] Start reconnect 5 socket.io.js:61 [2021-12-04T12:10:31.767Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:31.775Z] Reconnect is already running 5 socket.io.js:59 [2021-12-04T12:10:36.767Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619836768&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:36.857Z] Start reconnect 5 socket.io.js:61 [2021-12-04T12:10:36.858Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:36.859Z] Reconnect is already running 5@rushmed sagte in Samsung Internet Browser Problem mit ioBroker Web UI:
ERR_SSL_PROTOCOL_ERROR
Mhh . hast du HTTPS , obwohl @Feuersturm es auch nicht nutzt
EDIT :
Laut
connection to 'ws://192.168.178.20
ist bei dir HTTP ( ws )
-
@sigi234 ja
iobroker.admin@5.1.28 socket.io.js:59 [2021-12-04T12:10:21.256Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619821257&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ Connection.ts:239 u @ runtime.js:63 (anonymous) @ runtime.js:294 (anonymous) @ runtime.js:119 n @ asyncToGenerator.js:3 i @ asyncToGenerator.js:25 (anonymous) @ asyncToGenerator.js:32 (anonymous) @ asyncToGenerator.js:21 (anonymous) @ 5.fdbcba88.chunk.js:2 (anonymous) @ Connection.ts:99 socket.io.js:59 [2021-12-04T12:10:21.344Z] Start reconnect 0 socket.io.js:61 [2021-12-04T12:10:21.345Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:21.345Z] Reconnect is already running 0 socket.io.js:59 [2021-12-04T12:10:21.368Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619821370&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:21.429Z] Start reconnect 1 socket.io.js:61 [2021-12-04T12:10:21.430Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:21.430Z] Reconnect is already running 1 socket.io.js:59 [2021-12-04T12:10:22.430Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619822432&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:22.520Z] Start reconnect 2 socket.io.js:61 [2021-12-04T12:10:22.521Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:22.521Z] Reconnect is already running 2 socket.io.js:59 [2021-12-04T12:10:24.521Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619824521&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:24.582Z] Start reconnect 3 socket.io.js:61 [2021-12-04T12:10:24.583Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:24.583Z] Reconnect is already running 3 socket.io.js:59 [2021-12-04T12:10:27.583Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619827584&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:27.674Z] Start reconnect 4 socket.io.js:61 [2021-12-04T12:10:27.674Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:27.675Z] Reconnect is already running 4 socket.io.js:59 [2021-12-04T12:10:31.675Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619831676&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:31.764Z] Start reconnect 5 socket.io.js:61 [2021-12-04T12:10:31.767Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:31.775Z] Reconnect is already running 5 socket.io.js:59 [2021-12-04T12:10:36.767Z] Try to connect socket.io.js:91 WebSocket connection to 'ws://192.168.178.20:8081/?sid=1638619836768&name=admin' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR SocketClient.connect @ socket.io.js:91 (anonymous) @ socket.io.js:372 socket.io.js:59 [2021-12-04T12:10:36.857Z] Start reconnect 5 socket.io.js:61 [2021-12-04T12:10:36.858Z] ws connection error: CLOSE_ABNORMAL error @ socket.io.js:61 socket.onclose @ socket.io.js:128 socket.io.js:59 [2021-12-04T12:10:36.859Z] Reconnect is already running 5Zeig mal Instanzeinstellungen: socketio.0
-
Ich habe weder HTTPS noch eine socketio. Instanz.
Ich leg mal eine an.Edit:
Authentifizierung habe ich aktiv.
Mit dem alten Admin UI komme ich schonmal zum Login Screen und bleibe danach hängen. -
Ok, habe jetzt debug Zugriff auf den Samsung Browser. Wo kann ich da nach Problemen suchen?
Fehlt der App etwa Javascript?@rushmed sagte in Samsung Internet Browser Problem mit ioBroker Web UI:
Ok, habe jetzt debug Zugriff auf den Samsung Browser.
Wie hast du das gemacht?
-
@Glasfaser siehe Link der Debugging Zugang aufs Telefon wird über Chrome gestartet.
-
@Glasfaser siehe Link der Debugging Zugang aufs Telefon wird über Chrome gestartet.
-
@rushmed Konntest du das Problem lösen?
Hätte noch den Vorschlag den Hacken beim erzwingen der Websockets in der Instanz Web.0 zu deaktivieren.
Hiermit geht zumindest wieder der Zugriff auf die ViS mit dem neuen Samsung Internet Browser.
@seffe @Rushmed
Was aber beim neuen Samsung Internet Browser 16.0.2.19 trotzdem nicht mehr geht, ist der Zugriff auf Flot Diagramme, zumindest bei mir nicht (Websockets erzwingen ist deaktiviert). Sobald mehrere Flots geladen werden sollen, passiert außer einem derhenden Kreis einfach gar nichts und irgendwann stürzt der Browser dann auch noch ab. Wenn nur ein einzelnes Flot geladen werden soll, geht es. Mit Chrome und FF gibt es da keine Probleme. -
@rushmed Konntest du das Problem lösen?
Hätte noch den Vorschlag den Hacken beim erzwingen der Websockets in der Instanz Web.0 zu deaktivieren.
Hiermit geht zumindest wieder der Zugriff auf die ViS mit dem neuen Samsung Internet Browser.@seffe Nein, es funktionier immernoch nicht. Das Erzwingen der Websockets war bereits deaktiviert.
Ich sehe aber Licht am Ende des Tunnels. In der aktuellen Samsung Internet beta 16.2.1.25 komme ich wieder in die Admin Oberfläche. :+1:
Flot und Vis habe ich nicht getestet, ich visualisiere alles mit einer Kombi aus Grafana und HabPanel und das ging beides immer. -
@rushmed Dankeschön. Funktioniert bei mir jetzt auch wieder.
Support us
816
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge