Forged Alliance Forever

Re: Timeout in the lobby

2013-01-05T11:11:38+02:00

Next issue i have very often is that I'm unable to connect to FA Forever.
E.g. today's morning. Window show "Establishing connection..." for more than one minute. I stop it by pressing Cancel and app closed.
In system process viewer is FAForever.exe still running on max CPU usage. To be able run FAForever again i must kill it.
ERROR and WRANING message is saved in log before i stop the application.

Code:: 2013-01-05 09:43:08,220 INFO faf.main >>> --------------------------- Application Launch 2013-01-05 09:43:08,704 DEBUG faf.fa.relayserver initializing... 2013-01-05 09:43:09,780 INFO faf.util Read common stylesheet: client/client.css 2013-01-05 09:43:09,921 INFO faf.util Read common stylesheet: stats/formatters/style.css 2013-01-05 09:43:09,921 INFO faf.util Read common stylesheet: tournaments/formatters/style.css 2013-01-05 09:43:09,921 DEBUG faf.vault Map Vault tab instantiating 2013-01-05 09:43:09,937 INFO faf.replays Replays Widget instantiated. 2013-01-05 09:43:09,937 INFO faf.tutorials Tutorials instantiated. 2013-01-05 09:43:09,953 INFO faf.fa.replayserver listening on address 127.0.0.1:15000 2013-01-05 09:43:09,953 INFO faf.fa.relayserver relay listening on address 127.0.0.1:52605 2013-01-05 09:43:10,046 INFO faf.client Outgoing JSON Message: {"command": "ask_session"} 2013-01-05 09:43:31,480 ERROR faf.client TCP Socket Error: The remote host closed the connection 2013-01-05 09:43:31,480 WARNING faf.client Disconnected from lobby server. 2013-01-05 09:46:27,019 INFO faf.main >>> --------------------------- Application Launch 2013-01-05 09:46:27,503 DEBUG faf.fa.relayserver initializing... 2013-01-05 09:46:28,578 INFO faf.util Read common stylesheet: client/client.css 2013-01-05 09:46:28,703 INFO faf.util Read common stylesheet: stats/formatters/style.css 2013-01-05 09:46:28,720 INFO faf.util Read common stylesheet: tournaments/formatters/style.css 2013-01-05 09:46:28,720 DEBUG faf.vault Map Vault tab instantiating 2013-01-05 09:46:28,734 INFO faf.replays Replays Widget instantiated. 2013-01-05 09:46:28,734 INFO faf.tutorials Tutorials instantiated. 2013-01-05 09:46:28,734 INFO faf.fa.replayserver listening on address 127.0.0.1:15000 2013-01-05 09:46:28,734 INFO faf.fa.relayserver relay listening on address 127.0.0.1:52639 2013-01-05 09:46:28,812 INFO faf.client Outgoing JSON Message: {"command": "ask_session"} 2013-01-05 09:46:50,154 ERROR faf.client TCP Socket Error: The remote host closed the connection 2013-01-05 09:46:50,154 WARNING faf.client Disconnected from lobby server.

EDIT:
OS: W7Pro x64
If i dump a connection to a server i see that is established http & https connection's to port 80 and 443 with downloaded data, but connetion to port 8001 is tried to be established without success.
faforever.log

Code:: 2013-01-05 10:34:22,683 INFO faf.main >>> --------------------------- Application Launch 2013-01-05 10:34:23,151 DEBUG faf.fa.relayserver initializing... 2013-01-05 10:34:24,243 INFO faf.util Read common stylesheet: client/client.css 2013-01-05 10:34:24,368 INFO faf.util Read common stylesheet: stats/formatters/style.css 2013-01-05 10:34:24,384 INFO faf.util Read common stylesheet: tournaments/formatters/style.css 2013-01-05 10:34:24,384 DEBUG faf.vault Map Vault tab instantiating 2013-01-05 10:34:24,384 INFO faf.replays Replays Widget instantiated. 2013-01-05 10:34:24,398 INFO faf.tutorials Tutorials instantiated. 2013-01-05 10:34:24,398 INFO faf.fa.replayserver listening on address 127.0.0.1:15000 2013-01-05 10:34:24,398 INFO faf.fa.relayserver relay listening on address 127.0.0.1:52909 2013-01-05 10:34:24,461 INFO faf.client Outgoing JSON Message: {"command": "ask_session"} 2013-01-05 10:34:45,880 ERROR faf.client TCP Socket Error: The remote host closed the connection 2013-01-05 10:34:45,880 WARNING faf.client Disconnected from lobby server.

