Skip to main content

Error Codes - 800 (Failed request to an endpoint)

Updated

This error means Parsec couldn't contact its servers properly. The most obvious cause is a lack of internet access, but if you have a working internet connection, here are some other reasons this might happen.

 

Blocked from talking to the internet

Parsec may be blocked by the administrator of the network, if in a school or workplace setting. We recommend contacting IT to check that Parsec is correctly approved both in the network and in the machine. Detailed network requirements are available for IT.

In general, it can be worth checking if using web.parsec.app works normally without errors, as that will point out whether the block is specific to the Parsec app on the machine, instead of it being network-wide.

 

Issues caused by network optimizer apps

Some network optimizer apps will try to mess with the Parsec application, and ultimately result in Parsec not being able to talk to the internet. If you have one of these apps, we recommend uninstalling them. Known variants at this time that cause issues are:

  • NetEase / UU Game Booster
  • GearUp Booster

 

DNS issues

Your current DNS settings may not be correctly redirecting to Parsec addresses. To switch the DNS on Windows:

  • Press Windows key + R
  • Type ncpa.cpl and press Enter
  • Double-click the adapter you’re using for internet (usually named ‘Ethernet’ when using an ethernet cable, or ‘Wi-Fi’ for wireless connections)
  • Select ‘Properties’
  • Double-click ‘Internet Protocol Version 4 (TCP/IPv4)’
  • Select ‘Use the following DNS server addresses’
  • Change the Preferred and Alternate DNS servers to 8.8.8.8 and 8.8.4.4 respectively
  • Click OK and Close on all windows to apply the change
  • Open command prompt as administrator
  • Type ipconfig /flushdns and press Enter
  • Restart the computer

 

Microsoft services are disabled

If Microsoft services have been disabled, they can be fixed with the following method:

  • Press Windows key + R
  • Type msconfig and press Enter
  • Change Startup selection to "Normal startup"
  • Click OK and restart the computer

 

Proxy issues

Some regular consumer ASUS laptops have a built in proxy that causes issues with Parsec, and resetting the proxy resolves the issue.

Before resetting the proxy, make sure that you annotate how it currently is set up, in case it breaks something else in your system.

  • Open command prompt
  • Type netsh winhttp show proxy and press Enter

To reset the proxy:

  • Open command prompt as administrator
  • Type netsh winhttp reset proxy and press Enter
  • Try using Parsec

If you need to revert the proxy changes, use netsh winhttp set proxy ? to see examples of how to use the set proxy command.

 

Modified versions of Windows

If you have a modified or stripped version of Windows, or have ran scripts that have modified important parts of the system, Parsec may not work correctly. You can try Parsec on a machine that is not modified to confirm this.

 

Old Parsec version

Some users with old versions of Parsec may have issues with Parsec, and Parsec may not update properly. Try to reinstall Parsec using a newly downloaded installer.

 

Blocked by your internet provider or government

Notably in regions like China, it's possible that your internet provider or government has begun blocking the app.

 

Other reason

If none of the above matches your specific scenario or resolved the issue, you can get help on Discord. Teams or Enterprise customers should create a Parsec Support Ticket.

Related articles