Skip to main content

Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Welcome to Qlik Community! Check out our new navigation! FIND OUT MORE
Showing results for 
Search instead for 
Did you mean: 
Partner - Creator II
Partner - Creator II

QlikSense login from local server using DNS redirect (SSL-cert)


I have seen this issue on two diffrent customers now and i was hoping that someone could help me identify the problem.

In both cases I have a server that works fine using the internal name and localhost. However theese customers dont want to use the self-signed cert so i got a working SSL cert that basicly works for all subdomains of a specific name. Like this "*". To get this working you need to add a DNS-record to get a URL that will work with the cert (ex: This works fine and everythin, except when you are on the local server. If i use the servername (that worked befor with the self-signed cert) i get a cert-error (fine). However if i try to use i get the Windows Authentication screen and it asks me to add a usename and password, but it wont take my credentials. If i use the servername and localhost, it works fine. If i connect from another server, it also works.

The problem here is that i have an application running locally on the server and it wornt connect to the QRS-API unless the certificate is valid. Witch means that i need to use the name. But that way i cannot authenticate from the server.

Anyone seen this? Or anyone have any ideas?

4 Replies
Partner - Contributor III
Partner - Contributor III

do you have something in your host file on the server to resolve the domain name back to the localhost.  I suspect it still won't work but just checking.

Partner - Creator II
Partner - Creator II

No there is nothing in the host file. And as long as the DNS point to the local IP adress, it shouldnt matter. Also, i have this issue on two diffrent customers.

Partner - Specialist
Partner - Specialist

These sounds very much like somthing we've seen, and is a windows security 'feature'

You can work around this by the simple regedit from the server as documented in this URL (BryansGeekSpeak: Debugging Windows Server 2008R2 Event ID 6037 - "The target name used is not valid"), and given below for reference.

  1. Go to REGEDIT > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
  2. Right click MSV1_0 > New > Multi-String Value
  3. Type 'BackConnectionHostNames'
  4. Right click & select ‘Modify’
  5. Enter the Hostname of the site: WEBSITENAME (and on a new line enter the FQDN, as well)
  6. Restart the QlikSense Proxy
  7. Done!
Partner - Contributor III
Partner - Contributor III

Thank you for sharing. Works like a charm!