<?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: SSL Certificate Error vCenter 8 in vCenter™ Server Discussions</title>
    <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2994995#M95145</link>
    <description>&lt;P&gt;This thread pops up in the search results for problems with the VCSA 8 certificate errors problem, I thought I would add my experience for future reference in case it helps point others to their solution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was trying to upgrade 7.0.3.01700 (22357613) to 8.0.2 (22617221), but it was failing with weak signature algorithm errors. I know about the main support article: &lt;A href="https://kb.vmware.com/s/article/89424" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/89424&lt;/A&gt;. However, it didn't address all the issues and potential troubleshooting steps. I would suggest testing your certificates with the &lt;STRONG&gt;vsphere8_upgrade_certificate_checks.py&lt;/STRONG&gt; Python script at the bottom of that article link, since you can make changes and re-test quickly without going through the upgrade process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;2023-11-08 10:24:58.823Z ERROR #################### Errors Found ####################&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;2023-11-08 10:24:58.823Z ERROR&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;2023-11-08 10:24:58.823Z ERROR Support for certificates with weak signature algorithms has been removed in vSphere 8.0. Weak signature algorithm certificates must be replaced before upgrade. Refer to the vSphere release notes and VMware KB 89424 for more details. Correct the following 2 issues before proceeding with upgrade.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;2023-11-08 10:24:58.823Z ERROR&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;2023-11-08 10:24:58.823Z ERROR 1. The certificate with subject '/C=GB/ST=Greater Manchester/L=Salford/O=Comodo CA Limited/CN=AAA Certificate Services' in VECS store MACHINE_SSL_CERT has weak signature algorithm sha1WithRSAEncryption. The certificate thumbprint is D1:EB:23:A4:6D:17:D6:8F:D9:25:64:C2:F1:F1:60:17:64:D8:E3:49. The certificate Subject Key Identifier is A0:11:0A:23:3E:96:F1:07:EC:E2:AF:29:EF:82:A5:7F:D0:30:A4:B4.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;2023-11-08 10:24:58.823Z ERROR&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;2023-11-08 10:24:58.823Z ERROR 2. The certificate with subject '/C=GB/ST=Greater Manchester/L=Salford/O=Comodo CA Limited/CN=AAA Certificate Services' in VECS store TRUSTED_ROOTS has weak signature algorithm sha1WithRSAEncryption. The certificate thumbprint is D1:EB:23:A4:6D:17:D6:8F:D9:25:64:C2:F1:F1:60:17:64:D8:E3:49. The certificate Subject Key Identifier is A0:11:0A:23:3E:96:F1:07:EC:E2:AF:29:EF:82:A5:7F:D0:30:A4:B4. Caution: Verify that any certificates signed by the problematic certificate are not in use by vCenter Server.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;2023-11-08 10:24:58.823Z ERROR&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;2023-11-08 10:24:58.823Z ERROR ######################################################&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our leaf certificate was issued by "InCommon ECC Server CA" (&lt;A href="https://crt.sh/?id=12722102" target="_blank" rel="noopener"&gt;https://crt.sh/?id=12722102&lt;/A&gt;) which was issued by "USERTrust ECC Certification Authority" (&lt;A href="https://crt.sh/?id=1282303296" target="_blank" rel="noopener"&gt;https://crt.sh/?id=1282303296&lt;/A&gt;) which was issued by "AAA Certificate Services" (&lt;A href="https://crt.sh/?id=331986)" target="_blank" rel="noopener"&gt;https://crt.sh/?id=331986)&lt;/A&gt;. The last one is the problem, because its signature algorithm is sha1WithRSAEncryption. The "USERTrust ECC Certification Authority" is also a problem, because it's issued by the bad root.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[*] Store : TRUSTED_ROOTS&lt;BR /&gt;Alias: d1eb23a46d17d68fd92564c2f1f1601764d8e349&lt;BR /&gt;&lt;STRONG&gt;Signature Algorithm: sha1WithRSAEncryption&lt;/STRONG&gt;&lt;BR /&gt;Issuer: C=GB, ST=Greater Manchester, L=Salford, O=Comodo CA Limited, CN=AAA Certificate Services&lt;BR /&gt;Subject: C=GB, ST=Greater Manchester, L=Salford, O=Comodo CA Limited, CN=AAA Certificate Services&lt;BR /&gt;Subject Key Identifier: A0:11:0A:23:3E:96:F1:07:EC:E2:AF:29:EF:82:A5:7F:D0:30:A4:B4&lt;/P&gt;&lt;P&gt;[*] Store : TRUSTED_ROOTS&lt;BR /&gt;Alias: ca7788c32da1e4b7863a4fb57d00b55ddacbc7f9&lt;BR /&gt;Signature Algorithm: sha384WithRSAEncryption&lt;BR /&gt;Issuer: C=GB, ST=Greater Manchester, L=Salford, O=Comodo CA Limited, CN=AAA Certificate Services&lt;BR /&gt;Subject: C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USER Trust ECC Certification Authority&lt;BR /&gt;Subject Key Identifier: 3A:E1:09:86:D4:CF:19:C2:96:76:74:49:76:DC:E0:35:C6:63:63:9A&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on &lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1334297"&gt;@BrianCunnie&lt;/a&gt;'s reply and website, I knew I needed to &lt;STRONG&gt;remove&lt;/STRONG&gt; not only the root certificate, but also &lt;STRONG&gt;remove &amp;amp; replace&lt;/STRONG&gt; the "USERTrust ECC Certification Authority" at the next level down with its &lt;EM&gt;newer&lt;/EM&gt; self-signed version (&lt;A href="https://crt.sh/?id=2841410" target="_blank" rel="noopener"&gt;https://crt.sh/?id=2841410&lt;/A&gt;) that expires in 2038.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At that point, I used the common commands to list, unpublish, and publish.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;/usr/lib/vmware-vmafd/bin/dir-cli trustedcert list

