SPOG discovery probe failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2026 01:08 AM
Databricks adapter: SPOG discovery probe to 'https://adb-1235610976271489.3.azuredatabricks.net/.well-known/databricks-config' failed after 3 attempts (last error: HTTPSConnectionPool(host='adb-1235610976271489.3.azuredatabricks.net', port=443): Max retries exceeded with url: /.well-known/databricks-config (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1016)')))). Proceeding as a non-SPOG host. If adb-1235610976271489.3.azuredatabricks.net is a SPOG (unified) workspace, routing errors may follow; verify network reachability to /.well-known/databricks-config.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2026 05:28 AM
In simple terms, this error means:
Your computer tried to connect to your Databricks workspace, but it couldn't verify the website's security certificate.
The important part is:
certificate verify failed: self-signed certificate in certificate chainThis usually happens because:
- You're connected to a company VPN or corporate network that inspects HTTPS traffic.
- A proxy or antivirus is replacing the website's security certificate.
- Your computer is missing the required trusted certificates.
The "SPOG discovery" message isn't the actual problem—it's just telling you that Databricks couldn't check some workspace information because the secure connection failed.
What you can do
Open your Databricks workspace URL in a browser:
https://adb-1235610976271489.3.azuredatabricks.net
- If it opens normally, your workspace is likely fine.
- If you see a certificate warning, it's a network or certificate issue.
- If you're using a company VPN or proxy, try disconnecting and connecting again, or ask your IT team if they use SSL/HTTPS inspection.
- Make sure your Databricks tools (CLI, SDK, or VS Code extension) are up to date.