Skip to main content
Skip table of contents

Troubleshoot ROAD Clients / InstaRecorder

Sometimes, ROAD Clients will not behave as expected. More often than not, this is because of a misconfiguration!

On this page, we will walk you through some the most encountered cases of misconfiguration, and how you can resolve it.

Error messages when starting the client

Error no valid settings.json found

If you encounter the following message:

Solution

You probably missed a step in the configuration process!

Please check the Configure settings.json page, and make sure that:

  • The file settings.json is present and readable for the web server process

Error settings.json file may contain a syntax error

If you encounter the following message:

Solution

You probably made an error will configuring the settings.json.

Please check the Configure settings.json page, and make sure that:

  • The settings.json is correctly written and is a valid json file

Error DPE URL is missing in the settings.json file

If you encounter the following message:

Solution

You probably forgot the dpeUrl in the settings.json.

Please check the Configure settings.json page, and make sure that:

  • dpeUrl parameter should be written correctly and contain a valid url pointing to your DPE instance

Connection error with ROAD

If you encounter one of the following messages:

The currently configured default ROAD Service is unreachable - Please select a valid ROAD Service and consider changing your default ROAD Service on DPE Parameters.

Connecting to https://my-road-service:11005 failed! Please make sure the ROAD Service is running and accessible, and try again.

Solutions

Is ROAD Service running?

Make sure the ROAD Service is currently running and accessible via network.

Change ROAD Service

If the ROAD Service you are connecting to is often unavailable, consider changing your default ROAD Service. More information on the Configure common Parameters for all clients page.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.