Report reply Stormlilly 3 Posted October 11, 2017 We are finding that it is taking a long time (as in many minutes) to connect initially, then it works quite quickly but drops out sporadically for some users. Is there anything we can do to improve or optimize this ? Thanks! Quote Share this comment Link to comment
Report reply Michael 263 Posted October 11, 2017 i believe this might be related to an issue in 2.6.0 where i am forcing only websockets. i misunderstood something in the socket.io documentation and thought that would be a good thing, but i also have noticed that sometimes i need to refresh once or twice to get it to connect, cause depending on browser/device/internet connection/server load/ping/etc, websockets can take awhile to fully establish. so i've gone back to the default method in 2.6.1, hopefully this will resolve this issue. there are 2 servers currently for babble chat service, one is in North America (NYC) and the other one is in Europe (Amsterdam), European and Asian sites are reporting much better connections with the European server ( i am not sure where your site or a majority of its users are coming from, so if the NA server suits you best, stick with it ). Quote Share this comment Link to comment
Report reply Michael 263 Posted October 11, 2017 Changed Status from Pending to ClosedChanged Fixed In to Next Version Quote Share this comment Link to comment
Report reply Stormlilly 3 Posted October 11, 2017 Hey, thanks Michael. Can you please advise on an estimated timeframe for the release of 2.6.1 The ban user function is needed urgently, is there a fix in the meantime. Thanks! Excellent application. Quote Share this comment Link to comment
Report reply Michael 263 Posted October 11, 2017 Tomorrow at the earliest, there are a few things i need to test out a bit more before rolling out. instead of using /ban, you can use /mute, it will "silence" them for 24 hours Quote Share this comment Link to comment
Report reply Stormlilly 3 Posted October 12, 2017 Thanks for that. We are unable to connect at all now. It just keeps saying Connecting... It was working yesterday with lags, but myself and all of our members are unable to connect at all now. I've tried clearing the forum cache (which helped before) and changing the node server location, no luck. Quote Share this comment Link to comment