FORPRO-REMOTE / SUPPORT
Find help by error code
Enter the error code from your app (REPC-xxxx) or a symptom to see where the error occurred and what to check.
34 results
Unclassified error
When contacting support, include this code, the failed stage and the detailed reason.
REPC-1001Sign-in failed or required
Check your sign-in details, then sign in again.
REPC-1002You do not have permission to connect or perform this action
Ask the host owner to check the access permissions, tier and approval settings.
REPC-1003Server request failed
Check the connection to the forpro-remote server and its API response, then try again.
REPC-1004Remote PC is unavailable
Refresh the computer list, then check that the remote PC is online and sharing.
REPC-1005Connection approval failed
Ask the remote PC owner to check your connection request, then try again.
REPC-1006Connection approval timed out
Try connecting again when the remote PC owner can approve your request.
REPC-1007Invalid server response
Record the error reason in the response and check that the app and server versions are compatible.
REPC-2001Could not find a direct connection route
Check LAN discovery results and STUN/NAT records on both PCs. A STUN failure alone does not show that UDP is blocked.
REPC-2002Direct UDP connection failed
Check the remote PC and the connection route. On both PCs, check that the firewall allows UDP traffic for forpro-remote.
REPC-2003UDP connection attempt timed out
Compare the route/punch logs and NAT settings on both PCs. The timeout alone does not identify which device blocked the connection.
REPC-2004Secure handshake timed out
Check the handshake and identity logs on both PCs, then try again.
REPC-2005Could not verify the host identity or session authorization
Check the remote PC identity and session authorization. Do not skip certificate verification.
REPC-2006Local UDP port is unavailable
Check which process on this PC is using the requested UDP port. Try again with an available port.
REPC-2007The connection ended unexpectedly
Check whether the host stopped or the network changed on either PC, then reconnect.
REPC-3001Could not start the remote screen renderer
On the PC you are connecting from, check the GPU driver and the renderer backend named in the detailed reason.
REPC-3002Could not start the video decoder
On the PC you are connecting from, check the codec runtime and GPU support. Try a supported codec and pixel format.
REPC-3003Could not capture the remote PC screen
On the remote PC, check the selected display, screen capture permission and capture backend.
REPC-3004Video encoding failed on the remote PC
Check the encoder runtime and driver on the remote PC. Try again with supported resolution, codec and HDR settings.
REPC-3005Virtual display operation failed
Check the VDD driver and display setup on the remote PC, along with the response to the display add or select request (ADD/SELECT).
REPC-3006The first video packet has not arrived
Compare the remote PC capture, encode and send counters with the receive counters on the PC you are connecting from.
REPC-3007The first video frame is incomplete
On the PC you are connecting from, check packet loss, frame assembly and the stale-frame count.
REPC-3008Video decoding failed or stalled
Compare the assembled and decoded frame counts, and check the decoder error.
REPC-3009Decoded video is not showing on screen
Check the rendered-frame count, the window on the PC you are connecting from and any GPU presentation errors.
REPC-4001Audio operation failed
Check the selected audio device and its permissions, along with any audio capture or playback errors.
REPC-4002An input operation failed
Check input permissions and the interactive input helper on the remote PC.
REPC-4003Virtual gamepad error
Check the ViGEmBus driver on the remote PC and the result of the virtual controller connection.
REPC-4004Operating system permission is required
In your operating system settings, allow the permission named in the error reason, then try again.
REPC-5001Could not start the remote process
Check that you can access the installed executable and the runtime files it needs.
REPC-5002Remote process exited before the first frame
Collect the child process log and crash report. The last recorded stage alone does not explain why the process exited.
REPC-5003Stage completion was not reported in time
Check the last recorded stage, its counters and the child process status before trying again.
REPC-5004Could not apply the settings
Check the setting value, whether the device supports it and the response from the remote PC.
REPC-5005Local file or interprocess communication failed
Check storage space on this PC and permission to access the forpro-remote state directory.
REPC-5006Could not start the host
Check the host service or process log for the component that failed to start.