Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
simonaubert
Partner - Specialist II
Partner - Specialist II

official Qlik-Cli and certificate issue

Hello all,

My goal is to export qlik application scripts.
I use this version of Qlik-cli (so not the powershell module) https://github.com/qlik-oss/qlik-cli

It's a QSEOW so client-managed.

 

I have launched on the server itself : 

 

 

qlik app script get --app "04eecf48-e033-4a98-b273-767b73cfe447" -s https://localhost:4244

 

 

 

and received this answer :

 

 

Error: could not connect to engine on wss://localhost:4244/app/04eecf48-e033-4a98-b273-767b73cfe447
       This probably means that you have certificates that are not signed properly.
       If you have a self signed certificate then the flag '--insecure' might solve the problem.

 

 

 

i tried with the --insecure and got :

 

 

Error: could not connect to engine on wss://localhost:4244/app/04eecf48-e033-4a98-b273-767b73cfe447
       This probably means that there is no engine running on the specified url.

       Check that the engine is up and that the url specified is correct.

 

 

 

 

Then I tried to open the QMC from the server :
image.png

 

simonaubert_0-1655545407818.png

 

Do you think it's related ? Or is it something else ?

Best regards,

Simon

 

Bi Consultant (Dataviz & Dataprep) @ Business & Decision
Labels (2)
2 Replies
Damien_Villaret
Support
Support

Hello @simonaubert 

You cannot use the same command to import an app in Qlik Sense for Windows than the one for SaaS.

You need to import the app through the Qlik Repository Service (QRS), there is a tutorial on how to call it from Qlik-cli
https://qlik.dev/tutorials/using-qlik-sense-on-windows-repository-api-qrs-with-qlik-cli

If the issue is solved please mark the answer with Accept as Solution.
hakana
Employee
Employee

Hi,
It also looks like you are trying to connect directly to the engine. The engine doesn't use HTTPS.
Either connect through the proxy using HTTPS (:443) or try to connect to the engine with just HTTP.