<?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: HTML5 based connection via load balancer in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423286#M7875</link>
    <description>&lt;P&gt;Hi @Mohd Arsh​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This error means the HTML5 GW &amp;nbsp;failed to establish the RDP connection to the target machine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please verify that OCI LB listener for the HTML5 traffic is configured for&amp;nbsp;HTTPS on port 443 and not just a plain TCP listener.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also enable&amp;nbsp;Session Persistence&amp;nbsp;/ Sticky Sessions  on LB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please verify that the PSM is not sending traffic back to the LB VIP. Check the routing as well &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the LB is set to terminate SSL traffic then LB's trust store must have Root and Intermediate CAs&amp;nbsp;that issued the PSM certificates.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ensure PSM certs are imported into HTML5 GW server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps!&lt;/P&gt;</description>
    <pubDate>Wed, 15 Oct 2025 10:43:57 GMT</pubDate>
    <dc:creator>M.Vora780263</dc:creator>
    <dc:date>2025-10-15T10:43:57Z</dc:date>
    <item>
      <title>HTML5 based connection via load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423285#M7874</link>
      <description>&lt;P&gt;We are using an OCI Load Balancer in front of our PSM Connectors.&lt;/P&gt;&lt;P&gt; When we connect using the &lt;B&gt;CyberArk thick client (RDP)&lt;/B&gt; through the LB, everything works fine and the real target is reached.&lt;/P&gt;&lt;P&gt;However, when we try to launch &lt;B&gt;HTML5 (DPA) sessions via the same LB&lt;/B&gt;, the session fails with the error:&lt;/P&gt;&lt;P&gt; &lt;B&gt;DPA_CREATE_TUNNEL_TARGET_UNREACHABLE&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Interestingly, if we bypass the LB and point directly to a specific PSM Connector, the &lt;B&gt;same target works perfectly with HTML5.&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Key Observation:&lt;/B&gt;&lt;/P&gt;&lt;P&gt; In the failing case via Load Balancer, the logs show that the connection is trying to reach the &lt;B&gt;LB VIP instead of the actual target machine&lt;/B&gt;, which causes the HTML5 tunnel to fail.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any special configuration required on OCI Load Balancer for HTML5/DPA traffic?&lt;/P&gt;&lt;P&gt;Does HTML5 require Layer 7 features like WebSocket support, session persistence, or URL path handling?&lt;/P&gt;&lt;P&gt;Has anyone successfully configured OCI LB for CyberArk HTML5 access?&lt;/P&gt;&lt;P&gt;any resolution for this error?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 09:31:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423285#M7874</guid>
      <dc:creator>M.Arsh335937</dc:creator>
      <dc:date>2025-10-15T09:31:44Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 based connection via load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423286#M7875</link>
      <description>&lt;P&gt;Hi @Mohd Arsh​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This error means the HTML5 GW &amp;nbsp;failed to establish the RDP connection to the target machine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please verify that OCI LB listener for the HTML5 traffic is configured for&amp;nbsp;HTTPS on port 443 and not just a plain TCP listener.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also enable&amp;nbsp;Session Persistence&amp;nbsp;/ Sticky Sessions  on LB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please verify that the PSM is not sending traffic back to the LB VIP. Check the routing as well &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the LB is set to terminate SSL traffic then LB's trust store must have Root and Intermediate CAs&amp;nbsp;that issued the PSM certificates.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ensure PSM certs are imported into HTML5 GW server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps!&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 10:43:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423286#M7875</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-10-15T10:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 based connection via load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423287#M7876</link>
      <description>&lt;P&gt;Hi @Malhar Vora​&amp;nbsp; &lt;/P&gt;&lt;P&gt;Thanks for input &lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;B&gt;OCI LB listener&lt;/B&gt; is already configured for &lt;B&gt;HTTPS on port 443&lt;/B&gt;.&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;Session Persistence / Sticky Sessions&lt;/B&gt; are also enabled.&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;SSL verification&lt;/B&gt; is currently turned &lt;B&gt;off&lt;/B&gt; in the HTML5 (SIA) settings, so certificates should not be causing the issue.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Despite this, the HTML5 connection is still failing, anything else we can verify.&lt;/P&gt;&lt;P&gt;if we bypass the LB and point directly to a specific PSM Connector, the&amp;nbsp;same target works perfectly with HTML&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 11:44:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423287#M7876</guid>
      <dc:creator>M.Arsh335937</dc:creator>
      <dc:date>2025-10-15T11:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 based connection via load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423288#M7877</link>
      <description>&lt;P&gt;Hi @Mohd Arsh​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m now thinking that LB might be acting at Layer 7 which rewrites headers and makes the HTML5 tunnel think the target is the LB VIP&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you check with your LB team to see if it’s possible to use a Layer 4 TCP listener instead of HTTPS?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 11:56:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423288#M7877</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-10-15T11:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 based connection via load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423289#M7878</link>
      <description>&lt;P&gt;Hi @Malhar Vora​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;TCP 3389 listener&lt;/B&gt; → Already configured and working for Thick Client RDP. (layer 4)&lt;/P&gt;&lt;P&gt;&lt;B&gt;HTTPS 443 listener&lt;/B&gt; → Configured and intended for HTML5 (DPA/SIA) traffic. (layer 7)&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 12:13:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423289#M7878</guid>
      <dc:creator>M.Arsh335937</dc:creator>
      <dc:date>2025-10-15T12:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 based connection via load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423290#M7879</link>
      <description>&lt;P&gt;Hi @Mohd Arsh​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First, it doesn't matter which HTML5 GW (DPA/SIA or SecureTunnel),the listener on LB should be TCP/3389 from SIA/ST. You don't need to load balance HTTPS (HTML5GW) for Privilege Cloud deployment. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On your LB configuration, use pure L4 (TCP) load balancing. Avoid using L7 (RDP) and SSL inspection as this may broke the certificate validation. &lt;/P&gt;&lt;P&gt;Below is the LB configuration (F5) for your reference. &lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/ispss-deployment/latest/en/content/privilege%20cloud/privcloud-example-load-balance.htm&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;On the PSM server, ensure you have apply certificates to the RDP service, and the certificate should be configured with SAN included the FQDN of the LB (case sensitive is preferred). You also need to upload the root / intermediate cert to SIA portal. &lt;/P&gt;&lt;P&gt;See the following links for reference. &lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/ispss-deployment/latest/en/content/privilege%20cloud/privcloud-certs4psms.htm#tabset-1-tab-2&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/ispss-access/latest/en/content/hometileslps/dpa-crtfcts-lp.htm&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Oct 2025 15:50:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423290#M7879</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-10-15T15:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 based connection via load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423291#M7880</link>
      <description>&lt;P&gt;hello @Malhar Vora​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;I'm facing the same issue with a client. We have the PSMs configured to use LoadBalancer and on HTML5GW connections we get the same error. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you mention "please verify that the PSM is not sending traffic back to the LB VIP. Check the routing as well", is there something configurable on Cyberak Side? Because the only option there is to put the Gateway on the LoadBalancer "PSMServer" as also on the PSMs. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 07:17:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/html5-based-connection-via-load-balancer/m-p/1423291#M7880</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-03-30T07:17:52Z</dc:date>
    </item>
  </channel>
</rss>

