CORS - the error that refuses to die

Question

I've had this error on and off since moving from ArcIMS - cross site errors, but now I've hit something I simply cannot explain We have a server. The server has 4 IIS sites, one of which is 'AGS' - hosting Portal and Server. The other 3 are all internal mapping sites. We use http across the board as I struggle to get certificates to include all the alternative names, plus it serves no real benefit in-house The 3 internal sites all have IP bindings set to specific IP addresses allocated to the server AGS is set to "All unallocated" There are 4 IP addresses allocated to this server, so it should only be picking up the one left over. As it is, it all works. But I did hit issues when updating AGS, so I rolled back the change and investigated. As soon as I switch AGS to use the one remaining IP address - so the 'unallocated' one I get Access to XMLHttpRequest at 'http:///server/rest/services/BaseMapZoomStack/MapServer?f=json&dpi=96&transparent=true&format=png8' from origin 'http://' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Somehow it would appear that the 'unallocated' setting in IIS isn't doing what it should. In addition https:// :443/portal/webadaptor 404s - with the physical path pointing to to folder structure of one of the mapping sites that has a allocated IP address - both AGS and the mapping website have https bound to 443. Removing the http binding from one of the other 3 sites (not all of them) makes things happy - as long as the AGS site is "all unassigned" Making https for AGS bind to the IP address it should be using gives another "resource cannot be found" message. Something is obviously wrong with the allocation, I have tried adding the server name into HOSTS along with the IP address it should be using but that didn't work I'm at a loss. Until I resolve this I am relucatnat to upgrade AGS (currently on 10.6.1) as everytime I hit these issues.

AdrianMarsden · Answer

Yes - the other 2 do have a 443 binding, but don't seem to mess with the process.  And yes, I think certificates are an issue here, maybe not THE issue, but do mess with things.  It is as if the "All Unallocated" on the AGS site is using the first IP address it can find regardless of the bindings of the other sites.

TrinaNair · Answer

Hi Adrian, are the other 2 bindings also 443?  I found that I had to uninstall, and set the other 2 bindings for the install to another port.  I left the 443 binding to the fully qualified name (in the hosts file) and the URL that will have the SSL Certificate for the AGS install.  After the install of AGS and the Webadaptor, I set the other 2 bindings back to 443.