Slide 11 of 11

Troubleshoot a failed connection

When Save & test fails, check these first

A failed connection test usually comes down to a handful of causes:

CheckWhy it’s common
URL, port, and protocol (http or https)The wrong port or endpoint is a leading cause of connection failures.
Credentials and token scopeAuth errors often look like connection errors. Confirm the account or token has the permissions the data source needs.
Network reachabilityGrafana must be able to reach the endpoint over the network. A firewall, VPC, or private network can block access.

Tip: Read the exact error message. A 401 or 403 points to credentials or permissions, while a timeout or “connection refused” points to networking.

Learn more

The data source troubleshooting guide covers connection, authentication, and query errors in detail.

Troubleshoot data sources

Script

When you click Save and test and it fails, start with the basics.

The wrong URL or port is a common cause. After that, check your credentials and that your token or account has the right permissions. Authentication problems often look like connection problems, so it’s worth checking both. Grafana also has to be able to reach the endpoint over the network, which a firewall or private network can block.

When you do hit an error, read the exact message. A 401 or 403 points to credentials or permissions, while a timeout or connection refused points to networking. The data source troubleshooting documentation walks through the most common causes and fixes.

Previous Start next section