60 replies to this topic

[R.E.M.]

I figured the more data we have the better so I decided to do this too since I don't really have a refresh problem most of the time.

 

I can use all websockets except "Port 443, SSL" but that might be because I'm on a private university network and that port might be blocked.

 

I had the following results from the tracert from my university network.

 

Spoiler

Tracing route to app-prod.tf2center.com [198.27.126.53]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 10.34.90.1
2 1 ms 1 ms 2 ms 10.34.255.29
3 <1 ms <1 ms <1 ms fa10k-resrx4.rtr.lancs.ac.uk [148.88.255.201]
4 <1 ms <1 ms <1 ms iscore-facore.rtr.lancs.ac.uk [148.88.255.22]
5 * * * Request timed out.
6 2 ms 1 ms 1 ms xe-0-2-0.lanclu-rbr1.ja.net [194.81.46.1]
7 4 ms 4 ms 4 ms ae7.manckh-sbr1.ja.net [146.97.41.53]
8 6 ms 6 ms 6 ms ae29.erdiss-sbr1.ja.net [146.97.33.41]
9 9 ms 27 ms 9 ms ae31.londpg-sbr1.ja.net [146.97.33.21]
10 14 ms 10 ms 10 ms ae30.londtw-sbr1.ja.net [146.97.33.6]
11 10 ms 10 ms 10 ms ae29.londtn-sbr1.ja.net [146.97.33.10]
12 10 ms 10 ms 10 ms ae0.lond-gw-ixp4.ja.net [146.97.35.182]
13 * * * Request timed out.
14 * * * Request timed out.
15 91 ms * * nwk-1-6k.nj.us [178.33.100.234]
16 91 ms 91 ms 91 ms bhs-g1-6k.qc.ca [198.27.73.205]
17 87 ms 120 ms 110 ms bhs-4a-6k.qc.ca [198.27.73.222]
18 90 ms 90 ms 90 ms ns220445.ip-192-99-13.net [192.99.13.78]
19 87 ms 87 ms 88 ms 198.27.126.53

Trace complete.

 

I didn't have time to set up a VPN connection sadly, my university makes setting up VPN connections very difficult...

[k-swizzle]

I think it might help to mention that I'm connected from Amman, Jordan and my ISP is the biggest turd there could be: I'm on their best plan and clock 2meg if I'm lucky, making VPN connection absolutely impossible. Might be the reason. Still no improvements on my side although I did manage to connect to a lobby without getting kicked off at the ready up stage earlier. Somehow my reliability has dropped too... no clue if it's linked.. Would be really nice to be able to play without refresh issues anytime soon. As mentioned in my first post on this topic, I didn't experience the bug earlier the first few times I tried tf2c so maybe something changed in one of the updated that were made to the site?

Thanks

[Obnoxious]

It never refresh for me as well, here s some screenshot of your solutions, hope it helps fixing the problem.

 

traceroute : http://hpics.li/2f7ba53

 

socket : http://hpics.li/e3cbc02

[OverkillTASF]

