- 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.
09-17-2021 03:05 AM
(Docker Gateway Version 12_00_3_3)
I have exactly the same error as described in article
https://community.cyberark.com/s/article/PSMGW-HTML5-GW-Docker-TLS-Implementation-SSL-Certificates
The difference is, i am not using a self signed certificate. I have an intermediate and a root certificate as a .pem file and I have copied both into the folder /opt/cert. While starting the container, the log file shows, that the root and the intermediate certificate have been successfully imported to the trusted certificate authorities. Also tried this with a chained .pem.
The healthcheck of the gateway works without any certificate errors
connecting to the psm via rdp (mstsc) is working without any certificate warnings
the gatewayname as well as psmname in the cyberark configuration was written exactly like the CN in the certificates
running openssl s_client -connect psmserver1.xxx.xx:3389 inside and outside the container works without any certifcate errors.
Trying to connect via PSM and HTML5 Gateway immediatelly closes the browser tab. Logfile shows:
guacd[102]: DEBUG: Certificate verification failure 'unable to get local issuer certificate (20)' at stack position 1
guacd[102]: DEBUG: O = xxx, OU = xxx, CN = xxx Internal Issuing CA EMEIA - G1
09-17-2021 05:01 AM
Does the openssl command work inside the container when you run it as the user "psmgwuser" (via sudo for example)?
09-17-2021 05:40 AM
Very interessting. I have executed the command "sudo -u psmgwuser openssl s_client -connect xxx.xxx.xxx.xx:3389" inside the container and the certificate verification fails. Do you know, how to solve that ? Thanks for your advise.
[root@xxxxxx PSMGWDockerInstallation]# sudo -u psmgwuser openssl s_client -connect psmserver1.xxx.xxx.xx:3389
CONNECTED(00000003)
depth=1 O = xxxx, OU = xxxx, CN = xxxx Internal Issuing CA EMEIA - G1
verify error:num=20:unable to get local issuer certificate
---
Certificate chain
0 s:/C=DE/ST=xxxxx/L=xxxx/O=xxxx/OU=xxxx/CN=xxx.xxx.xxx.xx
i:/O=xxxx/OU=xxxx/CN=xxxx Internal Issuing CA EMEIA - G1
1 s:/O=xxxx/OU=xxxx/CN=xxxx Internal Issuing CA EMEIA - G1
i:/O=xxxx/OU=xxxx/CN=xxxx Internal Root CA - G1
---
Server certificate
-----BEGIN CERTIFICATE-----
xxx
xxx
xxx
-----END CERTIFICATE-----
subject=/C=DE/ST=xxxx/L=xxxx/O=xxxx/OU=xxx/CN=xxx.xxx.xxx.xx
issuer=/O=xxxx/OU=xxxx/CN=xxxx Internal Issuing CA EMEIA - G1
---
No client certificate CA names sent
Peer signing digest: SHA256
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 5312 bytes and written 415 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 3072 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-AES256-GCM-SHA384
Session-ID: DC2B0000D1C2A4584B1AD534323435FFFDE0E7A6B9AC84A840F6249A0579E671
Session-ID-ctx:
Master-Key: D9DDB6CF77CA6EFA80FB0A7F0A96CAE970B11E15ECD5D7F44CD50B227A629724456169D8D4D3F18F9DFEBE0EF812D5F1
Key-Arg : None
Krb5 Principal: None
PSK identity: None
PSK identity hint: None
Start Time: 1631881663
Timeout : 300 (sec)
Verify return code: 20 (unable to get local issuer certificate)
---
09-17-2021 06:37 AM
I have checked where the certificates are located inside the container by executing the command "openssl version -d". Finally the required certificate is located inside the container at "/opt/trust/import/xxxx_PKI_chain.pem" with read permissions for root only. I've changed permissions to 644 and from then the Gateway is working as expected.
@Bernhard: Is this a valid solution ?
09-17-2021 07:30 AM
I'd change the permission *outside* of the container and then redeploy it.
12-06-2021 07:07 PM
@Alexander Roth I am insatlling the HTML5 GW docker but running into issue "Err_connection_Timeout" when I initiate connection using new HTML5 GW. Could you let me know if you faced similar issue?
12-06-2021 11:25 PM
@Manisha Rai No, I didn't. After changing the permission, everything is working fine without any issues.
10-04-2023 11:20 PM
I had the same issue. I changed the permission to 644 on that folder and it worked for me too. It's just that information is missing in the CyberArk document. But great finding..
09-03-2024 09:37 AM
We are experiencing issues with the container run also, error we get is Error Unable to get issuer certificate getting chain....
At the importing certificate and configuring tomcat keystore.
Any advice appreciated.
Thanks
08-25-2025 03:05 AM
how could you resolved the problem? I have the same 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!

