What causes BOOTSTRAP_TIMEOUT_DUE_TO_MISCONFIG?

DNS resolution failure preventing the VM from reaching Databricks artifact storage. Firewall or security group rules blocking outbound traffic from the cluster subnet. Slow or unreachable cloud storage causing the bootstrap artifact download to time out. VPC/VNet configuration issue preventing the cluster from reaching the Databricks control plane. Incorrect proxy configuration on the cluster

How do I fix BOOTSTRAP_TIMEOUT_DUE_TO_MISCONFIG?

Check VPC/VNet configuration — ensure the cluster subnet has a route to the internet or to Databricks private endpoints. Verify firewall and security group rules allow outbound HTTPS (port 443) from the cluster nodes to Databricks FQDNs. Test DNS resolution from the subnet by launching a test VM and running nslookup on Databricks FQDNs. Review any recent changes to network configuration, security groups, or VPC routing tables. Check the Databricks documentation for required network endpoints and ensure all are whitelisted

High severitycluster

Power BI Refresh Error:
BOOTSTRAP_TIMEOUT_DUE_TO_MISCONFIG

What does this error mean?

The cluster VM bootstrap process timed out before Spark could start. This is almost always caused by a misconfiguration — typically a network or DNS issue preventing the VM from downloading required components.

Common causes

1DNS resolution failure preventing the VM from reaching Databricks artifact storage
2Firewall or security group rules blocking outbound traffic from the cluster subnet
3Slow or unreachable cloud storage causing the bootstrap artifact download to time out
4VPC/VNet configuration issue preventing the cluster from reaching the Databricks control plane
5Incorrect proxy configuration on the cluster

How to fix it

1Check VPC/VNet configuration — ensure the cluster subnet has a route to the internet or to Databricks private endpoints
2Verify firewall and security group rules allow outbound HTTPS (port 443) from the cluster nodes to Databricks FQDNs
3Test DNS resolution from the subnet by launching a test VM and running nslookup on Databricks FQDNs
4Review any recent changes to network configuration, security groups, or VPC routing tables
5Check the Databricks documentation for required network endpoints and ensure all are whitelisted

Frequently asked questions

Does this error affect all clusters or just new ones?

Usually only new clusters — running clusters have already completed bootstrap. If running clusters also fail, investigate network changes that affected the entire subnet.

What FQDNs does Databricks require?

See the Databricks documentation for your cloud provider — the list includes control plane endpoints, artifact storage, and log delivery endpoints specific to your region.