<?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 Re: Unble to Upload SSL Certificate in ExtremeCloud IQ</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq/unble-to-upload-ssl-certificate/m-p/121897#M4826</link>
    <description>&lt;P&gt;&lt;SPAN&gt;I’ve actually faced something very similar while working on a hosted setup where a PEM certificate upload kept failing even though the full chain (cert + intermediate + root + key) looked correct.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In my case, the issue wasn’t the certificate itself but how the PEM was being interpreted during upload. Re-exporting the chain cleanly and making sure there were no extra spaces, hidden characters, or incorrect ordering between the certificate and private key sections fixed it. In some environments, even small formatting differences can cause the upload to fail while the same file works elsewhere (like cloud instances).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://zeepackaging.com/blog/" target="_blank"&gt;&lt;SPAN&gt;Follow Me&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 09 Jun 2026 09:07:21 GMT</pubDate>
    <dc:creator>jennymartin</dc:creator>
    <dc:date>2026-06-09T09:07:21Z</dc:date>
    <item>
      <title>Unble to Upload SSL Certificate</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/unble-to-upload-ssl-certificate/m-p/98981#M3532</link>
      <description>&lt;P&gt;I have been trying to upload a new certificate on the Extreme IQ portal version&amp;nbsp;&lt;SPAN&gt;21.1.23.4-IQVA using a PEM file with all certificate, keys, root and intermediate&amp;nbsp;certificate but it keeps on failing with error -&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The certificate file ******24-25chain.pem cannot be uploaded.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I was able to upload the same certificate on the cloud instance without any problem. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2024 12:19:34 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/unble-to-upload-ssl-certificate/m-p/98981#M3532</guid>
      <dc:creator>dgn-tr_infrastr</dc:creator>
      <dc:date>2024-01-22T12:19:34Z</dc:date>
    </item>
    <item>
      <title>Re: Unble to Upload SSL Certificate</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/unble-to-upload-ssl-certificate/m-p/121897#M4826</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I’ve actually faced something very similar while working on a hosted setup where a PEM certificate upload kept failing even though the full chain (cert + intermediate + root + key) looked correct.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In my case, the issue wasn’t the certificate itself but how the PEM was being interpreted during upload. Re-exporting the chain cleanly and making sure there were no extra spaces, hidden characters, or incorrect ordering between the certificate and private key sections fixed it. In some environments, even small formatting differences can cause the upload to fail while the same file works elsewhere (like cloud instances).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://zeepackaging.com/blog/" target="_blank"&gt;&lt;SPAN&gt;Follow Me&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jun 2026 09:07:21 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/unble-to-upload-ssl-certificate/m-p/121897#M4826</guid>
      <dc:creator>jennymartin</dc:creator>
      <dc:date>2026-06-09T09:07:21Z</dc:date>
    </item>
  </channel>
</rss>

