<?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 Gateway with Docker. Certificate issuer verification error in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307513#M9692</link>
    <description>&lt;P&gt;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..&lt;/P&gt;</description>
    <pubDate>Thu, 05 Oct 2023 06:20:55 GMT</pubDate>
    <dc:creator>Rajeeb_Baral</dc:creator>
    <dc:date>2023-10-05T06:20:55Z</dc:date>
    <item>
      <title>HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307506#M9685</link>
      <description>&lt;P&gt;(Docker Gateway Version 12_00_3_3)&lt;/P&gt;&lt;P&gt;I have exactly the same error as described in article &lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/PSMGW-HTML5-GW-Docker-TLS-Implementation-SSL-Certificates&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The healthcheck of the gateway works without any certificate errors &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;connecting to the psm via rdp (mstsc) is working without any certificate warnings&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the gatewayname as well as psmname in the cyberark configuration was written exactly like the CN in the certificates &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;running &amp;nbsp;openssl s_client -connect psmserver1.xxx.xx:3389 inside and outside the container works without any certifcate errors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Trying to connect via PSM and HTML5 Gateway immediatelly closes the browser tab. Logfile shows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;guacd[102]: DEBUG:&amp;nbsp;&amp;nbsp;&amp;nbsp;Certificate verification failure 'unable to get local issuer certificate (20)' at stack position 1&lt;/P&gt;&lt;P&gt;guacd[102]: DEBUG:&amp;nbsp;&amp;nbsp;&amp;nbsp;O = xxx, OU = xxx, CN = xxx Internal Issuing CA EMEIA - G1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Sep 2021 10:05:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307506#M9685</guid>
      <dc:creator>alexander_roth_external</dc:creator>
      <dc:date>2021-09-17T10:05:16Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307507#M9686</link>
      <description>&lt;P&gt;Does the openssl command work inside the container when you run it as the user "psmgwuser" (via sudo for example)?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Sep 2021 12:01:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307507#M9686</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-09-17T12:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307508#M9687</link>
      <description>&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[root@xxxxxx PSMGWDockerInstallation]# sudo -u psmgwuser openssl s_client -connect psmserver1.xxx.xxx.xx:3389&lt;/P&gt;&lt;P&gt;CONNECTED(00000003)&lt;/P&gt;&lt;P&gt;depth=1 O = xxxx, OU = xxxx, CN = xxxx Internal Issuing CA EMEIA - G1&lt;/P&gt;&lt;P&gt;verify error:num=20:unable to get local issuer certificate&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;Certificate chain&lt;/P&gt;&lt;P&gt;&amp;nbsp;0 s:/C=DE/ST=xxxxx/L=xxxx/O=xxxx/OU=xxxx/CN=xxx.xxx.xxx.xx&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;i:/O=xxxx/OU=xxxx/CN=xxxx Internal Issuing CA EMEIA - G1&lt;/P&gt;&lt;P&gt;&amp;nbsp;1 s:/O=xxxx/OU=xxxx/CN=xxxx Internal Issuing CA EMEIA - G1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;i:/O=xxxx/OU=xxxx/CN=xxxx Internal Root CA - G1&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;Server certificate&lt;/P&gt;&lt;P&gt;-----BEGIN CERTIFICATE-----&lt;/P&gt;&lt;P&gt;xxx&lt;/P&gt;&lt;P&gt;xxx&lt;/P&gt;&lt;P&gt;xxx&lt;/P&gt;&lt;P&gt;-----END CERTIFICATE-----&lt;/P&gt;&lt;P&gt;subject=/C=DE/ST=xxxx/L=xxxx/O=xxxx/OU=xxx/CN=xxx.xxx.xxx.xx&lt;/P&gt;&lt;P&gt;issuer=/O=xxxx/OU=xxxx/CN=xxxx Internal Issuing CA EMEIA - G1&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;No client certificate CA names sent&lt;/P&gt;&lt;P&gt;Peer signing digest: SHA256&lt;/P&gt;&lt;P&gt;Server Temp Key: ECDH, P-256, 256 bits&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;SSL handshake has read 5312 bytes and written 415 bytes&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384&lt;/P&gt;&lt;P&gt;Server public key is 3072 bit&lt;/P&gt;&lt;P&gt;Secure Renegotiation IS supported&lt;/P&gt;&lt;P&gt;Compression: NONE&lt;/P&gt;&lt;P&gt;Expansion: NONE&lt;/P&gt;&lt;P&gt;No ALPN negotiated&lt;/P&gt;&lt;P&gt;SSL-Session:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Protocol&amp;nbsp;: TLSv1.2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Cipher&amp;nbsp;&amp;nbsp;: ECDHE-RSA-AES256-GCM-SHA384&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Session-ID: DC2B0000D1C2A4584B1AD534323435FFFDE0E7A6B9AC84A840F6249A0579E671&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Session-ID-ctx:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Master-Key: D9DDB6CF77CA6EFA80FB0A7F0A96CAE970B11E15ECD5D7F44CD50B227A629724456169D8D4D3F18F9DFEBE0EF812D5F1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Key-Arg&amp;nbsp;&amp;nbsp;: None&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Krb5 Principal: None&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;PSK identity: None&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;PSK identity hint: None&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Start Time: 1631881663&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Timeout&amp;nbsp;&amp;nbsp;: 300 (sec)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Verify return code: 20 (unable to get local issuer certificate)&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;</description>
      <pubDate>Fri, 17 Sep 2021 12:40:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307508#M9687</guid>
      <dc:creator>alexander_roth_external</dc:creator>
      <dc:date>2021-09-17T12:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307509#M9688</link>
      <description>&lt;P&gt;I have checked where the certificates are located inside the container by executing the command "&lt;I&gt;openssl version -d&lt;/I&gt;". Finally the required certificate is located inside the container at "&lt;I&gt;/opt/trust/import/xxxx_PKI_chain.pem&lt;/I&gt;" with read permissions for root only. I've changed permissions to 644 and from then the Gateway is working as expected.&lt;/P&gt;&lt;P&gt;@Bernhard: Is this a valid solution ?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Sep 2021 13:37:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307509#M9688</guid>
      <dc:creator>alexander_roth_external</dc:creator>
      <dc:date>2021-09-17T13:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307510#M9689</link>
      <description>&lt;P&gt;I'd change the permission *outside* of the container and then redeploy it.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Sep 2021 14:30:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307510#M9689</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-09-17T14:30:02Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307511#M9690</link>
      <description>&lt;P&gt;@Alexander Roth​&amp;nbsp;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?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Dec 2021 03:07:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307511#M9690</guid>
      <dc:creator>M.Rai201068067079</dc:creator>
      <dc:date>2021-12-07T03:07:45Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307512#M9691</link>
      <description>&lt;P&gt;@Manisha Rai​&amp;nbsp;No, I didn't. After changing the permission, everything is working fine without any issues. &lt;/P&gt;</description>
      <pubDate>Tue, 07 Dec 2021 07:25:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307512#M9691</guid>
      <dc:creator>alexander_roth_external</dc:creator>
      <dc:date>2021-12-07T07:25:10Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307513#M9692</link>
      <description>&lt;P&gt;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..&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2023 06:20:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307513#M9692</guid>
      <dc:creator>Rajeeb_Baral</dc:creator>
      <dc:date>2023-10-05T06:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307514#M9693</link>
      <description>&lt;P&gt;We are experiencing issues with the container run also, error we get is Error Unable to get issuer certificate getting chain....&lt;/P&gt;&lt;P&gt;At the importing certificate and configuring tomcat keystore.&lt;/P&gt;&lt;P&gt;Any advice appreciated.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 03 Sep 2024 16:37:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307514#M9693</guid>
      <dc:creator>sclarlvN</dc:creator>
      <dc:date>2024-09-03T16:37:17Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307515#M9694</link>
      <description>&lt;P&gt;The above also fixed our issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2024 08:50:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307515#M9694</guid>
      <dc:creator>sclarlvN</dc:creator>
      <dc:date>2024-10-09T08:50:16Z</dc:date>
    </item>
    <item>
      <title>Re: HTML5 Gateway with Docker. Certificate issuer verification error</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307516#M9695</link>
      <description>&lt;P&gt;how could you resolved the problem? I have the same issue&lt;/P&gt;</description>
      <pubDate>Mon, 25 Aug 2025 10:05:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/html5-gateway-with-docker-certificate-issuer-verification-error/m-p/1307516#M9695</guid>
      <dc:creator>ikirca</dc:creator>
      <dc:date>2025-08-25T10:05:54Z</dc:date>
    </item>
  </channel>
</rss>

