Qlik with Minikube - wrong redirection for console ?

[dvasseur]

Hi,

I've installed a QCS config using minikube, so access url is https://elastic.example:32443. So, the console url should be https://elastic.example:32443/console , but when using the url there is a internal redirect to https://elastic.example/console (port 443 and not 32443 anymore). Obviously nothing is listening on port 443 and so I cannot access to the console, and license the product... and use Qlik Sense 😛

I've just discovered Docker/Kubernetes so there may be an easy fix for this, any idea ?

David

[treysmithdev]

You need to set up a port forward from your host to your kubernetes cluster. You might have to adjust the following to account for your OS. Below is for Ubuntu.

Find your service name:

kubectl get svc

Do the following replacing %qcs service name%with appropriate name from above and %default% with the appropriate namespace.

kubectl port-forward service/%qcs service name% 32443:32443 -n %default% --address 0.0.0.0

You will probably also need to execute the following on the host machine:

sudo iptables -P FORWARD ACCEPT

 To make this setting persistent you'll need to utilize iptables:

sudo apt-get install iptables-persistent

[dvasseur]

Hi,

thanks for your feedback. Indeed I also had to play with iptables in order to allow a remote access to my QCS config but it won't solve my port-changing issue (QCS replying with and url on port 443 instead of the default 32443 one). I could forward 443 to 32443 using iptables/haproxy/... but it would be better to have this fixed in Qlik itself.

BR,

David

[Leigh_Kennedy]

Do you still have a problem with this url?

https://elastic.example:32443/console/license/overview/

Cheers.

[dvasseur]

It's working with this url, thanks ! At least now, I can license Qlik and use it.

Is this a known bug with the '/console' url ?