What causes PackageHubNotReachable?

The CI/CD runner or dbt Cloud agent does not have outbound HTTPS access to hub.getdbt.com. A corporate firewall or proxy is blocking the request to the dbt Hub domain. The dbt Hub service is experiencing a temporary outage. The runner's DNS cannot resolve hub.getdbt.com

How do I fix PackageHubNotReachable?

Step 1: Test connectivity from the CI runner: curl -I https://hub.getdbt.com.. Step 2: If hub.getdbt.com is blocked, switch all hub packages to their direct GitHub git format in packages.yml.. Step 3: For corporate proxies, configure the HTTPS_PROXY environment variable in the CI pipeline.. Step 4: Check the dbt status page (status.getdbt.com) to rule out a hub service outage.. Step 5: Cache the packages directory between CI runs to avoid redundant hub fetches when package versions have not changed.

Medium severityconnection

Power BI Refresh Error:
PackageHubNotReachable

What does this error mean?

The 'dbt deps' command could not connect to hub.getdbt.com to resolve package metadata, causing the install to fail with a network connectivity error.

Common causes

1The CI/CD runner or dbt Cloud agent does not have outbound HTTPS access to hub.getdbt.com
2A corporate firewall or proxy is blocking the request to the dbt Hub domain
3The dbt Hub service is experiencing a temporary outage
4The runner's DNS cannot resolve hub.getdbt.com

How to fix it

1Step 1: Test connectivity from the CI runner: curl -I https://hub.getdbt.com.
2Step 2: If hub.getdbt.com is blocked, switch all hub packages to their direct GitHub git format in packages.yml.
3Step 3: For corporate proxies, configure the HTTPS_PROXY environment variable in the CI pipeline.
4Step 4: Check the dbt status page (status.getdbt.com) to rule out a hub service outage.
5Step 5: Cache the packages directory between CI runs to avoid redundant hub fetches when package versions have not changed.

Frequently asked questions

Can I avoid hub.getdbt.com entirely for package installation?

Yes. Replace all hub package references with the equivalent git format pointing to the package's GitHub repository and a specific revision. This bypasses hub.getdbt.com and resolves packages directly from the source.

Does dbt Cloud use hub.getdbt.com or resolve packages differently?

dbt Cloud managed environments run dbt deps using the same hub.getdbt.com endpoint. dbt Cloud agents (self-hosted) depend on the agent's network access. If your agent cannot reach hub.getdbt.com, use git-based package references.