Troubleshoot verification errors for an endpoint

Last updated: Nov 20, 2024

SUPPORT

HEALTH TECH VENDOR

IMPLEMENTATION

You may run into errors when trying to verify a destination, or endpoint, in your Redox organization. This happens when Redox can't successfully reach or deliver to the destination.

We let you know if something's wrong by returning an HTTP or error code from the destination system. Your destination can't be verified until the issue triggering the error is resolved.

Generally, make sure that:

Your endpoint URL is correct (i.e., no typos).
Your system is configured to handle verification tokens and support POST requests.
Your system is running and receiving POST requests.

Reference material

Review these articles for background information:

HTTP response code

You may receive an error with a 4XX HTTP response code if your system considers the verification request invalid. If so, there may be an error in your system configuration.

Tip for masked secret values

When pasting values into masked fields (e.g., secrets, passwords, tokens) for auth credentials, make sure you don’t accidentally copy extra whitespace in the string. Extra whitespace will result in an authentication error when trying to verify the destination.

Pro tip: We recommend first pasting a value for masked fields into a text editor between quotes to check for extra whitespace.

Cloud destinations

For cloud destinations, you may receive a 4XX HTTP response code if your cloud permissions or configuration aren't set up correctly. For example, if you reference a cloud storage bucket that doesn't exist, the verification request will result in an error.

Check these cloud error response docs for more troubleshooting help:

Cloud provider	Reference docs
GCP	Google Cloud Storage (GCS) errors Cloud Healthcare API errors
AWS	S3 errors HealthLake errors
Microsoft Azure	Fabric errors Health Data Service docs Data Lake errors
Snowflake	If you're using Snowflake, the error messages are actually coming from your cloud provider's storage solution (i.e., S3 for AWS, GCS for Google, Datalake or Fabric for Azure). See their docs for troubleshooting help.
Databricks	If you're using Databricks, the error messages are actually coming from your cloud provider's storage solution (i.e., S3 for AWS, GCS for Google, Data Lake or Fabric for Azure). See their docs for troubleshooting help.

Error code or message

You may receive an error code or message if Redox can't deliver the verification request. Your system may have timed out or didn't respond to our verification request.

Here are examples of errors you might receive.

Error message	Notes
ENOTFOUND	The endpoint isn't publicly accessible. Remember that to successfully receive data, your endpoint must (a) be publicly accessible from the internet; (b) accept POST requests; and (c) use SSL/TLS encryption (not relevant to development environments).
Destination endpoint is not available	Another dashboard organization is already using that endpoint URL. Make sure to use a unique endpoint URL for your organization.
Production and staging applications must use HTTPS.	The endpoint URL is missing the "s" in https. Add the "s" in https of the endpoint URL.
UNABLE_TO_VERIFY_LEAF_SIGNATURE	There's a certificate issue with the endpoint's system. It's likely that the wildcard is listed twice. Make sure to follow the correct certificate format. This should be the leaf (i.e., wildcard cert) followed by the issuer/intermediate certificate.

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.