<?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: AppVol 2.12.1 - Certificate has not been verified in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800332#M6009</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Had same issue.. this is even more fun when running multiple vCenters under the same SSO...&lt;BR /&gt;Then you get the intermediate cert presented instead of the vCenter certs. Causing duplicate cert entry in the database.&lt;BR /&gt;This even causes that only one vCenter will work and the others will fail to even mount App Stacks.&lt;BR /&gt;Thankfully this quick bypass solves it and will be patched in 2.13&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 Jun 2017 13:20:05 GMT</pubDate>
    <dc:creator>LVANDUIJN</dc:creator>
    <dc:date>2017-06-01T13:20:05Z</dc:date>
    <item>
      <title>AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800325#M6002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can anyone of you confirm that the vcenter certificate verfication in appvol manager get lost again after few days?&lt;/P&gt;&lt;P&gt;We have the vmware self-signed certificate on our vcenter server. We also accept this certificate in appvolumes 2.12.1 with click on accept (machine managers).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that I can see the message: "Certificate: Using administrator trusted certificate"&lt;/P&gt;&lt;P&gt;If I check this setting after few days its again lost and I have to accept the certificate again. It's doesn't impact the appvol functionality, but I will create a lot of log entries..... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Validating SSL certificate for "VCA.domain.local": Rejected because certificate is neither verified nor trusted&lt;/P&gt;&lt;P&gt;Failed to connect to vSphere at "domain\srvappvol@VCA.domain.local": SSL_connect returned=1 errno=0 state=error: certificate verify failed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;VM-Master&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 May 2017 12:51:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800325#M6002</guid>
      <dc:creator>Erossman</dc:creator>
      <dc:date>2017-05-29T12:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800326#M6003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes we have the exact same issue, it's a known issue for as far as I'm aware. Just make sure to raise a ticket with VMware, they are aware.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 May 2017 13:59:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800326#M6003</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2017-05-29T13:59:55Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800327#M6004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I reconized that this happens after rebooting the vcenter server.&lt;/P&gt;&lt;P&gt;Why are these "known issues" are not public documented?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 May 2017 15:31:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800327#M6004</guid>
      <dc:creator>Erossman</dc:creator>
      <dc:date>2017-05-29T15:31:02Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800328#M6005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Indeed restarting the Vcenter triggers it. Strange thing is that we, at first sight, could not reproduce it on our acceptance environment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2017 07:32:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800328#M6005</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2017-05-30T07:32:24Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800329#M6006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The current workaround for this is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps:&lt;/P&gt;&lt;P&gt;1:- set env variable AVM_DISABLE_VCENTER_SSL_VALIDATION with value 1 on Management servers&lt;BR /&gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;SPAN style="font-size: 12.0pt; font-family: 'Times New Roman',serif;"&gt;2:- restart the manager service.&lt;BR /&gt; &lt;BR /&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2017 12:58:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800329#M6006</guid>
      <dc:creator>techguy129</dc:creator>
      <dc:date>2017-05-30T12:58:51Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800330#M6007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi techguy129,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can you please describe how to set this value on the appvolumes managers?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I open a command prompt and typed in....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;"set env variable AVM_DISABLE_VCENTER_SSL_VALIDATION=1"&lt;/SPAN&gt;&lt;SPAN class="j-post-author" style="font-size: 0.9em; font-family: proxima-nova, Arial, sans-serif; color: #666666;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;Is there an option to check this setting?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2017 15:55:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800330#M6007</guid>
      <dc:creator>Erossman</dc:creator>
      <dc:date>2017-05-30T15:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800331#M6008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;OL style="margin-right: 1.5em; margin-bottom: 1.5em; margin-left: 1.5em; font-size: 12px; color: #333333;"&gt;&lt;LI style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;Open &lt;STRONG&gt;Control Panel&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;Select &lt;STRONG&gt;System&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;Click the &lt;STRONG&gt;Advanced system settings&lt;/STRONG&gt; link.&lt;/LI&gt;&lt;LI style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;Click &lt;STRONG&gt;Environment Variables&lt;/STRONG&gt;. In the section &lt;STRONG&gt;System Variables&lt;/STRONG&gt;, Click &lt;CODE style="margin: 1.5em 0; font-family: 'andale mono', 'lucida console', monospace;"&gt;New&lt;/CODE&gt;.&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;In the &lt;/SPAN&gt;&lt;STRONG style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;New System Variable &lt;/STRONG&gt;&lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;window, specify the value of&amp;nbsp; &lt;EM&gt;V&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;EM&gt;ariable Name&lt;/EM&gt; as &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;AVM_DISABLE_VCENTER_SSL_VALIDATION and s&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;pecify the &lt;EM&gt;Variable Value&lt;/EM&gt; as 1&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;Click &lt;/SPAN&gt;&lt;STRONG style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;OK&lt;/STRONG&gt;&lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;. Close all remaining windows by clicking &lt;/SPAN&gt;&lt;STRONG style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;OK&lt;/STRONG&gt;&lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2017 17:30:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800331#M6008</guid>
      <dc:creator>techguy129</dc:creator>
      <dc:date>2017-05-30T17:30:54Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800332#M6009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Had same issue.. this is even more fun when running multiple vCenters under the same SSO...&lt;BR /&gt;Then you get the intermediate cert presented instead of the vCenter certs. Causing duplicate cert entry in the database.&lt;BR /&gt;This even causes that only one vCenter will work and the others will fail to even mount App Stacks.&lt;BR /&gt;Thankfully this quick bypass solves it and will be patched in 2.13&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Jun 2017 13:20:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800332#M6009</guid>
      <dc:creator>LVANDUIJN</dc:creator>
      <dc:date>2017-06-01T13:20:05Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800333#M6010</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks a lot techguy129! This seems to solve the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jun 2017 07:00:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800333#M6010</guid>
      <dc:creator>Erossman</dc:creator>
      <dc:date>2017-06-02T07:00:05Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800334#M6011</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just heard from VMware that this is indeed a know bug.&lt;/P&gt;&lt;P&gt;A hot patch is available, but needs to be requested separately from VMware Global Support.&lt;/P&gt;&lt;P&gt;The issue will be resolved in a future version of App Volumes&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Jul 2017 09:03:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800334#M6011</guid>
      <dc:creator>Lieven</dc:creator>
      <dc:date>2017-07-26T09:03:33Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800335#M6012</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If it is the 2.12.3.11 hotfix no need to ask for it. We tested it on our managers but still see this specific error message popping up.&lt;/P&gt;&lt;P&gt;We are now running 2.12.3.11 agent (which works quite well just not with all 2.9 appstacks) and 2.12.1.103 manager. For me it seems to be the most stable and quickest combination until now. And believe me I have seen a few &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt; &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Jul 2017 13:26:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800335#M6012</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2017-07-26T13:26:22Z</dc:date>
    </item>
    <item>
      <title>Re: AppVol 2.12.1 - Certificate has not been verified</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800336#M6013</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This issue has been addressed and deploying the most recent version of App Volumes would provide a more secure option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jeff Ulatoski&lt;/P&gt;&lt;P&gt;Senior Product Manager, App Volumes&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Feb 2018 17:24:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVol-2-12-1-Certificate-has-not-been-verified/m-p/1800336#M6013</guid>
      <dc:creator>julatoski</dc:creator>
      <dc:date>2018-02-23T17:24:14Z</dc:date>
    </item>
  </channel>
</rss>

