Host leaving room after a few minutes of game, disconnecting all peers. This peers doesn't recognize that they were disconnected. Instead they only know that the Host was. The signalling server (i run my own bought from Scirra) only shows that those peers left the room, it doesn't show anything about the Host. It seems to me that in fact the Host never left the room but, some how, all peers were disconnected at same time for some reason and what seems to them is that the Host was the one that have left the room. This behavior is intermitent. My signalling server is NOT under a SSL. Please help.
Develop games in your browser. Powerful, performant & highly capable.
It has nothing to do with the signalling server if your host and peers were connected and communicating at any point in time. My understanding is that once a peer successfully joins a room, the signalling server should not have anything to do with the peer anymore (it wouldn't know the connection status of any peer either).
Are all testing hosts/peers on a local network? Sounds like a NAT problem. WebRTC is generally pretty good about maneuvering through NATs, but things can go bonkers through double NATs or other more complicated scenarios.
Another possibility is the host connection is just too unreliable to keep the connections alive - this has nothing to do with speed or bandwidth, but more to do with latency jitter and packet loss.
Outside of that I would suspect an event sheet mistake.