The shield ip restrictions for fine everywhere for the front-end content, but it seems that restricting the backoffice only works on my local environment and not on Azure, any ideas why that might be?
There appeared to be some quirk in the config that was causing 'play dead' to fail. After changing to 'redirect' with any url, updating, and then setting back to 'play dead', it started working as expected.
I had created new Environments and had never set the redirect url.
Backoffice IP restrictions on Azure
The shield ip restrictions for fine everywhere for the front-end content, but it seems that restricting the backoffice only works on my local environment and not on Azure, any ideas why that might be?
umbraco 7.11.0
There appeared to be some quirk in the config that was causing 'play dead' to fail. After changing to 'redirect' with any url, updating, and then setting back to 'play dead', it started working as expected.
I had created new Environments and had never set the redirect url.
Hi Alan,
That's unfortunate to hear. I'm glad you've found a workaround for the 'play dead' issue. I've created a github issue here to keep track off it.
Has this resolved your issue with using the package on Azure? Or are you still experiencing issues here?
Regards, Joshua
Yes it is resolved now, I suspect it had nothing to do with Azure
That's excellent news!
is working on a reply...