connection's tcpdump

Code:: 10:34:24.429257 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [S], seq 117678923, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0 10:34:24.476499 IP 91.229.20.50.8001 > 89.177.xx.xx.52910: Flags [S.], seq 3154141147, ack 117678924, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 6], length 0 10:34:24.476766 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [.], ack 1, win 16425, length 0 10:34:24.477789 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [P.], seq 1:83, ack 1, win 16425, length 82 10:34:24.775766 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [P.], seq 1:83, ack 1, win 16425, length 82 10:34:25.384146 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [P.], seq 1:83, ack 1, win 16425, length 82 10:34:26.585227 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [P.], seq 1:83, ack 1, win 16425, length 82 10:34:27.833401 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [P.], seq 1:83, ack 1, win 16425, length 82 10:34:28.567380 IP 91.229.20.50.8001 > 89.177.xx.xx.52910: Flags [S.], seq 3154141147, ack 117678924, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 6], length 0 10:34:28.567657 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [.], ack 1, win 16425, options [nop,nop,sack 1 {0:1}], length 0 10:34:29.050180 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [P.], seq 1:83, ack 1, win 16425, length 82 10:34:31.452645 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [P.], seq 1:83, ack 1, win 16425, length 82 10:34:34.967445 IP 91.229.20.50.8001 > 89.177.xx.xx.52910: Flags [S.], seq 3154141147, ack 117678924, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 6], length 0 10:34:34.967716 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [.], ack 1, win 16425, options [nop,nop,sack 1 {0:1}], length 0 10:34:36.257492 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [P.], seq 1:83, ack 1, win 16425, length 82 10:34:45.882781 IP 89.177.xx.xx.52910 > 91.229.20.50.8001: Flags [R.], seq 83, ack 1, win 0, length 0

All FAForever.exe's network connection is in attachement.

Statistics: Posted by PaoloCZ — 05 Jan 2013, 11:11

Re: Timeout in the lobby

2013-01-04T22:24:33+02:00

PaoloCZ, I had the exact same issue, exhaustively documented in this thread: viewtopic.php?f=3&t=2657

It had something to do with my FAF account. User "discoverer2k4" was having the same issue also. The problem was resolved by Ze_Pilot changing something on the back end.

Statistics: Posted by dwhitty — 04 Jan 2013, 22:24

Re: Timeout in the lobby

2013-01-04T03:45:49+02:00

Next try after about 20 minutes and works:

forever.log http://pastebin.com/cyRhRCEX
game.log http://pastebin.com/TYJd3rrJ

Statistics: Posted by PaoloCZ — 04 Jan 2013, 03:45

Re: Timeout in the lobby

2013-01-04T03:26:30+02:00

