Anyone know how to troubleshoot this type of error? I can get to the admin area (not sure how--cool though--I'll have to figure out why 'sometime') but the site gives the too many redirect error.
What is confusing/confounding is that I've changed nothing in the Azure DNS configuration. I'm routing to a custom URL and using Azure's DNS (AD is not involved). I've tried every combination of SSL/no SSL (store SslEnabled, store URL, securitysettings.forcesslforallpages, etc.). I have a valid certificate, digwebinterface.com shows exactly what it should, I'm not using a CDN, I've examined every log I can find (I set stdoutLogEnabled="true" in web config), I examined eventlog.xml, and on and on.
I'm not sure what to do next. Getting the DNS and SSL set up was an exercise I don't want to attempt from scratch (I'm no network guru, for sure). Any ideas?
Err_Too_Many_Redirects in Azure--how to troubleshoot?
- 39
- 285
- 3/14/2011
- United States
Sadly, this is far from resolved (I was tricked for a bit, not realizing I was hitting the site with http).
I've now removed all traces of ssl (other than Azure creates an https url) and custom domain. I've completely removed my ssl cert. In other words, I'm as plain vanilla as I can make things (and I've redeployed, ensured all DB settings say 'no ssl,' etc.).
I've tried setting the store url to https (exactly the same url as shown in app service in azure portal) and http. I simply cannot get around the Err_Too_Many_Redirects.
Any troubleshooting tips would be greatly appreciated.
I've now removed all traces of ssl (other than Azure creates an https url) and custom domain. I've completely removed my ssl cert. In other words, I'm as plain vanilla as I can make things (and I've redeployed, ensured all DB settings say 'no ssl,' etc.).
I've tried setting the store url to https (exactly the same url as shown in app service in azure portal) and http. I simply cannot get around the Err_Too_Many_Redirects.
Any troubleshooting tips would be greatly appreciated.
- 39
- 285
- 3/14/2011
- United States
For what its worth, here's the latest.
I created a new core mvc app (out of the box, nothing added).
I deployed this to a new app service (in a different azure subscription).
Result: this worked fine.
I then bought a domain name and set up an Azure Front Door, redirecting http to https (see https://docs.microsoft.com/en-us/azure/frontdoor/front-door-how-to-redirect-https). And by the way, this looks really good. Azure creates and manages an SSL cert free of charge.
Result: this worked fine.
I then set up a Front Door for my nop site and set sslenabled=1 and securitysettings.forcesslforallpages=1. I set the store url to the custom domain that was created during the Front Door creation (https://www.[redacted].com).
Result: no joy.
I'm now in the land of remote debugging. If any nop/azure gurus out there have any advice, I'm all ears :)
I created a new core mvc app (out of the box, nothing added).
I deployed this to a new app service (in a different azure subscription).
Result: this worked fine.
I then bought a domain name and set up an Azure Front Door, redirecting http to https (see https://docs.microsoft.com/en-us/azure/frontdoor/front-door-how-to-redirect-https). And by the way, this looks really good. Azure creates and manages an SSL cert free of charge.
Result: this worked fine.
I then set up a Front Door for my nop site and set sslenabled=1 and securitysettings.forcesslforallpages=1. I set the store url to the custom domain that was created during the Front Door creation (https://www.[redacted].com).
Result: no joy.
I'm now in the land of remote debugging. If any nop/azure gurus out there have any advice, I'm all ears :)
