Web-socket error
Try without proxy and see if it's a server issue.
When i use http://host.xx:8082 i get no error. Same as before.
When i use https://host.xx i get websocket error. Worked before update.
Tryed to proxy websocket, but i dont know if im doing it right, but it has not been a problem before.
In my configuration using Let's Encrypt, even though I try to access using http:// the apache server automatically redirects to https://, your problem is probably in the apache server settings.
Remembering I'm using Linux + Apache!
OP uses Windows with Microsoft IIS server, as far as I understand. Not Apache.
Yes, you are correct!
However what I wanted to say is that the behavior should be the same for both servers or not ?, he should not have access to http without being directed to https!
Redirection has nothing to do with the proxy. It might be a good idea to redirect to HTTPS for security reasons, but that's not a requirement and you don't have to do it, even in Apache.
Yes, but I do not see an acceptable reason to use the http protocol since it makes use of a proxy.
So is there a change in 4.1 that results in this error?
Is there something i can do?
I have tryed all redirect and proxy settings i can come up with :)
No, there were no changes that could affect this, as far as I know.
I tryed IE browser to se if there is any differense, and to my suprise it looks like it works there???
Tryed to uninstall and reinstall Chrome, but still doesent work....
Took a look in Chrome Console now, and i see the error/message below.
Can this be the problem?
[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
ol.js:47 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
...Those are warnings, as far as I know. And no, those are not the problem.
Finaly i found a solution for this problem in another post...
Hallo,
ich habe alles genauso wie in den Beschreibungen umgesetzt und bekomme mit jedem Browser über https den websockefehler.
Kann mir jemand helfen?
Grüße
Hallo Sascha,
ich habe das geliche Problem hier. Hast Du schon eine Lösung gefunden?
After upgrade to 4.1 i got Websocket connection error... Tryed websocket proxy, but no luck.
Tryed to revert back to 4.0, all works fine.
Any sugestion what it could be wrong, or is there anyone that can share their IIS web.config?
This is only when i use secure connection...