Editor not starting (Browser websocket Problem?)

ioBroker / ioBroker.vis-2

Next generation visualisation for ioBroker platform.

Other

26 stars 3 forks source link

Editor not starting (Browser websocket Problem?) #70

Open Eistee82 opened 9 months ago

Eistee82 commented 9 months ago

Describe the bug
Editor not working. I only see an iobroker logo.

To Reproduce

Install vis-2
Start vis-2 with licence
Click the Icon

Screenshots & Logfiles
Chrome Devtools Error on Line 140 of File socket.io.js

Versions:

Adapter version: 2.2.2
JS-Controller version: 5.0.12
Node version: 18.17.1
Operating system: debian

Feuer-sturm commented 9 months ago

@Eistee82 Please post a screenshot of the settings of your web instance.

This is how it looks like on my system with vis2 v2.2.2 grafik

Eistee82 commented 9 months ago

Feuer-sturm commented 9 months ago

@Eistee82 does it work if you change it to "integriert " and "reine Web sockets verwenden " like I have it?

Eistee82 commented 9 months ago

Yes this is working. so there is a bug with websocket

Feuer-sturm commented 9 months ago

@Apollon77 @foxriver76 what is your oppinion for which Adapter is this issue relevant?

Eistee82 commented 9 months ago

Without "reine Web sockets verwenden" it is working too. "integriert" works and "ws.0" did not work

EvilEls commented 8 months ago

Without "reine Web sockets verwenden" it is working too. "integriert" works and "ws.0" did not work

same here

Version 2.2.6 in /opt/iobroker/node_modules/iobroker.vis-2, node: v18.17.1, js-controller: 5.0.12

When using socketio.0 instance, editor and view does not load with CORS error because of obviously wrong URL Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://https/socket.io/?ws=true&EIO=3&transport=polling&t=OgdBvgr.

When using integrated editor works but view reports ws connection errors:

Apollon77 commented 8 months ago

@Feuer-sturm vis issue