I also tried adding the credentials to my node server but the same problem persists. I am currently using a CloudFlare issues certificate and key which is in my NGINX configuration. As noted in September 2019, Volexity suspected that the Evil Eye attackers had also targeted iPhones based on the attackers' C2 servers going offline shortly after Project Zero's findings were made public. (OSStatus error -9836.)Īfter doing some research into the error I found that Safari is picky when it comes to creating secure websocket connections. 30 of iPhone devices using the App store use iOS 12 or earlier This represents a considerable attack surface of potentially vulnerable devices. I have been able to track down the error by inspecting the iOS browser through a Mac and this error shows up WebSocket network error: The operation couldn’t be completed. My application works from socket.io client -> NGINX Proxy -> Node.js socket server However clients using Safari on Desktop and iOS are unable to connect using both Safari and Chrome. Clients using Windows machines and Android Devices are able to make a websocket connection. This article is intended for system administrators for a school, business, or other organization. I am developing a chat application that makes use of socket.io for matchmaking. In iOS 10.3 and later and iPadOS, when you manually install a profile that contains a certificate payload, that certificate isn't automatically trusted for SSL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |