Hi,
I have datalore running as a docker container. Traffic needs to go through my haproxy, which performs ssl-termination.
Unfortunately when going through haproxy loading datalore fails. The browser tries to acces datalore using wss:// which results in an error 403.
Accessing the container directly (http://mydocker.host:8080) works since datalore is only accessed via ws://
This however is not an option for my deployment. I use the exact same haproxy configuration with other services which use websockets witthout any issues.
Same Problem here using nginx. When I access it through the public ip it works. So it’s gotta be a problem with the reverse proxy. @eee did it work in previous versions?
Yeah it is not an optimal solution because the wss connection for the collaboration socket still throws an error 403. But if you are solo you can use it without any problems