After adding a rim node successfully, the hub is inaccessible from that node, but the QMC works as normal
When looking into the repository log on the node, you can see repeated failed attempts at retrieving the app migration hash. You will see lines like:318832 20180224T062727.823+0000 INFO QSSERVER System.Repository.Repository.Core.SystemInformation 130 3b5bab24-023c-4b82-a3b5-29ddc51d2765 SERVICE\ACCOUNT Exception encountered when fetching app migration hash, still trying. Failed attempts: 380 The request was aborted: Could not create SSL/TLS secure channel. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)↵↓ at Qlik.Sense.Common.Communication.REST.Client.WebClientEx.GetWebResponse(WebRequest request, IAsyncResult result)↵↓ at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result) 3b5bab24-023c-4b82-a3b5-29ddc51d2765
If you attempt to reach http://localhost:4545/migrate you receive a Service Unavailable error, possibly with the suggestion to enable TLS 1.0 or SSL
It may work when contacting the server removely.Environment:
Qlik Sense any version
Qlik Sense uses the TLS settings and ciphers available to the underlying windows server, problems can arise if the server components are not in harmony with the client components.
There is an issue relating to ciphers available within the affected system.
Ciphers/Protocols that should not be used may have only been disabled only for Server or Client, rather than for both.
Verify in the respective registry location, example:
If 1.2 should not be used, it should be disabled for both Client and Server.
In the initial case with this issue, DisabledByDefault TLS was set to 1, preventing some of the dispatcher services from connecting properly.
Set DisabledByDefault TLS to 0, then restart services.