I had the same issue. The problem turned out to be the default port used by websockets (8575) wasn't open by default. Once this was opened, the readystate error disappeared.
↧
I had the same issue. The problem turned out to be the default port used by websockets (8575) wasn't open by default. Once this was opened, the readystate error disappeared.