|
shallowdeep -> RE: Anyone Else struggling with CollarChat? (4/27/2013 1:38:29 AM)
|
General response to perhaps add a bit more understanding to the situation, albeit with a bit of speculation:
The problem, when it occurs, is completely independent of browser. I've done a few packet captures with Wireshark, and the failure occurs while attempting to establish the TCP connection with Collarchat's server. To establish a connection over which data can subsequently be exchanged, your computer and the server need to complete a "handshake" first, essentially to agree on how to communicate further. The data sent in the handshake is minimal and does not identify your OS or browser, so the server is unaware of the type of device trying to establish a connection during the process. Where the system has been breaking down is that computers requesting a connection have not been receiving a response to the first step of the handshake. After trying several times and getting no response, the requesting computer eventually gives up on the connection and the browser then displays an appropriate error about the failed connection. A browser doesn't get around to identifying itself until the HTTP GET request, which is never actually being made because the TCP handshake fails to complete. The bottom line? Switching your browser and OS will have no effect on the problem.
The problem does not appear to be with Collarchat's server. The server, as far as I am aware, has been up and functioning for the entire time the problem has persisted and doesn't appear to be overloaded. As noted in this thread, some users, like MasterG2kTR, have had no problems connecting. There is a chance that the server is intermittently deciding to preferentially ignore requests from certain IP addresses or ranges, but I don't think this is likely to be the case.
Instead, the issue is more likely to be that the paths along which data is sent from some users' computers to the server are never actually connecting with the intended destination. Some paths work fine, others don't. The path used to reach the server is heavily dependent on your location and ISP, but there can also be a relatively random element to it, as the Internet routes packets dynamically based on a number of factors and even data sent between the same two computers will not always take the same route. This accounts for users who are sometimes able to get through after repeated attempts – that successful request happens to get routed along a working path. Clicking on a magic combination of links before attempting to load the page won't do anything to improve your odds of success, so you can feel free to stop that – unless it happens to make you feel better. :)
These sorts of routing problems can be a bit difficult to diagnose and fix because they may not be consistently reproducible and can be caused by external network factors not under the control of the site administrators, or even of the site's hosting company. That said, I know that I, for one, would welcome more communication about the issue if it happens to recur yet again.
It looks like things are working at the moment, but if they should go south again, some suggestions of things to do that have a little more than voodoo behind them:
Verify the problem is not just with you. A very simple site like downforeveryoneorjustme.com or isup.me is a good first place to try. However, even if those sites show it as being just your problem, you may want to double-check with a more comprehensive service that tests from more than one location, like this one. If the outage seems to be affecting more locations than just you, consider notifying support.
If possible, switch the ISP you use to connect. With phones and tablets that have both WiFi and a cellular connection, this can mean simply using the other connection. The difference in the service provider is likely to see your packets routed differently and may allow you to connect reliably, as theshytype observed.
If possible, try using some proxy servers. A proxy adds an intermediate destination between your computer and the final destination server. This may force traffic with the server along a working path.
TL;DR:
To users:
- Switching browsers or OSes will not help you to access the site.
- Neither will clicking on specific links to get here, or specific combinations of links.
- Switching the network or network path you use to connect, on the other hand, may help.
- The problem may be more difficult to fix than it would appear, so patience won't hurt.
To admins:
- More communication about the issue, as time permits, would be awesome.
|
|
|
|
