I seem to have a strange problem. I had an HTTPS site with an SSL certificate set up on a windows 2012 server and it ran fine but it was not on the default 443 port.
So to access the site you would type https://test.site.com:1234. The site was linked to an external IP so you could access it from outside the network using https://test.site.com:1234.
I now need it to run on the default 443 port. After editing the bindings the site is no longer accessible externally and If I try accessing it from a local network using the local IP I get an SSL error and if I accept then I'm directed to a 404 page.
Putting the site back on to the 1234 port makes it accessible again. So to me, it seems as if something is up with the port.
The site 'test.site.com' isn't a registered domain so I don't know if that would be part of the problem?
I checked the firewall and as far as I can see everything seems fine there.
So, the HTTPS site works if it is not running off the default 443 port. Once on the default 443 port, it is inaccessible.
Could the issue be related to the SSL cert or the lack of registered domain name?
edit - I can now access the site via local IP. It is only the external access that a problem.