Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
The hostname in Qlik Sense is determined by the content of host.cfg. In order to change the hostname you must change the value in this file. This will also result in all certificates being invalidated.
Once invalidated, they need to be recreated and any passwords stored in the database will need to be reset (e.g Data Connections and User Directory Connector credentials). Passwords are encrypted based on the server certificates. For an alternative method that may not required passwords to be reset, see How to Change the Qlik Sense server hostname
In a single node site this is sufficient, in a multi-node system there are further steps required.
Please note the information on this article pertain to steps when changing the server hostname only, and not the Windows domain which it is joined to. When changing the domain please see the links below for more information:
For Video transcript click here.
[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("yourServerHostname.yourDomain.com"))
Correcting Share paths if it is shared on the Central Node:
Update the Qlik Sense Data connections via the Qlik Management Console (QMC):
The relevant tables in the repository database that contain the host name information are:
LocalConfigs ( Hostname column )
ServerNodeConfigurations ( Host Name )
Note: Please make sure that the above table hostname column should contain the correct server FQDN ( network host name and not the individual machine host name ) this should be exactly the hostname that is in the host.config file
Note : LocalConfigs table has been removed in Qlik Sense Enterprise February 2019 and newer.
There are three possible scenarios in a multi-node environment. Changing the hostname for a Rim node only, the hostname of the Central node, or both. Certificates are always generated by the central node and are based on hostname so the change of hostname on the Central node consumes more time, will require redistribution, and in some cases also the deletion and re-adding of node information.
On the Rim node:
[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("qlikserver.domain.local"))
Unfortunately it is not possible to adjust the hostname of a node in QMC, so a when a Rim node's hostname is changed you have to then delete and re-add it with the steps below.
On the Central server:
All certificates used by Qlik Sense are created and signed by the central node and are based on its hostname, changing the hostname on the central node and recreating all self-signed certificates breaks this chain of trust and thus all certificates on all rim nodes will need to be recreated and redistributed.
On every Rim node:
On the central node:
[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("qlikserver.domain.local"))
10. Start all the Qlik Sense services in the proper order. If the Qlik Logging Service (Centralized logging database) has been installed see Error 1064 Unable to start Qlik logging service after hostname was changed. Also see Manual Start and Stop order of Qlik Sense services.
11. Confirm the new certificates are created and QMC is accessible.
12. In the QMC under Nodes, select each Rim node and click Redistribute, and follow the instructions displayed in order to install the certificates on the Rim node.
13. Perform the steps under "Correcting Share paths if it is shared on the Central Node" above under the Single Node section.
14. Also if Centralized logging is enabled, the following Data Connection host value needs to be updated:
15. Change the 'trustedLocations' and 'url' values in all the monitor_REST_* Data Connections to the new Fully Qualified Domain Name (FQDN). Any other Qlik Sense Data Connections' Connection string need to be updated to have these values in the Connection string set to the new FQDN of the Central node. These are listed in QMC under the Data Connections section. See example under How to set up Monitoring Apps in a clustered environment
16. Keep in mind: The central certificate is used to encrypt password strings being used in connectors, so changing this certificate means that you will need to re-type and save the passwords for all Data Connections and User Directory Connectors that include password information. See related article Reload of the Operations Monitor app or other monitoring apps fail with 401 (Unauthorized) The steps for resetting passwords are also mentioned in the following article Repository System Log Shows Error "Not possible to decrypt encrypted string in database".
Back on the Rim node(s):
# Set the Installation Directory for Qlik Sense $installDir = 'C:\Program Files\Qlik\Sense\' # Specify the new password for the qliksenserepository account $password = 'MyNewPassword' $files = Get-ChildItem -Path $installDir -Include Configure-Service.ps1 -Recurse foreach ($file in $files) { $ScriptToRun=$($file.FullName) &$ScriptToRun localhost 4432 qliksenserepository $password }
5. The RIM node points to a FQDN for connections to the QSR database. This is different than in a Single Node environment with postgreSQL installed locally where 'localhost' is used in the connection strings instead of the FQDN to connect to the database. So the listen_addresses setting in the postgres.conf file on the central node needs to be updated if in fact the postgreSQL (QSR) database is hosted on the Central node. The article on step 7 covers this as well. For more information see PostgreSQL: postgresql.conf and pg_hba.conf explained
6. Start all the Qlik Sense services in the proper order. See Manual Start and Stop order of Qlik Sense services .
7. If Centralized Logging / Logging Database is enabled in the environment, follow the steps documented under the article below:
8. Validate that the in QMC, the node are registered as online in the Nodes section.
the relevant tables in the repository database that contain the host name information are:
LocalConfigs ( Hostname column )
ServerNodeConfigurations ( Host Name )
Note: Please make sure that the above table hostname column should contain the correct server FQDN ( network host name and not the individual machine host name ) this should be exactly the hostname that is in the host.config file
Note : LocalConfigs table has been removed in Qlik Sense Enterprise February 2019 and newer.