---
slug: connection-problems
title: Connection Problems
section: Reference
description: Diagnose Connector failures against databases, warehouses, object storage, or APIs.
listed: false
---
# Connection Problems

**Use this page to diagnose Connector failures against databases, warehouses, object storage, or APIs. The fastest path is to prove reachability first, then credentials, then permissions, and finally TLS.**

## Checklist

Work through these in order:

- **Reachability**: confirm the source is reachable from your network (DNS, VPN, firewall rules).
- **Connection details**: verify the host, port, database, and warehouse values.
- **Credentials and permissions**: verify credentials, and make sure the role still has access to the tables you query (least-privilege still needs enough privilege).
- **TLS**: confirm TLS requirements. Some sources require TLS and specific CA certificates.

## Common errors

### Authentication failed

Try:

- **Reset** the password or Token.
- **Allow-list** your IP or network on the source side.
- **Check** role, schema, and object grants.

### Connection timed out

Usually one of:

- Firewall or security group blocking the port.
- Wrong port.
- VPN split-tunnel issue.

### SSL or TLS errors

Usually one of:

- Missing CA certificate.
- Wrong TLS mode.
- Certificate hostname mismatch.

## Next steps

If you are still stuck, gather:

- **Source type and version** (for example, Postgres 15, Snowflake, S3).
- **Exact error message** from OrcaSheets.
- **Whether it works from another client** (for example, `psql`, DBeaver).

Then contact support with that bundle.

## Related pages

- [Connectors](/docs/connectors)
- [Data Import Errors](/docs/data-import-errors)
- [Performance Issues](/docs/performance-issues)
- [Access Control & SSO](/docs/access-control-sso)