/usr/lib/vmware-vmafd/bin/vecs-cli entry list --store TRUSTED_ROOTS --text

# This is the AAA Certificate Services root
/usr/lib/vmware-vmafd/bin/dir-cli trustedcert get --id A0110A233E96F107ECE2AF29EF82A57FD030A4B4 --outcert /certs/A0110A233E96F107ECE2AF29EF82A57FD030A4B4.pem

/usr/lib/vmware-vmafd/bin/dir-cli trustedcert unpublish --cert /certs/A0110A233E96F107ECE2AF29EF82A57FD030A4B4.pem

# This is the USERTrust ECC Certification Authority issued by AAA Certificate Services
/usr/lib/vmware-vmafd/bin/dir-cli trustedcert get --id 3AE10986D4CF19C29676744976DCE035C663639A --outcert /certs/3AE10986D4CF19C29676744976DCE035C663639A.pem

/usr/lib/vmware-vmafd/bin/dir-cli trustedcert unpublish --cert /certs/3AE10986D4CF19C29676744976DCE035C663639A.pem&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I then uploaded the new self-signed "USERTrust ECC Certification Authority" (&lt;A href="https://crt.sh/?id=2841410" target="_blank" rel="noopener"&gt;https://crt.sh/?id=2841410&lt;/A&gt;) through the vSphere Certificate Manager GUI. I had to do that after the above, because it has the same Subject Key Identifier as the other version, otherwise &lt;STRONG&gt;vSphere would complain that it was already in the store&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At this point, I was still having problems. The VCSA 8 certificate check was &lt;EM&gt;still&lt;/EM&gt; failing. Hmmmm??? I started looking and remembered about &lt;STRONG&gt;/etc/vmware-rhttpproxy/ssl/rui.crt&lt;/STRONG&gt; and &lt;STRONG&gt;/etc/vmware-vpx/ssl/rui.crt&lt;/STRONG&gt;. These files had the old intermediate+root chain in them, so I removed that (i.e., the "-----BEGIN CERTIFICATE-----" sections) and added the new certificate information to them and restarted the services. I went back to the GUI and got an error: &lt;FONT color="#FF0000"&gt;"Error occurred while fetching machine certificates: com.vmware.vcenter.certificate_management.vcenter.tls"&lt;/FONT&gt;. This was solved with a full VCSA reboot. For some reason stopping and starting the services wouldn't fix it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After the reboot, everything looks great. The correct root is there and no errors in VCSA. BUT!!! The VCSA 8 certificate check still fails with: &lt;FONT color="#FF0000"&gt;"The certificate with subject '/C=GB/ST=Greater Manchester/L=Salford/O=Comodo CA Limited/CN=AAA Certificate Services' in VECS store MACHINE_SSL_CERT has weak signature algorithm sha1WithRSAEncryption."&lt;/FONT&gt; WHY???!!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I figured that somewhere the old root information was still in VCSA, but I've replaced everything. Not so fast. Whenever you upload a new leaf certificate, VMware tells us to append the full chain to the end of that certificate. So when it's saying the problem is in MACHINE_SSL_CERT, it's talking about this. But this isn't mention anywhere in the notes and you can't easily troubleshoot it, at least I couldn't. I thought the easiest would be to create a new file that contained the old/current leaf, but with the new root chain appended. But VCSA won't let you do that, because: &lt;FONT color="#FF0000"&gt;“MACHINE_SSL_CERT certificate replacement failed. SerialNumber and Thumbprint not changed after replacement, certificates are same before and after.”&lt;/FONT&gt; I understand the error, because the leaf is not changing. But the chain &lt;EM&gt;is&lt;/EM&gt; changing. I kind of feel like I should be able to perform this action.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While reviewing &lt;A href="https://kb.vmware.com/s/article/83276" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/83276&lt;/A&gt;, it showed the procedure for extracting the current certificate and private key from the MACHINE_SSL_CERT. When I did that, I confirmed that the &lt;STRONG&gt;“__MACHINE_CERT”&lt;/STRONG&gt; alias contained the WHOLE certificate chain (leaf, intermediates, root). So I created a new file that contained the old leaf, intermediate, and NEW root chain. I deleted and recreated &lt;STRONG&gt;“__MACHINE_CERT”&lt;/STRONG&gt; and restarted VCSA services. That finally fixed it! The upgrade certificate check script succeeds.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;/usr/lib/vmware-vmafd/bin/vecs-cli entry getcert --store MACHINE_SSL_CERT --alias __MACHINE_CERT --output ~/entry__MACHINE_CERT-getcert.txt

/usr/lib/vmware-vmafd/bin/vecs-cli entry getkey --store MACHINE_SSL_CERT --alias __MACHINE_CERT --output ~/entry__MACHINE_CERT-getkey.txt

openssl pkey -in entry__MACHINE_CERT-getkey.txt -pubout -outform pem | sha256sum

openssl x509 -in leaf_MACHINE_CERT.pem -pubkey -noout -outform pem | sha256sum&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I manually created my own &lt;STRONG&gt;leaf_chain_MACHINE_CERT.pem&lt;/STRONG&gt; with the right certificates.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;/usr/lib/vmware-vmafd/bin/vecs-cli entry delete --store MACHINE_SSL_CERT --alias __MACHINE_CERT

/usr/lib/vmware-vmafd/bin/vecs-cli entry create --store MACHINE_SSL_CERT --alias __MACINE_CERT --cert leaf_chain_MACHINE_CERT.pem --key entry__MACHINE_CERT-getkey.txt&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No more errors with the certificate checks.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Nov 2023 20:09:51 GMT</pubDate>
    <dc:creator>rwattuab</dc:creator>
    <dc:date>2023-11-10T20:09:51Z</dc:date>
    <item>
      <title>SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2933907#M93723</link>
      <description>&lt;P&gt;Hi Everyone, the surprisingly new version of vCenter does not work with my current SSL from vCenter 7&lt;/P&gt;&lt;P&gt;here are the errors:&lt;/P&gt;&lt;P&gt;1. When trying to insert Sectigo 1yr (&lt;SPAN class=""&gt;Error occurred while fetching tls: Provided certificate using the weak signature algorithm. Please provide the strong signature algorithm certificate&lt;/SPAN&gt;)&lt;/P&gt;&lt;P&gt;2. When trying to insert Let's Encrypt (&lt;SPAN class=""&gt;Error occurred while fetching tls: the trustAnchors parameter must be non-empty)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;3. When trying to SSL.com 90-days (Error occurred while fetching tls: 0)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;4. When trying to insert wildcard not work as well (Wildcard SSL working well with ESXi but not working with Center)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;================&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;I tried to re-issue, I changed the SSL provider, I read every article, and none of them is working&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;since I was at vCenter 7 all of them except Let's Encrypt working fine&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;but now none of them working&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;please give me a solution, appreciate it&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Best Regards&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 16 Oct 2022 22:27:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2933907#M93723</guid>
      <dc:creator>AHMNco</dc:creator>
      <dc:date>2022-10-16T22:27:18Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2934214#M93724</link>
      <description>&lt;P&gt;Confirmed. vCenter 8.0, I'm seeing same error:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Error occurred while fetching tls:0 &lt;/LI-CODE&gt;&lt;P&gt;when trying to replace machine certificate with certificate genrated using a CSR generated by vCenter itself.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2022 14:42:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2934214#M93724</guid>
      <dc:creator>chall32</dc:creator>
      <dc:date>2022-10-18T14:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2934941#M93725</link>
      <description>&lt;P&gt;After thousand years nobody even replied, where are the VMware Experts????&lt;/P&gt;</description>
      <pubDate>Sun, 23 Oct 2022 23:59:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2934941#M93725</guid>
      <dc:creator>AHMNco</dc:creator>
      <dc:date>2022-10-23T23:59:09Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935184#M93726</link>
      <description>&lt;P&gt;I will not be so original and will say to generate a new certificate and to check a certificate template for vCenter7&lt;/P&gt;&lt;P&gt;Highly possible that maybe changes are needed&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 13:37:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935184#M93726</guid>
      <dc:creator>maksym007</dc:creator>
      <dc:date>2022-10-25T13:37:36Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935188#M93727</link>
      <description>&lt;P&gt;The problem is not with the certificate, it is with the application of the newly generated certificate into vCenter 8.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 13:46:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935188#M93727</guid>
      <dc:creator>chall32</dc:creator>
      <dc:date>2022-10-25T13:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935284#M93728</link>
      <description>&lt;P&gt;so where is the resolution?&lt;/P&gt;&lt;P&gt;where are the VMWare experts??&lt;/P&gt;&lt;P&gt;is nobody gonna come and answer this problem?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 01:03:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935284#M93728</guid>
      <dc:creator>AHMNco</dc:creator>
      <dc:date>2022-10-26T01:03:06Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935322#M93729</link>
      <description>&lt;P&gt;same problem!&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 07:47:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935322#M93729</guid>
      <dc:creator>lasersword</dc:creator>
      <dc:date>2022-10-26T07:47:48Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935335#M93730</link>
      <description>&lt;P&gt;Same problem and Auto Gen Certificate is Sha256 with rsa:3084&amp;nbsp; and my certs with Sectigo Sha384 with rsa:8192&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 08:25:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935335#M93730</guid>
      <dc:creator>Tokiha</dc:creator>
      <dc:date>2022-10-26T08:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935385#M93731</link>
      <description>&lt;P&gt;Same problem; tried "ecdsa-with-SHA256 + id-ecPublicKey (384 bit)" and "sha384WithRSAEncryption +&amp;nbsp;rsaEncryption (2048 bit)", both without luck.&lt;/P&gt;&lt;P&gt;Default certificate is:&amp;nbsp;"sha256WithRSAEncryption +&amp;nbsp;rsaEncryption (2048 bit)"...&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 13:20:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935385#M93731</guid>
      <dc:creator>tim427</dc:creator>
      <dc:date>2022-10-26T13:20:32Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935951#M93732</link>
      <description>&lt;P&gt;It seems none of the VMWare Experts care about our problem!!!!!&lt;/P&gt;</description>
      <pubDate>Sun, 30 Oct 2022 01:26:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2935951#M93732</guid>
      <dc:creator>AHMNco</dc:creator>
      <dc:date>2022-10-30T01:26:30Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936074#M93733</link>
      <description>&lt;P&gt;This is what I had to do to fix it for my Sectigo/Comodo certificate:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;edit the .ca-bundle&lt;/LI&gt;&lt;LI&gt;replace the bad PEM with the good PEM (see attached files)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Longer story: the bad &amp;amp; good certificates have the same key (their RSA Modulus is the same) and the same CN ("USERTrust RSA Certification Authority"), so they can be interchanged, but the bad PEM has been cross-signed (issued) by the old, bad "AAA Certificate Services" (which is self-signed with the weak SHA1 algorithm). The good cert is self-signed with the strong SHA-384 algorithm.&lt;BR /&gt;&lt;BR /&gt;If you feel uncomfortable downloading the cert from a forum (and you should feel uncomfortable), you can view the details of the good certificate here: &lt;A href="https://crt.sh/?id=1199354" target="_blank" rel="noopener"&gt;https://crt.sh/?id=1199354&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;And you can download a copy of the PEM here: &lt;A href="https://crt.sh/?d=1199354" target="_blank" rel="noopener"&gt;https://crt.sh/?d=1199354&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Nov 2022 15:32:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936074#M93733</guid>
      <dc:creator>BrianCunnie</dc:creator>
      <dc:date>2022-11-04T15:32:35Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936101#M93734</link>
      <description>&lt;P&gt;No, not working&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2022 16:31:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936101#M93734</guid>
      <dc:creator>AHMNco</dc:creator>
      <dc:date>2022-10-31T16:31:31Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936108#M93735</link>
      <description>&lt;P&gt;I had similar issues and in my case it was due to the path to root certificated being incomplete. Also make sure that any cert in path is at least above sha 1 as version 8 rejects any sha 1 cert. Another approach i took was to delete all related trusted root certs to make sure there is no conflict's. That has t be done from CLI and a slight pain in ass.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2022 17:17:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936108#M93735</guid>
      <dc:creator>ASMITH_77</dc:creator>
      <dc:date>2022-10-31T17:17:50Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936627#M93747</link>
      <description>&lt;P&gt;Hey &lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5050467"&gt;@AHMNco&lt;/a&gt; :&lt;BR /&gt;&lt;BR /&gt;FYI, I wrote a blog post describing how I was able to get past this error (use a different cert in the CA Bundle). You may want to skip to the &lt;A href="https://blog.nono.io/post/vcenter_8.0_tls/#troubleshooting" target="_self"&gt;Troubleshooting&lt;/A&gt; section.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 14:04:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936627#M93747</guid>
      <dc:creator>BrianCunnie</dc:creator>
      <dc:date>2022-11-03T14:04:17Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936657#M93749</link>
      <description>&lt;P&gt;OK good to see some have got it working using public certs.&amp;nbsp; I'm still struggling to replace the machine cert with a cert generated by an internal CA.&lt;/P&gt;&lt;P&gt;acursory look through the logs in /var/log/vmware/certificatemanagement and /var/log/vmware/certificateauthority isn't providing much help either!&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 16:06:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936657#M93749</guid>
      <dc:creator>chall32</dc:creator>
      <dc:date>2022-11-03T16:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936663#M93750</link>
      <description>&lt;P&gt;Found the error in /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[2022-11-03T15:31:03.619Z] [ERROR] http-nio-5090-exec-4          com.vmware.vise.mvc.exception.GlobalExceptionHandler              Exception handled while processing request for /ui/certificate-ui/ctrl/certificates/tls:  com.vmware.vapi.std.errors.Error: Error (com.vmware.vapi.std.errors.error) =&amp;gt; {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) =&amp;gt; {
    id = com.vmware.certificatemanagement.error,
    defaultMessage = Exception found (0),
    args = [0],
    params = &amp;lt;null&amp;gt;,
    localized = &amp;lt;null&amp;gt;
}],
    data = &amp;lt;null&amp;gt;,
    errorType = ERROR
}&lt;/LI-CODE&gt;&lt;P&gt;Full error attached.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Nov 2022 16:22:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2936663#M93750</guid>
      <dc:creator>chall32</dc:creator>
      <dc:date>2022-11-03T16:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2937165#M93753</link>
      <description>&lt;P&gt;Problem also exists when configuring vCenter login with OpenID Connect in Azure. To access login.microsoft.com, both CA certs from Digicert are needed, but "&lt;SPAN class=""&gt;DigiCert Global Root CA" use "SHA-1 with RSA Encryption" signature algorithm. Importing fails, means also configuring OIDC fails.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;It's not that VMware supports 100s of different IDPs. The only one is ADFS and using Microsofts cloud service isn't uncommon.&lt;/P&gt;&lt;P&gt;When checking login.microsoft.com with ssllabs.com, they wrote about the Root CA from Digicert:&amp;nbsp;&lt;SPAN&gt;Weak or insecure signature, but no impact on root certificate&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;VMware, please fix it. Thanks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Nov 2022 17:17:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2937165#M93753</guid>
      <dc:creator>BAUERAG</dc:creator>
      <dc:date>2022-11-07T17:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2937326#M93757</link>
      <description>&lt;P&gt;Same issue here. Reverting back to vCenter 7....&lt;/P&gt;</description>
      <pubDate>Tue, 08 Nov 2022 17:24:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2937326#M93757</guid>
      <dc:creator>donaldsteele</dc:creator>
      <dc:date>2022-11-08T17:24:08Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2937506#M93760</link>
      <description>&lt;P&gt;vSphere 8.0 (&lt;SPAN&gt;vCenter Server and ESXi )&lt;/SPAN&gt;&amp;nbsp; do not support certificate&amp;nbsp;&lt;SPAN&gt;with weak signature algorithms, such as sha1WithRSAEncryption.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Just check if the certificate you are using is&amp;nbsp;with weak signature algorithms. Check the below KB for more details.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/89424" target="_blank"&gt;https://kb.vmware.com/s/article/89424&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Nov 2022 16:43:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2937506#M93760</guid>
      <dc:creator>Anil0210</dc:creator>
      <dc:date>2022-11-09T16:43:52Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Certificate Error vCenter 8</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2946854#M93966</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1334297"&gt;@BrianCunnie&lt;/a&gt;&amp;nbsp; I followed your instructions from your blog post, even purchasing the exact certificate you purchased and attempted this with vCenter 8.&lt;/P&gt;&lt;P&gt;First, I created via&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;CN=vcenter-80.nono.io # "CN" is the abbreviation for "Common Name"
