- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2026 11:37 PM
Hi @somnii
First check whether the notebook is running on Serverless or Classic compute, because the troubleshooting path is different.
A quick test can separate DNS resolution from HTTPS connectivity, replace your host and try this:
import socket, requests
host = "api.example.com"
try:
print("DNS:", socket.gethostbyname(host))
except Exception as e:
print("DNS failed:", e)
try:
print("HTTPS:", requests.get(f"https://{host}", timeout=10).status_code)
except Exception as e:
print("HTTPS failed:", e)You can also run:
%sh
curl -I -v https://api.example.comcurl -v is useful because it can quickly show whether the failure is at DNS resolution, TCP connection, TLS handshake, or HTTP/API layer.
If DNS fails → focus on name resolution / outbound networking.
If DNS works but HTTPS fails → check firewall/proxy, IP allowlisting, TLS, or API endpoint itself.
For Serverless, also check:
SELECT event_time, event_id, destination, access_type, dns_event
FROM system.access.outbound_network
WHERE event_time >= current_timestamp() - INTERVAL 30 MINUTES
ORDER BY event_time DESC
If the destination shows access_type = 'DROP', that points to the serverless outbound network path.
For Classic compute, check the workspace VPC/VNet egress path instead: NAT/internet access, firewall/security-group rules, proxy settings, and whether the external API requires source-IP allowlist. Databricks docs the required subnet routing, NAT gateway, security-group, and outbound-access configuration here
If Serverless shows access_type = 'DROP', check whether your account level exposes any serverless egress/network policy controls. If no relevant setting is available and the issue is only on Serverless, then Databricks Support may need to investigate further.