The workaround is a very simple fix just use 127.0.0.1 instead of localhost. Since our WebKit connections use these settings they are also affected by this. Perhaps you are suffering from the following misconfiguration: Safari has an HSTS Policy that forces the "localhost" to use HTTPS, which can cause previously working connections to no longer work. If your WebKit connections suddenly stop working and you start receiving the following error message: The next time you visit the page in Royal TSX it shouldn't prompt for certificate validation anymore and the WebSocket related issues should be gone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |