This error means Parsec couldn't contact its servers for some reason. The error itself is pretty cryptic, so we use a separate tool to get a less cryptic code.
People that get this error should run the public.parsec.app/resources/TestHTTP.exe tool. This tool makes requests to various parts of Parsec and some other general sites like Google, and provides an error code if something goes wrong. Check the output for error codes and check if that error is documented below.
Some users with old versions of Parsec may have issues with Parsec, and Parsec may not update properly. Users on Windows/Mac/Linux should just reinstall Parsec, and Android users should update their app. Users on the Pi should check the Pi article’s error 800 section.
If Parsec is the sole thing that fails in the test tool, it may be blocked by the administrator of the network, if in a school or workplace setting.
Parsec can also get blocked by stuff like Bitdefender, or any overzealous firewall set up.
It can also be worth checking if using web.parsec.app works normally without errors, as that will point out whether something on the machine is blocking the requests, instead of it being a network-wide thing.
It's also entirely possible that the connection is acting up temporarily. You can try Parsec at a later time.
If in Russia or another country sanctioned by the US, the error is likely because of US sanctions, which Parsec must enforce due to being US based.
It’s unclear if China is now blocking Parsec or the ISPs have done some generally weird stuff. The affected person can attempt to change their DNS, which some users have said solved their issue.
Code 200 means the request was made successfully (on older versions of the tool, you may see code 403 instead). In the case of code 200 on both parsec.app and parsecgaming.com, check if Parsec is working correctly, as it may have been a temporary blip.
Some people may have successful requests with one URL, but an error code with another, which means something is up specifically with one of those. This may be a sign that a specific URL is blocked by the administrator of the network.