Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Chirag_
Partner - Contributor III
Partner - Contributor III

Error Making Connection in Qlik Sense Server in Talend Data catalog

Hi Team,

I'm encountering an SSL handshake failure while running MIMB (Metadata Integration Model Bridge) in Talend Data Catalog to import metadata from Qlik Sense. Here’s a summary of the issue:

  • System: Windows Server 2022
  • MIMB Version: 11.1.0 (Patch from 2024-09-10)
  • Import Tool: Qlik Sense 11.11 to 14.x via WebSocket API
  • Server URL: wss://192.168.11.251/app/



Following is the error i am getting:

javax.websocket.DeploymentException: SSL handshake has failed
MITI.MIRException: javax.websocket.DeploymentException: SSL handshake has failed

Chirag__0-1738155323131.png

 

Best Regards

Labels (2)
1 Solution

Accepted Solutions
Chirag_
Partner - Contributor III
Partner - Contributor III
Author

Hello Qlikkies ,

A Quick update : we resolved the issue

It was the error with the certificate file ( client.pfx /server.pfx/root.pfx)

while exporting the qlik sense server certificate it ask for computer name and that name is to be used here instead of ip ( here we have used wss://192.168.11.251/app/ which is incorrect as certificate contains computer name instead of IP Address.)

we solved this issue by simply adding the computer name in Server URL part of TDC import setup.

Hope that helps,

 

 

Best Regards

Chirag

 

View solution in original post

1 Reply
Chirag_
Partner - Contributor III
Partner - Contributor III
Author

Hello Qlikkies ,

A Quick update : we resolved the issue

It was the error with the certificate file ( client.pfx /server.pfx/root.pfx)

while exporting the qlik sense server certificate it ask for computer name and that name is to be used here instead of ip ( here we have used wss://192.168.11.251/app/ which is incorrect as certificate contains computer name instead of IP Address.)

we solved this issue by simply adding the computer name in Server URL part of TDC import setup.

Hope that helps,

 

 

Best Regards

Chirag