Help with FAF client - Connecting to Update Server issue

[steady1060]

So over the past two months I have been trying to get FAF to work for me, read all over these forums, and tried many steps. Here's the issue I'm having:

I can start the FAF client fine. It logs in and lets me move around the different tabs. However, I can't start my own game, join a game, or watch replays because every time I do one of those an "Updating FAF" box appears and says "Connecting to Update Server" with an empty progress bar. I looked in my logs, and after attempting to join a game in forever.log I see these lines:

2015-05-05 07:03:54,568 DEBUG faf.downloader Searching map preview for: isis3v3.v0001
2015-05-05 07:04:01,796 DEBUG faf.updater The following error occurred: Connection timed out.
2015-05-05 07:04:01,796 DEBUG faf.updater TCP Error Connection timed out

The last two lines shown show up every. single. time. I tried testing the proxy server option and it always shows an error box saying "FA has failed to start." Here's another clip from my attached log:

2015-05-05 07:02:41,358 INFO faf.fa Running FA with info: {'recorder': u'Steady1060', 'game_time': 1430834561.359, 'uid': -1, 'featured_mod': 'faf'}
2015-05-05 07:02:41,358 INFO faf.fa Running FA via command: "C:\ProgramData\FAForever\bin\ForgedAlliance.exe" /init init_faf.lua /log "C:\ProgramData\FAForever\logs\game.log" /nobugreport /gpgnet 127.0.0.1:49597
2015-05-05 07:02:41,359 ERROR faf.client FA has failed to start
2015-05-05 07:02:42,700 INFO faf.client Outgoing JSON Message: {"state": "off", "command": "fa_state"}
2015-05-05 07:02:42,701 INFO faf.chat autopostjoin: false
2015-05-05 07:02:49,762 WARNING faf.fa Process forcefully terminated.

I looked in C:\ProgramData\FAForever\bin\ and there is no "bin" folder, I assume it will create one and place ForgedAlliance.exe file once it updates FAF client, but since that happens it never launches. I think these errors are connected.

Just to include what I've done:
1. Tried uninstalling both FA (disc install with update) and FAF and re-installing fresh
2. Linked account to Steam
3. Uninstalled FA (disc install) Installed FA through steam
4. Installed FA and FAF on a separate home computer, same exact issue.
5. Tried networking issue troubleshooting, DMZ'd my PC no effect, opened all ports FAF should need no effect, disabled security features of my router etc.
6. Tried creating rules in windows firewall (Running Win7 x64) both outbound and inbound, no effect.
7. Tried disabling windows firewall, no effect.
8. No antivirus installed, but tried running some scans on my PC and they found nothing (its a clean PC anyway)
9. Read about similar issues from various posts on forums and tried every step they did, no effect.
10. Tried Tracert to the address one of those posts listed, direct.something, it went through no issues, no timed out hops etc.

I've never had an issue with anything online-related ever on my internet connection or PC, for what it is worth.


Please help me fix the TCP Error Connection timed out issue!

[steady1060]

Here's the same log after trying again today to update FAF by creating my own game. TCP Time Out again happens. Anyone can help with this?

[steady1060]

No help? Here's the latest log, they are all the same log just with new attempts each time.

[Scales]

Have you started your game outside of FAF via steam?

Are you on a wi-fi connection? I had a terrible time with wi-fi and TCP disconnects.

Have you enabled the UPnP or changed the default port FAF uses?

I'm not a coder but judging by the looks of your logs it just seems to drop the connection part way through with no errors. And judging by the fact the same issue happens on another computer, I would say it's network related. If your router has some logging features it might be of worth to investigate into that.

[steady1060]

Hey Scales, thanks for the reply.

I have started Supcom outside FAF, I play it through steam regularly with Steam's matchmaking service.
I am not on wifi, never been on wifi.

I tried changing port to 9154 and enabling UPnP, here's an error that happened. It's something? New log attached.

2015-05-12 19:04:17,786 INFO faf.fa.upnp Creating UPnP port mappings...
2015-05-12 19:04:17,957 ERROR faf.fa.upnp Exception in UPnP createPortMapping.
Traceback (most recent call last):
File "fa\upnp.pyc", line 58, in createPortMapping
File "<COMObject <unknown>>", line 4, in Add
com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147220976), None)
2015-05-12 19:04:17,957 INFO faf.client The game port is now set to 9154
2015-05-12 19:04:17,957 INFO faf.client sending packet to lobby.faforever.com

[Scales]

Have you enabled UPnP in your router too? Make sure your routers firmware is up to date as well.

[steady1060]

Yes, UPnP has always been enabled on the router. Firmware is most recent. Logging is not an option on this router.

[Scales]

Well I did a quick search on the upnp.pyc script that fails, and low and behold the first thing to come up was a topic on this forum. check it out here:

viewtopic.php?p=59504

It might be your ISP is the cause of your problems.

[steady1060]

I should have thought to search for that, thanks! Looks like I'll be calling my ISP to continue troubleshooting. Ill report back in case others have this issue now or in the future.

I still feel like that may not be the issue though, let me explain: That thread has a guy complaining he has intermittent issues with connections to other players, not the update server. Also, the technology used (DS-Lite, for IPv4 exhaustion issues) is built to allow full functionality, not limit it in any way. My issue is a normal server request for data, not peer to peer connections (which work just fine, I run torrents occasionally). I will still follow up with my ISP and try to track this down, but I don't think they are doing anything to cause this issue - we shall see.

EDIT: For those not wanting to read the other thread by someone else having the UPnP issue, basically it was concluded the ISP is providing pseudo IPv4 addresses to customers because IPv6 is being phased in and no new IPv4 addresses are being handed to customers. With no real IPv4 address by the ISP, issues like this happen, and cannot be fixed apparently. Not sure if I got that right.

[Sheeo]

ISP's arent at fault for doing what they're doing, IPv4 address exhaustion is a thing.

Your particular issue is unrelated to the game and UPnP, which the other thread is about. You're unable to establish an IPv4 TCP connection to our server on port 9001, but somehow able to use our other public ports.