Client doesn't start, not connecting to assign server

[jesup]

I installed FAH on my Win10 machine; it doesn't seem to start. It runs (see it in Process Explorer) but is totally idle, but FAHControl can't contact it. When I kill it and run it from a Powershell, it fails with an unable to rename logfile. If I run it with --log foo.log, it starts and I get a dump of data about FAH and my machine, and this I get this:
16:05:56:<config>
16:05:56: <!-- Folding Slots -->
16:05:56:</config>
16:05:56:Connecting to assign1 . foldingathome . org : 8080

and it sits there forever. I can connect to assign1 via telnet on port 8080 no problem. I've repeatedly uninstalled, made sure all traces of it are removed and reinstalled. I've rebooted.

GPU is a NVidia 1070; CPU is Ryzen 3600. 32 GB ram.

[Joe_H]

If you are running some types of anti-malware or firewall software, they block HTTP & HTTPS connections if they are not from "known" browsers. The client FAHClient process acts like a browser to download and upload. So if this is the case, then an exception will be needed for FAHClient to allow HTTP and HTTS over ports 8080 and 80.

[jesup]

This is normal windows with only the built-in Windows Defender. I also tried allowing FAHClient.exe through the firewall explicitly; it appears to make no difference.

[Joe_H]

People more familiar with Defender hopefully will comment, I am not familiar with it and the Windows PC's at work use another software instead of Defender.

The same problem may be an issue if you are behind an institutional or corporate firewall if that applies to your situation.