- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
10-15-2025 02:31 AM
We are using an OCI Load Balancer in front of our PSM Connectors.
When we connect using the CyberArk thick client (RDP) through the LB, everything works fine and the real target is reached.
However, when we try to launch HTML5 (DPA) sessions via the same LB, the session fails with the error:
DPA_CREATE_TUNNEL_TARGET_UNREACHABLE
Interestingly, if we bypass the LB and point directly to a specific PSM Connector, the same target works perfectly with HTML5.
Key Observation:
In the failing case via Load Balancer, the logs show that the connection is trying to reach the LB VIP instead of the actual target machine, which causes the HTML5 tunnel to fail.
Is there any special configuration required on OCI Load Balancer for HTML5/DPA traffic?
Does HTML5 require Layer 7 features like WebSocket support, session persistence, or URL path handling?
Has anyone successfully configured OCI LB for CyberArk HTML5 access?
any resolution for this error?
10-15-2025 03:43 AM
Hi @Mohd Arsh
This error means the HTML5 GW failed to establish the RDP connection to the target machine.
Please verify that OCI LB listener for the HTML5 traffic is configured for HTTPS on port 443 and not just a plain TCP listener.
Also enable Session Persistence / Sticky Sessions on LB
please verify that the PSM is not sending traffic back to the LB VIP. Check the routing as well
If the LB is set to terminate SSL traffic then LB's trust store must have Root and Intermediate CAs that issued the PSM certificates.
Ensure PSM certs are imported into HTML5 GW server.
Hope it helps!
10-15-2025 04:44 AM
Hi @Malhar Vora
Thanks for input
Despite this, the HTML5 connection is still failing, anything else we can verify.
if we bypass the LB and point directly to a specific PSM Connector, the same target works perfectly with HTML
10-15-2025 04:56 AM
Hi @Mohd Arsh
Thanks for the update.
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
Can you check with your LB team to see if it’s possible to use a Layer 4 TCP listener instead of HTTPS?
10-15-2025 05:13 AM
Hi @Malhar Vora
TCP 3389 listener → Already configured and working for Thick Client RDP. (layer 4)
HTTPS 443 listener → Configured and intended for HTML5 (DPA/SIA) traffic. (layer 7)
10-15-2025 08:50 AM
Hi @Mohd Arsh ,
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.
On your LB configuration, use pure L4 (TCP) load balancing. Avoid using L7 (RDP) and SSL inspection as this may broke the certificate validation.
Below is the LB configuration (F5) for your reference.
https://docs.cyberark.com/ispss-deployment/latest/en/content/privilege%20cloud/privcloud-example-load-balance.htm
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.
See the following links for reference.
https://docs.cyberark.com/ispss-deployment/latest/en/content/privilege%20cloud/privcloud-certs4psms.htm#tabset-1-tab-2
https://docs.cyberark.com/ispss-access/latest/en/content/hometileslps/dpa-crtfcts-lp.htm
03-30-2026 12:17 AM
hello @Malhar Vora ,
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.
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.
Thank you
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

