Hi, thank you. yes it looks like SSL certificate issue, but SSL checker( https://www.sslshopper.com/ssl-checker.html ) shows that certificate is correct. I've never clicked 'proceed anyway', because main server in production at least 2 years, and certificate is valid. I see the same problem with new PC, where this site was never opened and into incognito mode. When first URL was opened and WSS connection established for example to *wss://web.serverid.server_url/web-connect* I still have the same problem with another servers, for example *wss://web.serverid1.server_url/web-connect* *wss://web.serverid2.server_url/web-connect* and so on. After opening such URLs into browser application can establish connect, until next time when it received new URLs.
And it works in Firefox. сб, 31 авг. 2019 г. в 19:09, J Decker <[email protected]>: > Sounds more like a certificate issue, when you go to the https, do yo > uhave to click 'proceed anyway' (or whatever the option) > My Websocket services aren't behind redirect, so I don't know if that > works... > > On Sat, Aug 31, 2019 at 12:42 AM Евгений Горлов <[email protected]> > wrote: > >> Hi all, >> I got error "*WebSocket opening handshake was canceled*" while >> connecting to web server. In Firefox it works well, in Chrome I found >> workaround, we need copy URL for example >> *wss://web.serverid.server_url/web-connect* to browser and try to open >> page by replacing wss to https for example >> *https://web.serverid.server_url/web-connect >> <https://web.serverid.server_url/web-connect>*. And after that it works >> and application able to establish connection. Maybe it happens because on >> our server we have redirect to main page, I don't know exactly. >> But such workaround is not applicable for users. >> Maybe somebody know, how to do it automatically or how to prepare Chrome >> for future connections. >> >> *Mit Freundlichen Grüßen*, >> >> *Evgeny* >> linkedin <https://de.linkedin.com/in/evgeniy-gorlov-818a5660> >> *Tel.: **+48 790 781 951* >> *Skype: evgeniy.gorlov* >> >> -- >> You received this message because you are subscribed to the Google Groups >> "emscripten-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/CAGRRjyBQoRaG%3DpoPAd21jJ-XhhjmpJ%2B6hoyHNDsFOTea%3Dddcjw%40mail.gmail.com >> <https://groups.google.com/d/msgid/emscripten-discuss/CAGRRjyBQoRaG%3DpoPAd21jJ-XhhjmpJ%2B6hoyHNDsFOTea%3Dddcjw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/CAA2GJqWvBRW2KN%3Dd%3DJB%2BaBsCYzcJuiMrn1vj6UnRHcgyngDrGA%40mail.gmail.com > <https://groups.google.com/d/msgid/emscripten-discuss/CAA2GJqWvBRW2KN%3Dd%3DJB%2BaBsCYzcJuiMrn1vj6UnRHcgyngDrGA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAGRRjyAabW179Fz1ONXmbqrMV59kCVGu9NtAmdQQv8UaPCZabA%40mail.gmail.com.
