<?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 Prisma Acess Agent EPM issue in Prisma Access Agent Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-agent-discussions/prisma-acess-agent-epm-issue/m-p/1267807#M8</link>
    <description>&lt;P&gt;I have a PAA agent installed onto a Windows machine and when the vpn tunnel is down the EPM status is up and working but as soon as we bring the vpn tunnel up the EPM status goes down indicating a SSL handshake failed, now ive eliminated DNS issue with/without tunnel, all good, ive disabled dencryption of any *.gpcoudservice.com traffic within prisma, and also done testing with the forwarding profile to ensure&amp;nbsp;&amp;nbsp;*.gpcoudservice.com also goes direct and not down VPN tunnel from agent. One thing to note according to the documentation, and on other customers deployments the PAA domain should be &amp;lt;company-name&amp;gt;.epm.gpcloudservice.com, now for my tenant the domain suffix is .lab.gpcloudservice and not .epm, this is a demo tenant so not sure if this is correct.&amp;nbsp; Has anybody seen this before&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2026 15:49:52 GMT</pubDate>
    <dc:creator>GabrielBryson</dc:creator>
    <dc:date>2026-11-05T15:49:52Z</dc:date>
    <item>
      <title>Prisma Acess Agent EPM issue</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-agent-discussions/prisma-acess-agent-epm-issue/m-p/1267807#M8</link>
      <description>&lt;P&gt;I have a PAA agent installed onto a Windows machine and when the vpn tunnel is down the EPM status is up and working but as soon as we bring the vpn tunnel up the EPM status goes down indicating a SSL handshake failed, now ive eliminated DNS issue with/without tunnel, all good, ive disabled dencryption of any *.gpcoudservice.com traffic within prisma, and also done testing with the forwarding profile to ensure&amp;nbsp;&amp;nbsp;*.gpcoudservice.com also goes direct and not down VPN tunnel from agent. One thing to note according to the documentation, and on other customers deployments the PAA domain should be &amp;lt;company-name&amp;gt;.epm.gpcloudservice.com, now for my tenant the domain suffix is .lab.gpcloudservice and not .epm, this is a demo tenant so not sure if this is correct.&amp;nbsp; Has anybody seen this before&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2026 15:49:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-agent-discussions/prisma-acess-agent-epm-issue/m-p/1267807#M8</guid>
      <dc:creator>GabrielBryson</dc:creator>
      <dc:date>2026-11-05T15:49:52Z</dc:date>
    </item>
  </channel>
</rss>

