Skip to main content

Troubleshooting

When Test connection fails, the message names the problem. This page groups the messages the engine can give, with what to check. The wording of each message is the engine's own.

Terms used on this page (11)
  • FHIR - Fast Healthcare Interoperability Resources - a modern web API standard for health data
  • SFTP - SSH File Transfer Protocol - file transfer over a secure SSH connection
  • FTPS - FTP with TLS - file transfer on a plain FTP server, encrypted
  • TLS - Transport Layer Security - the encryption behind https:// and secure sockets
  • IMAP - Internet Message Access Protocol - reads mail from a mailbox
  • SMTP - Simple Mail Transfer Protocol - sends mail
  • STARTTLS - a way to switch a mail connection to TLS after it has started
  • AMQP - Advanced Message Queuing Protocol - the protocol RabbitMQ speaks
  • SAS - Shared Access Signature - an Azure token that grants limited access to a storage container
  • WSDL - Web Services Description Language - the document that describes a SOAP service
  • DNS - Domain Name System - turns a host name into an address

See the Glossary for every term.

Can't reach the system​

The message saysWhat to check
Not reachable: no answer when connecting.The address, the network, or a firewall on the other side.
Not reachable: connection refused.Nothing is listening on that port, or a firewall is blocking it.
Not reachable: the address could not be found (DNS).The host name is misspelled or not resolvable from the engine's machine.
No answer within 8 seconds.The address and port, or a firewall dropping the connection.
The secure (TLS) connection failed.The certificate is not trusted, or the other side does not use TLS on that port.
The address is not valid. / Could not read a host from the JDBC URL.The address format. For a database, include the port, e.g. host:1433.
Write each broker as host:port.A Kafka broker in the list has no port.

Reached, but the wrong kind of server​

The message saysWhat to check
Something answered on that port, but it is not an SSH/SFTP server.The SFTP port (usually 22).
…not an FTP server.The FTP port (usually 21).
…not an AMQP (RabbitMQ) server.The RabbitMQ port (5672, or 5671 with TLS).
…not an IMAP mail server. / …not an SMTP mail server.The mail port: IMAP 993; SMTP 465 or 587.
The address answered, but not with a FHIR CapabilityStatement.The base URL must end at the FHIR root.
The address answered, but not with a WSDL document.The WSDL URL.
The token URL answered HTTP …Check it is the server's OAuth token endpoint.

Reached, but sign-in or access failed​

The message saysWhat to check
Reachable, but the username or password was rejected.The account and password (FTP, database, mail).
Reachable, but the credential was rejected (HTTP 401 / 403).The Basic, Bearer or API key credential.
Reachable, but the client ID or secret was rejected.The OAuth client ID and secret of the FHIR server.
Reachable, but the SAS token was rejected or has expired, or lacks list permission.The Azure token: it needs list and read (inbound) or write (outbound), and must not have expired.
The FTP server does not offer TLS (AUTH TLS).Turn FTPS off, or ask for it to be enabled.
The mail server did not accept a sign-in… It may need TLS on another port.The mail port and TLS setting.
The mail server offered STARTTLS but refused it.The mail server's TLS configuration.

Found it, but not what you asked for​

The message saysWhat to check
Signed in, but the folder '…' does not exist or cannot be opened.The FTP folder name.
Signed in, but that database does not exist.The database name in the JDBC URL.
There is no bucket called '…'. / The bucket exists, but in a different region.The S3 bucket name and its region.
The container was not found in that storage account.The Azure container name.
The server answered, but … was not found (HTTP 404).The path.
The server redirected the request (HTTP 3xx).Use the final address, usually https://.
Reachable, but the server answered with an error (HTTP 5xx).The problem is on the other system's side.

Folder problems​

The message saysWhat to check
That is not a valid folder path. / The folder does not exist on the engine's machine.The path, from the engine's machine, not yours.
That path is a file, not a folder.The path should end at the folder.
The engine cannot read this folder - check its permissions.Read permission for the engine (inbound).
The engine cannot write to this folder - check its permissions.Write permission for the engine (outbound).

Inbound port and webhook problems​

The message saysWhat to check
Port N is already in use on this engine. Choose another port.Another program or connection already uses that MLLP port.
The webhook path is rejectedThe Path may use letters, digits and dashes only.
Set a shared secret before switching it on.A webhook with no shared secret accepts nothing safely - set one and give it to the partner.

Incomplete settings​

If a required setting is blank, the test says so instead of reporting a network failure (for example, A password or a private key is needed for SFTP). Fill in the missing setting and test again.

It tested fine, but the connection shows "Not live"​

A passing test and Carries orders are different things. Hover over Not live in the connections grid for the reason. Reasons the engine gives include:

  • A webhook has no shared secret.
  • The format does not carry orders yet - for example CSV needs a mapping into the order first.
  • An MLLP port is missing, outside 1024–65535, used by two connections (both stop), or taken by another program.
  • An SFTP connection has no Server host key, or the key does not match - the engine then reads nothing, so an impostor server cannot feed it orders.
  • The connector is not one of those that carry orders yet. See Stage 1 and Stage 2.

Still stuck?​

Each connector page has a Worked example that you can load with Fill example and a list of things to check. Start from Connector reference.