Quick thoughts here:
- Do all debugging on the server. If you ultimately want external access, be sure the server itself is functional then expand outward.
- That's not a Qlik Sense 404 page, so something else is serving up that 404 page
- I would expect you to enter the QMC via https://ServerName/qmc rather than https://ServerName/Something/QMC, but in any case this page is being delivered by something other than Qlik Sense.
From (1) you will need to investigate what service is binding to port 444. A netstat -ano | findstr :443 command on the server to point you into the direction of what service is binding that port. Stop that service then restart the Proxy Service to make sure Sense can bind to that port. The Log > Proxy > Trace > system log will write whether Sense can bind to 80 and/or 443.
Right guys - for anyone else looking at this, it's to do with services eating each other I think.
1. QlikView and Qlik Sense don't work on the same server. I didn't know this. So in my Amazon Instance I had to turn off all existing QlikView Services.
This didn't fix it, I might add.
2. Linked to the above reply from Levi, SQL interferes with the port (?). Turn off SQL services.
Then it worked.