In addition to that, finding ways to break things is significantly easier in general. When the DDoS attack started, it made the game unplayable for everyone. After all the back-end changes to counter it, at least the majority of players can play again. I know it is extremely frustrating when a connection drops. It would be helpful to follow MostLostNoob's guide to share some logs with us. This can help determine if your issue is not DDoS-related and ensure all information is available.

Pinpointing lag issues can be very challenging - Especially with Supreme Commander, as it is using P2P. If you are far from other players, this could cause lag with some, but not all players. If your internet connection is poor, you can encounter issues as well. You could try to determine the quality of your connection. If it has no issues, you can try to find out if certain players from other countries cause the lag with you (The country flag in the lobby tells you where they are located) You can try to change the coturn server in the FAF client to something else (see client options), but I have no idea if that will be helpful in your case. But testing does not hurt.

@lydeker Try adding an exclusion/exception for the FAF Client in your anti-virus software & Windows Security.

@MostLostNoob you're a godsend. how was that not fixed when i reinstalled tho. im sure i logged in. well whatever; thanks a lot

@magge ah yes it was security software interfering, i did take a browse at other peoples problem and saw it was a common issue and it was probably the only solution i didnt test for whatever reason.. Thank you tho appreciate it

@magge it would appear it was the ai mod, played a three hour game last night only thing was lag which is expected with all the units, changed the map file path so that may have been the fix as well but as of now im finding no issues.

client.log Sorry if this was needed first. First time asking for help

@blackhart All versions of SCFA have a difficult time with using network storage systems like OneDrive, Dropbox, etc.. To get around this for FAF, you'll need to: go to FAF client > top left menu > Settings > Forged Alliance Forever > Maps and Mods Location > Choose... navigate to a location outside of OneDrive either select an already existing folder or create a new folder for where FAF will store your maps/mods & then select the new folder double-check the new path to ensure that it's not in OneDrive

2024-04-23T22:50:47.702+03:00 DEBUG 1088 --- [FAF Client] [JavaFX Application Thread] c.faforever.client.steam.SteamService : Steam API stopped omg=/ if steam app closed, faf not working. thx

This should now be fixed

@karbonforms said in FAF Client: Nothing works.: java.lang.RuntimeException: java.io.IOException: Cannot run program "rundll32": CreateProcess error=740, The requested operation requires elevation Caused by: java.io.IOException: Cannot run program "rundll32": CreateProcess error=740, The requested operation requires elevation Caused by: java.io.IOException: CreateProcess error=740, The requested operation requires elevation > java.io.IOException: Cannot run program "C:\ProgramData\FAForever\bin\ForgedAlliance.exe" (in directory "C:\ProgramData\FAForever\bin"): CreateProcess error=2, The system cannot find the file specified > Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified These lines suggest that you have insufficent permissions to run whatever was passed to rundll32, I'm guessing that's launching the browser or You haven't linked the FAF binary correctly.

@mostlostnoob said in Problem when authorizing Client - ERR_CONNECTION_REFUSED: @samae1 Try either changing the Default Browser in Windows Settings &/or clearing your browser cache. @Samae1 May I suggest Vivaldi. I know Windows is getting increasingly obtuse with how you go about changing your default applications like the browser.

Still an issue. Any update?

Well, we found the problem and it was the anti-virus he had, everything works fine now, thanks to those who have readed my post

Короче я исправил баг В командной строке ( через администратора) Я вёл sfc /scannow

Thanks, magge!