ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Web socket issues with ERL and Safari on iOS

    IT Discussion
    websocket safari piss off apple ios
    2
    5
    2.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch
      last edited by scottalanmiller

      Ok, this has been a pain in my ass for a bit, but it also is proof that Chrome on iOS is safari.

      I had visited this router in Safari first, and clicked trust on the cert warning pop up. I can then log in and then get this when the dashboard tries to load.

      Chrome
      image.jpg

      Safari
      image.jpg

      1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch
        last edited by

        The problem by the way is Safari on iOS.

        Relevant thread: http://community.ubnt.com/t5/EdgeMAX/iPad-and-quot-Safari-failed-to-establish-WebSocket-connection/m-p/1118675#M49226

        1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller
          last edited by

          That sucks, were you able to work around it?

          JaredBuschJ 1 Reply Last reply Reply Quote 0
          • JaredBuschJ
            JaredBusch @scottalanmiller
            last edited by

            @scottalanmiller Never bothered to because it is obviously not truly a UBNT issue. All the work arounds involve creating certs and manually importing them into the iOS device, that is not worth it.

            To me this is Safari being bad. Software should do what the user tells it. I told Safari to trust the self signed cert. That means trust the damn cert always. Not just when they want to.

            1 Reply Last reply Reply Quote 1
            • JaredBuschJ
              JaredBusch
              last edited by

              When you perform the same steps on OS X (Yosemite 10.10.1) it does as desired.

              Screen Shot 2015-01-11 at 9.42.13 AM.png

              Screen Shot 2015-01-11 at 9.43.15 AM.png

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post