topic Re: User having issue connecting Qlik Sense into Snowflake via key pairs authentication in Connectivity & Data Prep

User having issue connecting Qlik Sense into Snowflake via key pairs authentication

desmondchew — Thu, 22 May 2025 01:32:14 GMT

We have setup a key pairs authentication providing Snoflake the public key and using private key in Qlik Sense. However when we tried to connect to Snowflake we encountered the following error.

How can we solve this please?

ERROR [HY000] [Qlik][Snowflake] (4)
REST request for URL *** failed: CURLError (curl_easy_perform() failed) - code=60 msg='SSL peer certificate or SSH remote key was not OK' osCode=11 osMsg='Resource temporarily unavailable'.

Thank you.
Desmond

Re: User having issue connecting Qlik Sense into Snowflake via key pairs authentication

FedericoDellAcqua — Thu, 29 May 2025 08:29:23 GMT

Check this out 🙂

https://community.snowflake.com/s/article/CURLerror-SSL-peer-certificate-or-SSH-remote-key-was-not-OK-during

Re: User having issue connecting Qlik Sense into Snowflake via key pairs authentication

marksouzacosta — Thu, 29 May 2025 13:58:24 GMT

Hi @FedericoDellAcqua, your link is not working.

Re: User having issue connecting Qlik Sense into Snowflake via key pairs authentication

marksouzacosta — Thu, 29 May 2025 14:00:39 GMT

Hi @desmondchew, can you show exactly with screen shots how have you setup your connection to Snowflake?

Re: User having issue connecting Qlik Sense into Snowflake via key pairs authentication

FedericoDellAcqua — Thu, 29 May 2025 14:04:02 GMT

Hello @marksouzacosta , that's strange... Iattach below the solution suggested in snowflake community that I tried to link 🙂

Solution

Run the open_ssl command to show the certificate chain while connecting to the s3 bucket endpoint as opposed to the Snowflake server.

---This would reveal a 'Verify return code: 19 (self signed certificate in certificate chain)'

---This happens when a TLS proxy presents itself and its certificate during a handshake. This confirmed the presence of a proxy in between.

Command used:

echo QUIT | openssl s_client -connect abcdn-customer-stage.s3.amazonaws.com:443 -showcerts

As a solution, please contact your network team and bypass the following:

1)The Snowflake endpoints found through SYSTEM$ALLOWLIST() and/or SYSTEM$ALLOWLIST_PRIVATELINK() for your SSL proxy.

If the issue still exists, then in addition to the above step

2) Bypass the internal stage URL [the ones that are seen in the error stack of the error thrown ].

Applies to :

All Snowflake ODBC and JDBC drivers.