QMC and HUB no accessible with error "Could not connect to the license service"

[Shadi_Sai]

After Migration of the system, the services are all running however the QMC and HUB aren't working, I tried checking similar cases and they got the same problem but no solution for it, I check the C:\ProgramData\Qlik\Sense\Log\Repository\Trace\"Server_NAME"_System_Repository.txt log and I got the following error:
There was an error contacting the license service. Keep retrying... (130 failed requests) GET /v1/licenses/overview StatusCode: InternalServerError Response: . Could not connect to the license service.

in the Proxy log trace i got the following:
When contacting https://localhost:4242/ No connection could be made because the target machine actively refused it 127.0.0.1:4242↵↓Unable to connect to the remote server

I checked the ports in cmd and here is what I got:

Port 4242:

TCP 127.0.0.1:60433 127.0.0.1:4242 SYN_SENT 11832

Port 4432:

TCP 10.10.10.229:4432 0.0.0.0:0 LISTENING 12128
TCP 10.10.10.229:4432 10.10.10.229:52410 ESTABLISHED 12128
TCP 10.10.10.229:4432 10.10.10.229:52438 ESTABLISHED 12128
TCP 10.10.10.229:52410 10.10.10.229:4432 ESTABLISHED 11832
TCP 10.10.10.229:52438 10.10.10.229:4432 ESTABLISHED 11972
TCP 127.0.0.1:4432 0.0.0.0:0 LISTENING 12128

I don't know if the ports are used or no and that is the reason its refusing the connection, I had iis on the same machine but I have removed it.

Appreciate the help.

[Alan_Slaughter · Accepted solution]

Hi Shadi_Sai, could you please review this article:

https://community.qlik.com/t5/Official-Support-Articles/Node-offline-GET-v1-licenses-overview-Status...

[Shadi_Sai · Accepted solution]

Hi @Alan_Slaughter  , I have checked the following article before but the fix didn't work for my case, however I have solved the issue with the support team, the problem was the IPv6 IP was using the port however the service only recognizes the IPv4 IP of the machine (127.0.0.1:4242 only will work), and the solution was to disable the IPv6 protocol in the network adapter.
I hope it can help someone if he encountered the same issue.

[tin_u]

Thank you for posting the resolution @Shadi_Sai, i was having the same issues on a server that was working previously when this suddenly popped up during the holidays, i disabled IPv6 in the network adapter and restarted the server, everything works again.