Hostname/IP doesn't match certificate's altnames
Article Number: 000018018 | Last Modified: 2019/04/29
- After upgrade from one Qlik Sense track, the application is not migrated successfully
- Application in QMC is showing either Unknown or Migration failed
- Log is showing from the System Log under (C:\ProgramData\Qlik\Sense\Log\AppMigration)
Migration failed: Hostname/IP doesn't match certificate's altnames: Error: Hostname/IP doesn't match certificate's altnames\n at SecurePair.<anonymous> (tls.js:1390:23)\n at SecurePair.emit (events.js:92:17)\n at SecurePair.maybeInitFinished (tls.js:980:10)\n at CleartextStream.read [as _read]
(C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\node_modules\\bluebird\\js\\main\\promise.js:84:37)\n at RPC.open
Node.js has issues handling self signed certificates based on IP instead of hostname.
The recommended solution is that every node in your environment are added using their Fully Qualified Domain Name and not using the IP address.