openssl genrsa -out $CN.key 3072
openssl req \
  -new \
  -key $CN.key \
  -out $CN.csr \
  -sha256 \
  -subj "/C=US/ST=California/L=San Francisco/O=nono.io/OU=homelab/CN=${CN}/emailAddress=brian.cunnie@gmail.com" \
  -config &amp;lt;(cat &amp;lt;&amp;lt;EOF
[ req ]
distinguished_name = req_distinguished_name
req_extensions     = req_ext
[ req_distinguished_name ]
[ req_ext ]
subjectAltName = @alt_names
[alt_names]
DNS.1   = ${CN}
EOF
)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(obviously, I changed the values).&lt;/P&gt;&lt;P&gt;I then requested a certificate from&amp;nbsp;&amp;nbsp;&lt;A href="https://ssls.com/" target="_blank" rel="noopener"&gt;SSls.com&lt;/A&gt;, and we purchased their least-expensive offering, the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;PositiveSSL 1 domain Comodo SSL&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;(using the same disclaimer):&lt;/P&gt;&lt;P&gt;&lt;EM&gt;[We do not endorse either SSLs.com or Sectigo (formerly Comodo); We encourage you to use the reseller and the Certificate Authority (CA) with which you are most comfortable]&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;They then provided me with the two files.&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;vcenter.domain.co.crt&lt;SPAN&gt;&amp;nbsp;and&amp;nbsp;&lt;/SPAN&gt;vcenter_domain_co.ca-bundle&lt;/P&gt;&lt;P&gt;Then we followed the instructions from your blog post:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;BLOCKQUOTE&gt;&lt;UL&gt;&lt;LI&gt;On your vCenter, navigate to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Menu → Administration → Certificates → Certificate Management&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;On the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;__MACHINE_CERT&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;tile, click&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Actions&lt;/STRONG&gt;, select&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Import and Replace Certificate&lt;/STRONG&gt;.&lt;/LI&gt;&lt;LI&gt;Select&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Replace with external CA certificate(requires private key)&lt;/STRONG&gt;.&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Machine SSL Certificate&lt;/STRONG&gt;: click&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Browse File&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and select&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;vcenter.domain.crt&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Chain of trusted root certificates&lt;/STRONG&gt;: click&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Browse File&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and select&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;vcenter_domain_co.ca-bundle&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Private Key&lt;/STRONG&gt;: click&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Browse File&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and select&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;vcenter_domain_co.ca-bundle&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Click&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Replace&lt;/STRONG&gt;.&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;After doing this, vCenter reports: "&lt;SPAN&gt;Error occurred while fetching tls: Invalid input, not a valid PEM formatted Primary Key"&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;I've been beating my head all day with this.&amp;nbsp; vCenter logs aren't much of a help.&amp;nbsp; Did you have to do anything else, or am I just missing a step?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jan 2023 00:37:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/SSL-Certificate-Error-vCenter-8/m-p/2946854#M93966</guid>
      <dc:creator>obsidianindy</dc:creator>
      <dc:date>2023-01-05T00:37:26Z</dc:date>
    </item>
  </channel>
</rss>

