I have a web application with an api and services that has been running successfully on Azure for two years on a VM. I am now making changes to the code and have created a new "staging" VM to test my changes. Everything works great
for both machines. I have also attached a traffic manager to each VM and point my friendly URL to the traffic manager. After testing my staging site, I switch the traffic managers so the production friendly URL is pointing to my staging VM and
my staging friendly URL is pointing to the older production VM. The site and services run fine, but when I try to access the api to the new staging VM, I'm getting a 403 error, which boils down to my site is not picking up client certificates. The
settings in IIS are exactly the same for both machines, and when I switch the traffic managers back to the original configuration, the api access is fine again. Has anybody run into this problem before? I need some help!
↧