I have the same problem, and activating VPN did not improve the issue. Could not log in at all, in fact.

Recently I have been unable to join or host games through FAF. It reaches "connecting" screen and stays there. Attempting launching FA from Steam works fine, but then I'm alone. I had codex attempt to troubleshoot, even to use a prior, successful version of the client. It did not work. I'm attaching logs and its summary. Running on Nobara. This did work previously on this operating system.

Uploaded logs, replay, and a .md dump: logs and readme.zip

Edit: I pulled the server repo and threw codex at it:

  In GameConnection._handle_lobby_state() (https://github.com/FAForever/server/blob/develop/server/gameconnection.py), the expected sequence is:

  1. GameState Idle sets the host’s player state to HOSTING.
  2. GameState Lobby immediately calls send_HostGame.
  3. A unit test explicitly verifies this behavior.
  4. That code has not changed since July 27.

  Therefore, the important unknown is whether production receives the client’s game-targeted GameState message through the WebSocket transport. Our local logs prove delivery from FA → ICE adapter → Java
  callback, but not Java client → production server.

  I updated the report with four precise server-log questions.

README.txt

I'm sorry I can't go beyond AI slop on this.