Please wait. Remember that no one immediately can respond to you.
AFAIK, MIT is having server problems of connectivity, MIT is working on a fix right now. I also had similar issues yesterday.
Please wait. Remember that no one immediately can respond to you.
AFAIK, MIT is having server problems of connectivity, MIT is working on a fix right now. I also had similar issues yesterday.
More reports of the Companion failing @ 20%. Perhaps this is a Server-side glitch of some sort?
In the last 10 minutes I succeeded to connect. I tried it in a very simple app and in another one using an extension. In the latter it was a little bit unstable (instead of popping out an error, it closed the companion). I did not do anything to change the 20% (no firewall, no http vs https, etc). Just tried (for 100th time) the companion and worked.
OK, something just occurred to me (sorry).
If you are using WebRTC (aka NOT legacy mode), if the PC and device cannot directly communicate, they will attempt to route their connection through a "turn" server. The turn server we use is located on the network at MIT that has been having issues since yesterday. We believe that network is better, so if this was the problem, it should be gone now.
This would not affect legacy connections.
Bingo! Working ...!
OK, It's Working!!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.