When you use the Parsec web client in Chrome, you're using a different networking protocol than the native client typically uses. This networking protocol (webRTC) is a standard for low latency video streaming on the web. Unfortunately, it doesn't come with all of the optimizations that we've added for our native low latency game streaming protocol (BUD). On top of having reduced performance versus BUD, webRTC will, at times, fail to make a peer-to-peer connection. The 6200 error represents that scenario. We recommend trying to use the Parsec native client to make a connection to your hosting computer. It has a much higher likelihood of succeeding. You can download the Parsec native application directly from our website for your chosen device.
Articles in this section
- Error Codes - 22006 and 15000 (Unable To Initialize Encoder On Your Server)
- All Error Codes
- Error Codes - 10 (Parsec couldn't find a compatible video decoder)
- Error Codes - 6107 (You Must Re-Authenticate)
- Error Codes - 1406 (Arcade's attempt to capture the game timed out)
- Error Codes - 1407 (Arcade is missing some important files to capture this game)
- Error Codes - 112 (You do not have permission to initiate a connection to this host)
- Error Codes - 13015 (Client disappeared during stream initialization)
- Error Codes - 40000 (Raspberry Pi GPU Memory set incorrectly)
- Error Codes - 6200 (A webRTC Connection Failed)