Looker Troubleshooting

This page lists common issues when connecting Sifflet to Looker. Error messages appear in the connection test report and in the logs of the source details (click the source name in Integrations > Sources).

Authentication

Sifflet Can't Sign In to the Looker API

Symptom: the connection test fails, or the refresh fails with:

Cannot access the Looker API, please check your credentials

Cause: the Host field doesn't point to the Looker API, the API port is wrong, or the client ID and secret in the credential are invalid.

Fix:

1. Check that the Host field ends with /api/4.0, and add the port (:443 or :19999) if needed, as described in Step 2.
2. Check that the credential uses the JSON format with the user (client ID) and password (client secret) keys.
3. If the API key was deleted, generate a new one as described in Step 1, and update the credential in Integrations > Credentials.

Missing Assets

Some Looker Dashboards Are Missing from the Catalog or Lineage

Symptom: some Looker dashboards or explores don't appear in the Sifflet Data Catalog or in the lineage.

Cause: the Sifflet user can't view the folders that contain them, its model set doesn't include their models, or they are LookML dashboards and no LookML repository is connected.

Fix:

1. Give the Sifflet user View access to the folders to catalog, and check that its role's model set includes the models, as described in Step 1. See Looker's documentation on folder access.
2. For LookML dashboards, connect the LookML repository, as described in Step 3.
3. Run the source again from Integrations > Sources.

LookML Repository

The Git Connection Test Fails

Symptom: Test Connection in the Git configuration returns an error.

Cause: the URL doesn't match the authentication type, the credential format doesn't match the Git provider, the token or key has no read access to the repository, or the Git server isn't reachable from Sifflet.

Fix:

1. Use an HTTPS URL (https://...git) with the USER_PASSWORD or HTTP_AUTHORIZATION_HEADER authentication type, and an SSH URL ([email protected]) with the SSH authentication type.
2. Check the credential format for your Git provider, and that the SSH key has no passphrase, as described in Step 3.
3. Check that the token has not expired and has read access to the repository, or that the deploy key is added to the repository.
4. For a self-hosted Git server, check that it's reachable from Sifflet, as described in Network Access.