<?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 Switch From  Self-Signed Certificate to CA Signed on Globaprotect Fails in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/switch-from-self-signed-certificate-to-ca-signed-on-globaprotect/m-p/456992#M2260</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Our users were running for some time using a self-sgined certificate with few errors and issues.&lt;/P&gt;&lt;P&gt;I was trying to install a wildcard certificate to replace the one in use, but no matter what I do, I ended up with the error message "The network connection is unreachable or the portal is unresponsive. Check the network connection and reconnect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The same certificate with similar configuration is working just fine on other firewalls. However, other firewalls didn't had a previous configuration with self-signed certificate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No need to say, there is nothing in the Monitor\globalprotect , not even a prelogin entry. It's just like the agent itself didn't like the new certificate on the firewall. Even worse, GP log shows nothing useful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried the connection from three different machines running Windows and mac with the same exact result.&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jan 2022 15:28:46 GMT</pubDate>
    <dc:creator>kinanakelstcs</dc:creator>
    <dc:date>2022-01-05T15:28:46Z</dc:date>
    <item>
      <title>Switch From  Self-Signed Certificate to CA Signed on Globaprotect Fails</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/switch-from-self-signed-certificate-to-ca-signed-on-globaprotect/m-p/456992#M2260</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Our users were running for some time using a self-sgined certificate with few errors and issues.&lt;/P&gt;&lt;P&gt;I was trying to install a wildcard certificate to replace the one in use, but no matter what I do, I ended up with the error message "The network connection is unreachable or the portal is unresponsive. Check the network connection and reconnect.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The same certificate with similar configuration is working just fine on other firewalls. However, other firewalls didn't had a previous configuration with self-signed certificate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No need to say, there is nothing in the Monitor\globalprotect , not even a prelogin entry. It's just like the agent itself didn't like the new certificate on the firewall. Even worse, GP log shows nothing useful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried the connection from three different machines running Windows and mac with the same exact result.&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jan 2022 15:28:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/switch-from-self-signed-certificate-to-ca-signed-on-globaprotect/m-p/456992#M2260</guid>
      <dc:creator>kinanakelstcs</dc:creator>
      <dc:date>2022-01-05T15:28:46Z</dc:date>
    </item>
    <item>
      <title>Re: Switch From  Self-Signed Certificate to CA Signed on Globaprotect Fails</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/switch-from-self-signed-certificate-to-ca-signed-on-globaprotect/m-p/458304#M2294</link>
      <description>&lt;P&gt;Check the PanGPS/PanGPA logs on the agent:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClaLCAS" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClaLCAS&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/globalprotect/9-1/globalprotect-admin/get-started/enable-ssl-between-globalprotect-components/globalprotect-certificate-best-practices.html" target="_blank"&gt;GlobalProtect Certificate Best Practices (paloaltonetworks.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClFoCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClFoCAK&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jan 2022 12:47:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/switch-from-self-signed-certificate-to-ca-signed-on-globaprotect/m-p/458304#M2294</guid>
      <dc:creator>nikoolayy1</dc:creator>
      <dc:date>2022-01-12T12:47:01Z</dc:date>
    </item>
  </channel>
</rss>