I was so fast with answer. First time I try connect to game lobby works fine, but i exit this game lobby (it's for newbies) and look for better game for me.
I found a game where are 3 players in game lobby, but only gamemaker has a ping and other NIL, again...
I try to rejoin once again, but there was only gammaker. Next player connect after few seconds, but also have NIL.

There are reports:
forever.log http://pastebin.com/2KPT8rsr
game.log http://pastebin.com/Bnwsvp5d

Statistics: Posted by PaoloCZ — 04 Jan 2013, 03:26

Re: Timeout in the lobby

2013-01-04T03:27:22+02:00

Forwarded from viewtopic.php?f=3&t=2669 by Ze_Pilot.
Second check is with disabled antivirus.

After few hours (just now) I try it once again and works fine.
I don't change anything on my PC. I only exit FA Forever around 18:00 and start this time (around 02:00). No programs uninstalled no programs installed no antivirus update.

Statistics: Posted by PaoloCZ — 04 Jan 2013, 03:12

Re: Timeout in the lobby

2013-01-03T20:57:44+02:00

I figured I'd necro this thread instead of creating a useless duplicate one, as I have the same problem. Though, mine has now escalated to the point where I can't play a multiplayer game on FAF at all anymore.

http://pastebin.com/itYesSNi - forever.log
http://pastebin.com/yacVR9Du - game.log
http://pastebin.com/pTek95QB - replay.log

These logs are with the following settings:

DMZ off; ports forwarded: 6112, 9103, 30350 (UDP & TCP).
Antivirus removed.
Computer firewall turned completely off.
Lobby port set to 6112.
uPnP function in lobby unticked.

My attempts at fixing this problem so far:

Putting my router in DMZ mode.
DMZ off; port forwarding ports 6112, 9103, 30350 (UDP & TCP).
Computer firewall completely off.
Computer firewall on with FAF, SupCom and FA as exceptions.
Antivirus removed (still got it removed).
uPnP function in lobby ticked.
uPnP function in lobby unticked.
Game port set to random ports as 3123 (also with uPnP on/off).
Router uPnP on.
Router uPnP off.

Additional info:

Router: Siemens, Gigaset SX551.
That's the only router I'm behind.
Router has a firewall, which I have left turned on at all times.
I'm in the Netherlands.
My provider is KPN.
My computer handles this game with ease.

Statistics: Posted by Mascaraudus — 03 Jan 2013, 20:57

Re: Timeout in the lobby

2013-01-02T21:39:58+02:00

ok, I'm a little frustrated :/

thx for help

Statistics: Posted by rogueleader — 02 Jan 2013, 21:39

Re: Timeout in the lobby

2013-01-02T20:56:31+02:00

Well.. thanx ^^

Statistics: Posted by Harpagon — 02 Jan 2013, 20:56

Re: Timeout in the lobby

2013-01-02T20:22:17+02:00

Only GPG has FA code, they won't give it

I don't know what your problem is, but it's probably beyond the scope of FAF.

Statistics: Posted by Ze_PilOt — 02 Jan 2013, 20:22

Re: Timeout in the lobby

2013-01-02T20:17:55+02:00

i know other play with a different ISP, and he have the same problem

how we can give you the FA code ? or what you want for found the problem ?

i will see for firmware

Statistics: Posted by rogueleader — 02 Jan 2013, 20:17

Re: Timeout in the lobby

2013-01-02T20:15:37+02:00

http://www.forum-orange.com/forums/view ... p?id=25964

Seems that some people have problems with peer to peer (what FA is using) and old firmware of the livebox2.

I guess you will have to update it, you probably should contact the support.

Statistics: Posted by Ze_PilOt — 02 Jan 2013, 20:15

Re: Timeout in the lobby

2013-01-02T20:12:52+02:00

The core of the problem is FA closing your UDP socket for some reason.

I have no control over it (it's not the server asking for doing that:), and I didn't code FA or have access to the source, so I can't know for sure why it's doing it.

But the fact that you have the same ISP is suspicious.. Can you find someone else with the same ISP and router and having, or not, problems ?

Statistics: Posted by Ze_PilOt — 02 Jan 2013, 20:12

Re: Timeout in the lobby

2013-01-02T19:43:00+02:00

Same ISP, also a livebox2 (the problem did not occur with my previous livebox1). I have tried with a dmz, with livebox firewall off and with windows firewall off...
I noticed the option "save logs" was unticked on the faf of the computer I am currently on.. So I cant give them (and the logs I sent in the first post were probably outdated).

Statistics: Posted by Harpagon — 02 Jan 2013, 19:43

Re: Timeout in the lobby

2013-01-02T19:29:09+02:00

i've create a DMZ too, and i've create rule on the nat/pat for 6112 and 8067

problem not solved

Statistics: Posted by rogueleader — 02 Jan 2013, 19:29

Re: Timeout in the lobby

2013-01-02T19:24:02+02:00

mhhh

i've try with firewall and antivirus off, this do not change anythings

Statistics: Posted by rogueleader — 02 Jan 2013, 19:24