<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SPOG discovery probe failed in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/spog-discovery-probe-failed/m-p/162764#M5418</link>
    <description>&lt;P&gt;Databricks adapter: SPOG discovery probe to '&lt;A href="https://adb-1235610976271489.3.azuredatabricks.net/.well-known/databricks-config" target="_blank"&gt;https://adb-1235610976271489.3.azuredatabricks.net/.well-known/databricks-config&lt;/A&gt;' 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.&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jul 2026 08:08:49 GMT</pubDate>
    <dc:creator>Th0rs7en</dc:creator>
    <dc:date>2026-07-13T08:08:49Z</dc:date>
    <item>
      <title>SPOG discovery probe failed</title>
      <link>https://community.databricks.com/t5/administration-architecture/spog-discovery-probe-failed/m-p/162764#M5418</link>
      <description>&lt;P&gt;Databricks adapter: SPOG discovery probe to '&lt;A href="https://adb-1235610976271489.3.azuredatabricks.net/.well-known/databricks-config" target="_blank"&gt;https://adb-1235610976271489.3.azuredatabricks.net/.well-known/databricks-config&lt;/A&gt;' 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.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2026 08:08:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/spog-discovery-probe-failed/m-p/162764#M5418</guid>
      <dc:creator>Th0rs7en</dc:creator>
      <dc:date>2026-07-13T08:08:49Z</dc:date>
    </item>
    <item>
      <title>Re: SPOG discovery probe failed</title>
      <link>https://community.databricks.com/t5/administration-architecture/spog-discovery-probe-failed/m-p/162793#M5420</link>
      <description>&lt;P class=""&gt;In simple terms, this error means:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;STRONG&gt;Your computer tried to connect to your Databricks workspace, but it couldn't verify the website's security certificate.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The important part is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;PRE&gt;&lt;SPAN&gt;certificate verify failed:
self-signed certificate in certificate chain&lt;/SPAN&gt;&lt;/PRE&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;PRE&gt;&amp;nbsp;This usually happens because:&lt;/PRE&gt;&lt;UL&gt;&lt;LI&gt;You're connected to a company VPN or corporate network that inspects HTTPS traffic.&lt;/LI&gt;&lt;LI&gt;A proxy or antivirus is replacing the website's security certificate.&lt;/LI&gt;&lt;LI&gt;Your computer is missing the required trusted certificates.&lt;P&gt;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.&lt;/P&gt;&lt;H3&gt;What you can do&lt;/H3&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Open your Databricks workspace URL in a browser:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;PRE&gt;&lt;SPAN&gt;https://adb-1235610976271489.3.azuredatabricks.net&lt;/SPAN&gt;&lt;/PRE&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;UL&gt;&lt;LI&gt;If it opens normally, your workspace is likely fine.&lt;/LI&gt;&lt;LI&gt;If you see a certificate warning, it's a network or certificate issue.&lt;/LI&gt;&lt;LI&gt;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.&lt;/LI&gt;&lt;LI&gt;Make sure your Databricks tools (CLI, SDK, or VS Code extension) are up to date.&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Mon, 13 Jul 2026 12:28:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/spog-discovery-probe-failed/m-p/162793#M5420</guid>
      <dc:creator>Miss_Maee</dc:creator>
      <dc:date>2026-07-13T12:28:41Z</dc:date>
    </item>
  </channel>
</rss>

