@mostlostnoob sorry, that's a missreading of what's written.

the operative "it" in the context of this thread was the FAF crash.

I said "running it from steam". which implies it did run.

@deribus thank you very much

GLHF!

@mostlostnoob btw about exception in windows firewall, it's asks is it file/folder/task what should i choose, cause i've chosen folder and add exception for faf client folder

Host candidates are all candidates "harvested" from your network interfaces - virtual or physical. So a 10.x.x.x address or 172.x.x.x appearing that you don't know could be a virtual machine network adapter or a docker network. Other ip addresses could stem from VPNs or other network services (Hamachi, ...)
Server relexive is the ip address a coturn server sees when you connect to it. If 73.157.8.80 is not your public ip, there indeed is a problem. Are you sitting in front of a proxy maybe? What does https://ifconfig.me show as IP?
Relayed candidates are basically the ip addresses of the Coturn servers that offer TURN traffic proxying,

And yes basically all our self-hosted coturn servers get DDoS hammered as soon as we publish the ip.
Global is a 3rd party service that cannot be ddosed.

@mostlostnoob Thanks a lot! It helped!

@kalebalzak Have you tried running a system scan with anti-virus (even Windows Security) to see if there is indeed an infection?

If so & the report came back clean, then I'd suggest that you perform a check of the Windows file system by booting into the Windows Recovery Environment (WinRE). While holding Shift, select Restart from Windows menu. This should get you into the recovery options screen. Navigate to enter Command Prompt, then follow steps 4-7 of this guide to check the Windows file system. At any time you get a message that some changes were made, start back from step 4 & continue until every step clears with no changes being made.

Most likely, your security software is blocking access to the files, or your Windows user account has no permission to access the files.

@stan1234 Recent issues in the past months based apparently upon software/network problems and a persistent DDOS attack.

d432a4c7-b91b-49b8-a01c-695c6f257b72-image.png

В этом пути не должно быть oneDrive или русских букв, нужно создать новую папку где хочешь и прописать путь к ней

@melanol Replays use their own copy of the game files, so even if the replay you're watching is of the game you just played, the client will need to download the game files for the version of the game that the replay is for.

While you can't stop this, you can mitigate some of downloads by enabling "Game data cache" in client > top left menu > Settings > Data and caches. This will tell the client to keep a copy of the game files for the replays you watch so that if you watch another replay with that same version of the game files, it doesn't need to download them again. I would suggest that you review the "Game data cache validity in days" setting to ensure that the client will keep those replay game files for as long as you'd like (use 0 for no time limit).

PM me with your account details and we can sort it out.

For anyone in the future who is looking the same issue up and finds this post, you cannot change your steam link account.

ok nvm, I got it for whatever reason the default was set to 140 width and 39 height, I changed it to 600 by 250 and I am good now.

@anybody00 Since you started your own thread, I'll re-post my original reply there.

How can I do it?

From the logs it looks like your server is trying to connect to localhost 127.0.0.1:80 as if it is the lobby server which won't work. So maybe your host resolution.

From your screenshot it also looks like your client is unable to download the remote config from https://content.faforever.com/dfc-config.json for some ssl reason so it seems like maybe something is wrong with your DNS situation or something