Didn't find good vpn yet, but found another interesting thing: this bug also occurs when trying to host new game. So, i doubt it's vpn problem.
FAF Client sometimes show error and stop connecting to custom/coop game
Still the problem is present. Maybe get latest build from github and debug it myself? Tired of this silly error...
Google sez WSAEINTR can be caused by a firewall. To see if that's a network issue and not something with the game, try running the FA exe directly and launching a lobby from there.
@mazornoob I have firewall off. And FA don't launch directly. And I even can't host new campaign games
Could it be the reason?
2023-06-28 22:46:20.367 INFO Ice Servers set, total addresses: 18 (c.f.iceadapter.ice.GameSession:170)
2023-06-28 22:46:20.367 INFO Sending Response:{"result":null,"id":1,"jsonrpc":"2.0"} (com.nbarraille.jjsonrpc.JJsonPeer:574)
2023-06-28 22:46:20.482 WARN Failed to ping coturn1.faforever.com (c.f.iceadapter.util.PingWrapper:52)
2023-06-28 22:46:20.517 WARN Failed to ping coturn2.faforever.com (c.f.iceadapter.util.PingWrapper:52)
2023-06-28 22:46:20.560 WARN Failed to ping coturn3.faforever.com (c.f.iceadapter.util.PingWrapper:52)
2023-06-28 22:46:20.600 WARN Failed to ping coturn5.faforever.com (c.f.iceadapter.util.PingWrapper:52)
2023-06-28 22:46:20.654 WARN Failed to ping anz1.coturn.faforever.com (c.f.iceadapter.util.PingWrapper:52)
2023-06-28 22:46:20.751 WARN Failed to ping coturn4.faforever.com (c.f.iceadapter.util.PingWrapper:52)
2023-06-28 22:46:22.187 WARN Close requested, stopping... (c.f.iceadapter.rpc.RPCHandler:139)
2023-06-28 22:46:22.187 INFO close() - stopping the adapter (com.faforever.iceadapter.IceAdapter:158)
2023-06-28 22:46:22.189 INFO GPGNetServer stopped (c.f.iceadapter.gpgnet.GPGNetServer:253)
@zorg-kirill said in FAF Client sometimes show error and stop connecting to custom/coop game:
To make it more clean and easy, I deleted all logs, launched SCFAF and managed to get an error from the first attempt. Here are screenshots/fresh logs:
So, the error code is the same, but now it don't point at "game log" or any log. So there is another bug with wrong error alerts. And in my opinion, the main error might be somewhere in ICE adapter.
it's in lobby, like in this screenshot
@sheikah btw, if I ping these servers in CMD, everything works fine, no packets lost