- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
02-04-2026 08:22 AM
I’m trying to install CyberArk PSM Gateway using Docker on Ubuntu 22.04, and I’m running into an issue with Root CA trust between PVWA and PSM Gateway.
We are using an internal CA issued by Microsoft Active Directory Certificate Services. I have placed the Root CA certificate inside the container directory /opt/cert. I start the PSM Gateway container using this directory for certificate import.
sudo ./html5_console.sh run -ti -p 443:8443 -v /opt/cert/:/opt/import:ro --cap-drop=all--cap-add={CHOWN,DAC_OVERRIDE,FOWNER,SETGID,SETUID} -e AcceptCyberArkEULA=yes -e GWCert=psmgw.crt -e GWKey=psmgw.key -e GWCAFile=rootCA.crt -e PVWACAFile=rootCA.crt -e EndPointAddress=https://pvwa.lab-env.net/PasswordVault --name psmgw.lab-env.net cahtml5gw:14_6_1_8
I have tested the Root CA in both .crt and .pem formats. The PSM Gateway starts successfully, and the certificate import process completes without errors. However, when I try to run "curl https://pvwa.lab-env.net/" from inside the container, I receive an SSL certificate verification error indicating that the Root CA is not trusted.
Has anyone faced a similar issue with Root CA trust when running CyberArk PSM Gateway in Docker? Any guidance on the correct way to install or trust the internal Root CA inside the container would be greatly appreciated.
02-04-2026 05:57 PM
I have similar issue before, and base on community discussion, i solve it with this setup:
sudo ./html5_console.sh run -ti -p 443:8443 -v /opt/cert/:/opt/import:ro -e AcceptCyberArkEULA=yes -e GWCert=psmgw.crt -e GWKey=psmgw.key -e GWCAFile=rootCA.crt -e EndPointAddress=https://<PVWA hostname>/passwordvault --name <container_name> cahtml5gw:<version_tag>Inside the cert directory i put this files:
Hope this works for you
02-04-2026 09:34 AM
The files under /opt/cert, what permissions do they have?
I have seen this when the files are owned by root and not readable by others. In the container another account (don't remember which) will try to read the pem files, but they still belong to root, so it will fail to read them.
02-04-2026 02:08 PM
@Putmano Keo Try removing PVWACAFile, that parameter is not documented. Try re-running the container with debug parameters enabled: https://community.cyberark.com/s/article/How-to-enable-debug-logging-for-html5gw-docker-and-podman-version
Also try a few curl and openssl commands from inside the container and analyze the results + new debug logs generated:
PSM: openssl s_client -connect <psm-hostname>.<domain>:3389
PVWA: openssl s_client -connect <pvwa-hostname>.<domain>:443
PVWA Curl: curl -iks https://<pvwa-hostname-or-lb>
02-04-2026 05:57 PM
I have similar issue before, and base on community discussion, i solve it with this setup:
sudo ./html5_console.sh run -ti -p 443:8443 -v /opt/cert/:/opt/import:ro -e AcceptCyberArkEULA=yes -e GWCert=psmgw.crt -e GWKey=psmgw.key -e GWCAFile=rootCA.crt -e EndPointAddress=https://<PVWA hostname>/passwordvault --name <container_name> cahtml5gw:<version_tag>Inside the cert directory i put this files:
Hope this works for you
02-05-2026 06:43 AM
I have fixed the permission but it still the same.
02-05-2026 06:43 AM
I have run the debug, but I cannot open it to read. Is it a text file? Thanks.
02-05-2026 06:46 AM
Thank you, Heron. Yes, I fixed it by duplicating rootCA.pem and rootCA2.pem. Do you know why this is necessary? Is this a bug? I used to deploy on version 12.6, and I didn’t have this issue.
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!

