Test a connection
Who this is for: admins and editors who set up connections, and anyone fixing a workflow that fails to reach another system.
Before you start: you need the Manage connections permission (manage_connections), and the secrets the connection uses must be set. See Create a connection.
Test connection sends one real request to the other system, with the sign-in applied, and tells you whether it worked. Use it after you create a connection, after you rotate its secrets, and when a workflow suddenly fails to reach the system.
- Open Connections.
- Find the connection and the environment you want to check: Test or Production.
- Select Test connection.
- Read the result under the button.
Liitora sends one GET request to the connection’s address plus its Path for Test connection (default /). It does not retry. The result is saved on the connection, with Last worked or Last problem.
If the address itself returns an error page, set Path for Test connection to a path that answers a simple GET, such as /health or /v1/me, and test again.
What the result means
Section titled “What the result means”| Status | When | What to do |
|---|---|---|
| Working | The system answered with a 2xx status. The message says the status and how long it took. | Nothing. |
| Partly working | The system answered, but with another status, for example 404. The sign-in probably worked. | Check the address and the Path for Test connection. |
| Not working | Sign-in was refused (401 or 403), the system had an error (5xx), the system could not be reached, or a secret is missing. | See below. |
| Not tested yet | Nobody has tested this setup yet. | Select Test connection. |
Sign-in refused (401 or 403)
Section titled “Sign-in refused (401 or 403)”The card shows a Reconnect hint: “The system refused the sign-in.” The secrets are wrong, expired or lack the rights the system needs.
- Check the credentials in the other system.
- Rotate the secret with the right value, or select Reconnect and pick other secrets.
- Select Test connection again.
For OAuth 2, check the Token URL and Scopes too. If the token request itself is refused, the message names the OAuth error, such as invalid_client.
The system had an error (5xx) or did not answer
Section titled “The system had an error (5xx) or did not answer”The other system is down or overloaded. Try again later. If it keeps happening, check the system’s own status page.
The address is blocked
Section titled “The address is blocked”Liitora only connects to public HTTPS addresses. Private and internal addresses (for example 10.x.x.x, 172.16.x.x to 172.31.x.x, 192.168.x.x, 127.0.0.1 and cloud metadata addresses) are always blocked, also when a public host name points to one of them. Redirects are not followed.
If your system is only reachable inside your own network, Liitora cannot reach it yet. Make it reachable over the internet with HTTPS, for example through an API gateway, and limit access on your side to the address shown in your settings.
The firewall drops the connection
Section titled “The firewall drops the connection”If the test times out or the connection is refused, but the system works from your own network, your firewall may not know Liitora. Allow Liitora through your firewall, then test again.
A secret is missing
Section titled “A secret is missing”The message says which secret has no value. Add the value, then test again.
Ask your AI assistant
Section titled “Ask your AI assistant”Your AI assistant can run the same check with the test_connection tool and explain the result. See the MCP tools reference.