I am having problems accessing a website, that recentely got SSL-security, on the server side.
Accessing the website like normal is not a problem, but when I try to open the website on the server that hosts it - it simply will not open.
This is not the only site on this server and I can access all of them, except the ones that has SSL security.
This causes a problem because the website in question contains an API-service and some of the other sites need to connect to this API.
But connecting to this website through xmlHttpRequest (and other such codes) is not working.
I would prefer not to have to rewrite all the codes for these other sites, when all the functionality is available in the API. (This would also mean making changes in so many different places as the services evolve and change.)
What can cause this problem and how do I fix it?
EDIT: There is another SSL-secured site on this server, and I was misinformed about its status. This other website can be accessed on the server side. I will go through all settings on the IIS and firewall on the server to find why they behave differently.
EDIT: I've found a solution by changing the rewrite rule - which forces the use of https - to not apply to the internal address (127.0.0.1). I am now able to access the website from the server-side.
This does not solve the problem, it is just a temporary fix to avoid the problem.