Verification errors for an endpoint

When verifying an endpoint, you may run into some errors in the Redox dashboard. These errors originate from your system as a result of Redox sending the verification request with the verification token.

There are four main types of errors:

  1. HTTP response code
  2. Error code
  3. Error message: Destination endpoint is not available.
  4. Error message: Production and staging applications must use HTTPS.

HTTP response code

After clicking the Verify & Save button on the Endpoint > Settings page, you may receive an error with a 4XX HTTP response code.

Why: This means that your system considered the verification request from Redox as invalid. It's possible that there's an error in your system configuration.

What should you do:

  • Make sure that your endpoint URL is correct (i.e., no typos).
  • Make sure that your system is configured to handle verification tokens and support POST requests.

Error code

After clicking the Verify & Save button on the Endpoint > Settings page, you may receive an error code.

Why: This means that Redox couldn't actually deliver the verification request. It's possible that your system timed out or didn't respond to the verification request.

What should you do:

  • Make sure that your endpoint URL is formatted correctly.
  • Make sure that your system is running and successfully receiving POST requests.

Destination endpoint isn't available

After clicking the Verify & Save button on the Endpoint > Settings page, you may receive an error message that says: Destination endpoint is not available.

Why: This means that the endpoint URL that you entered is being used for another dashboard organization.

What should you do:

  • Make sure that you use a unique endpoint URL for your organization.

Production and staging applications must use HTTPS

After clicking the Verify & Save button on the Endpoint > Settings page, you may receive an error message that says: Production and staging applications must use HTTPS.

Why: This means that the endpoint URL is missing the "s" in https.

What should you do:

  • Make sure that you add the "s" in https of the endpoint URL.