Connection and authentication issues
Troubleshoot Dremio connection and authentication issues with error, cause, and solution guidance.
Resolve common connection and authentication issues when integrating Dremio with Atlan.
Connection refused
Connection refused: Unable to connect to Dremio instance
Cause
The Dremio instance isn't available from Atlan, or the REST API isn't enabled.
Solution
- Verify that Dremio is running and available.
- Check that the REST API is enabled in Dremio admin settings.
- Confirm the host and port are correct:
- Dremio Cloud: Port 443 (HTTPS)
- Dremio on-premises: Port 9047 (HTTPS)
- Test connectivity from Atlan environment:
# For Dremio Cloudcurl -k https://your-dremio-host:443/api/v3/info# For Dremio on-premisescurl -k https://your-dremio-host:9047/api/v3/info
- Check firewall rules to make sure the correct port is open.
Authentication failed
Authentication failed: Invalid credentials
Cause
The provided username/password or Personal Access Token (PAT) is incorrect, or the user account doesn't exist.
Solution
- For username/password authentication:
- Verify the username and password are correct
- Check that the user account exists in Dremio
- Test authentication with a simple API call:
curl -k -u username:password https://your-dremio-host:9047/api/v3/info
- For PAT authentication:
- Verify the PAT token is valid and not expired
- Check that the PAT was generated for the correct user
- Test authentication with the PAT:
curl -k -H "Authorization: Bearer YOUR_PAT_TOKEN" https://your-dremio-host:9047/api/v3/info
- Make sure the user has appropriate permissions.
- Reset the password or generate a new PAT if necessary.
SSL certificate error
SSL certificate verification failed
Symptoms include errors such as certificate verify failed, self-signed certificate, or unable to get local issuer certificate.
Cause
Dremio is serving a TLS certificate that isn't signed by a publicly trusted certificate authority—typically a self-signed certificate or one issued by an internal / private CA—so Atlan can't verify it against the public trust store. The certificate may also be expired.
Solution
- Check the certificate's validity and expiration date, and renew it if it has expired.
- For a self-signed or internal-CA certificate, obtain the CA (issuer) certificate that signed your Dremio server certificate (from your platform or security team) and upload it in the CA Certificate field when configuring the connection. See Configure authentication.
- Upload the CA certificate, not the server's leaf certificate, in PEM, CRT, or CER format.
- Atlan trusts the uploaded CA in addition to the public trust store; TLS verification stays enabled.
- Re-run Test Connection after uploading the certificate.
Don't disable TLS verification to work around this error. Uploading the CA certificate is the supported path and keeps the connection verified.
Permission denied
Permission denied: Insufficient privileges
Cause
The user account doesn't have the required permissions to access data sources or spaces.
Solution
- Verify the user has read access to all required data sources.
- Check that the user has access to spaces containing your datasets.
- Make sure the user has appropriate permissions for the data sources and spaces you want to crawl.
- Review and update user permissions in Dremio admin settings.
Timeout error
Request timeout: Connection timed out
Cause
Network latency is too high or the connection is unstable.
Solution
- Check network connectivity between Atlan and Dremio.
- Verify that network latency is under 100ms.
- Make sure sufficient bandwidth is available.
- Check for any network interruptions or packet loss.
- Consider using a VPN if Dremio is in a private network.
Need help
If you continue to face issues, contact Atlan support by submitting a support request.