I also encounter this issue. Both with Iceweasel in Linux and Firefox on Windows. Even from completely seperate internet connections in two different cities with two different ISPs. I believe the in-game browser works fine for both (though it can't launch Mumble).

[k-swizzle]

Finding it great how nobody seems to really care about this anymore.. OP is now over two months old and still no fix or even update?

[Some_Thing]

k-swizzle: The issue to be fixed is not an easy one to fix as it's only affecting certain people that don't seem to have any commonality.

 

Some new information which may assist some people with this issue.

 

If you have Hamachi installed, uninstall it and attempt to use TF2Center (after a reboot). A friend of mine has been having the same issue and we've tried different fixes and work around. It seems after uninstalling Hamachi, everything on the site started working for him, including refreshing as it is supposed to.

[talse]

It seems as though running the websocket over ssl would fix it for me, and probably quite a few others. Is this possible? 

[OverkillTASF]

I would be more than happy to test this with a developer. I am a server administrator and have both Windows and Linux machines and can provide testing on both proxied, unproxied, NATed, unNATed, IPv6 and v4. Will collect Wireshark dumps as desired.

For me at home, this is resolved by disabling my SQUID proxy, which is transparently routing ONLY port 80 through the proxy. And hasn't caused any mysterious impact anywhere else.

 

With proxy on, Iceweasel gives me:

 

[20:23:57.941] Iceweasel can't establish a connection to the server at ws://rc.tf2center.com/lobbies?15-IResourceListener.0-&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=1.0.13&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&X-Cache-Date=0. @ http://rc.tf2center....DF811E82.js:638
[20:23:58.056] GET http://rc.tf2center...._=1397262237947 [HTTP/1.1 200 OK 84ms]
[20:23:57.943] "Websocket closed, reason: Connection was closed abnormally (that is, with no close frame being sent)."
[20:23:57.943] "Websocket closed, wasClean: false"
[20:23:57.943] "Websocket failed. Downgrading to Comet and resending"

 

With it off, all works correctly.

 

I am not a web developer so the tons of information available in the web console doesn't mean much to me, and I don't know what to provide.

 

Squid does appear to be passing the traffic correctly, as I receive the expected "TCP_MISS" for an uncached, but valid and proxied, web request. However, if WebSockets ends up then trying to do straight TCP/IP chatter over port 80, a proxy server will definitely get in the mix. For this reason, I would expect most web-socket utilizing websites to do the websockets on port 443, since most proxies have to be configured to just pass 443 traffic through as is. It's possible that Squid will be smart enough to recognize plain-text HTTP on port 443 and not treat it like a CONNECT request... but I don't have a good way to test that at present.

 

Users, make sure you are not behind a proxy. Some of you will know how to do this, some of you will not. Internet security software can silently intercept your web traffic for scanning, as do most corporate Internet connections. Some of you won't be able to address this even if you knew how, due to Internet provider restrictions or just having an overbearing parent like me.

 

TF2Center. Consider running websockets on port 443, or providing an alternate path (HTTPS, secured by a free CaCert certificate) for users who are on "tampered with" connections.

Edited by OverkillTASF, 12 April 2014 - 12:01 AM.

[Birdboy628]

Still no answer? Firefox 28 Windows 7 64 bit.

[MasterNoob]

Gentlemen,

 

I have prepared a test using SSL, using a self generated certificate, therefore you need to manually accept it.

 

https://beta.tf2center.com/lobbies

 

The easiest way to test is just to type a chat msg and see it appearing in the panel. I have also set up a Lobby, so selecting slots should have the same result as chatting (both using websockets).

 

Let me know if this resolves the issue.

 

Cheerz

 

MN

[k-swizzle]

Hello, thanks for the reply- sadly this doesn't seem to have resolved it for me. On a slightly different note, I used to work with a vpn so had config files and  a program called 'Tunnelblick' lying around. I've deleted/uninstalled everything to do with all that though so surely if that was the issue it would have been resolved. Further, I don't nor have I ever owned the program 'Hamachi'. 

Cheers and apologies for being a d*ck in earlier post.

[MasterNoob]

Cheers and apologies for being a d*ck in earlier post.

 

Keep in mind that we have 600 concurrent users on the site on an average day, 31.000 players in our DB; if updates wouldn't work for anyone, that would not be acceptable. So next time, just assume it's you.

 

However, it seems that you can see this yourself now; apologies accepted ;-)

[kKaltUu]

 My teammate has the same problem, all site functions work correctly except for ajax stuff

 

"Websocket closed, reason: Connection was closed abnormally (that is, with no close frame being sent)." jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket closed, wasClean: false" jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket closed, reason: Connection was closed abnormally (that is, with no close frame being sent)." jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket closed, wasClean: false" jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket reconnect maximum try reached 6" jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket error, reason: "

[MasterNoob]

 

 My teammate has the same problem, all site functions work correctly except for ajax stuff

 

"Websocket closed, reason: Connection was closed abnormally (that is, with no close frame being sent)." jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket closed, wasClean: false" jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket closed, reason: Connection was closed abnormally (that is, with no close frame being sent)." jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket closed, wasClean: false" jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket reconnect maximum try reached 6" jquery.atmosphere-ver-29EB4DE0B679C4726DDEDB23DF811E82.js:1977
"Websocket error, reason: "

 

 

you mean Websocket stuff ;-)

 

Anyway; i cant fix his infrastructure. He should try a stock installation of any OS, making sure he's not behind any proxy or anything...

[talse]

Gentlemen,

 

I have prepared a test using SSL, using a self generated certificate, therefore you need to manually accept it.

 

https://beta.tf2center.com/lobbies

 

The easiest way to test is just to type a chat msg and see it appearing in the panel. I have also set up a Lobby, so selecting slots should have the same result as chatting (both using websockets).

 

Let me know if this resolves the issue.

 

Cheerz

 

MN

Yes, that seems to work fine!

[Commander]

Gentlemen,

 

I have prepared a test using SSL, using a self generated certificate, therefore you need to manually accept it.

 

https://beta.tf2center.com/lobbies

 

The easiest way to test is just to type a chat msg and see it appearing in the panel. I have also set up a Lobby, so selecting slots should have the same result as chatting (both using websockets).

 

Let me know if this resolves the issue.

 

Cheerz

 

MN

Yeah it works

[Obnoxious]

it works for me now, gj

[SGH]

Also works for me, can't wait til it goes "official".

[Crack]

I got this bug as well on Google Chrome. I run on the ISP (TPG). I on https://beta.tf2center.com/lobbies I enabled "Auto detect Proxy settings" and it worked fine. On rc.tf2center.com it is still having that bug. 

[Jetz_]

I have the same difficulties, many a lobby have been lost due to this :sad: