Troubleshooting by Category

This troubleshooting guide is organized by categories denoted by the section headers (see this page's Table of Contents). This guide will cover common failure modes for the Signals Notebook Connector and steps that can be taken to identify the cause and resolve the issue.

To quickly locate a relevant part of the troubleshooting section, use the browser’s search capability (Ctrl+F or ⌘+F) and type part of the error message or code.

Category: Connector Configuration

HTTPS Not Enabled

When the connector is first started, HTTPS is not enabled because there is no certificate configured. If you try to access the connector at https://<connector-hostname>:<port>/, you will see the message ERR_SSL_PROTOCOL_ERROR. Change the URL to http://<connector-hostname>:<port>/ instead.

HTTPS Enabled

If the connector is configured with HTTPS enabled and you try to access the connector at http://<connector-hostname>:<port>/, you will see a message like ERR_EMPTY_RESPONSE. Change the URL to https://<connector-hostname>:<port>/ to use HTTPS.

Incorrect Hostname or Port

If you try to access the connector and receive a message like ERR_CONNECTION_REFUSED, check the hostname and port in the URL and verify that the connector is running (e.g. with docker container ls).

DNS Error

If after you SSO, through URI Redirect, you encounter a DNS issue, that means either your URI Redirect is set up incorrectly, or your DNS resolver does not have the right entries.

For deployment to localhost ensure that your machine’s host file has the Redirect URI mapped to the right IP addresses.

Category: Tetra Data Platform Settings

🚧

Potential Unrecoverable State...

Incorrect Tetra Data Platform settings can lead to an unrecoverable state (e.g. admin user can’t log in to fix the configuration).

Before making any configuration changes in these areas, you can export the current configuration using the Export Configuration button in the Connector settings screen. The exported configuration will contain all non-sensitive connector settings and DataWeave scripts, and can be imported from the Connector settings screen after resetting the config database.

Incorrect TDP Domain or Subdomain

If the domain or subdomain for TDP is incorrect, any API calls to TDP will fail. This will generally be seen with a message like getaddrinfo ENOTFOUND {hostname}. Correct the TDP domain and subdomain in the Tetra Data Platform settings to resolve the error.

📘

Pre TDP v3.3

For TDP versions before v3.3, leave the subdomain field blank.

Incorrect Organization

If the TDP organization is incorrect, API calls to TDP will fail. This will generally be seen with a message like This user does not belong to the requested organization. Correct the TDP organization in the Tetra Data Platform settings to resolve the error.

Incorrect Service User Token

If the TDP service user token is incorrect, API calls to TDP will fail. This will generally be seen with a message like Invalid token. Correct the TDP service user token in the Tetra Data Platform settings to resolve the error.

Category: Signals Notebook Settings

Incorrect Server URL

If the Signals Notebook server URL is incorrect, API calls to Signals Notebook will fail. Correct the server URL in the Signals Configuration settings to resolve the error.