Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Alan Falloon 12 posts 142 karma points
    Dec 16, 2018 @ 23:35
    Alan Falloon
    0

    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

  • Alan Falloon 12 posts 142 karma points
    Dec 17, 2018 @ 01:23
    Alan Falloon
    100

    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.

  • Jcr 18 posts 128 karma points
    Dec 17, 2018 @ 20:34
    Jcr
    0

    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

  • Alan Falloon 12 posts 142 karma points
    Dec 17, 2018 @ 20:36
    Alan Falloon
    0

    Yes it is resolved now, I suspect it had nothing to do with Azure

  • Jcr 18 posts 128 karma points
    Dec 17, 2018 @ 20:37
    Jcr
    0

    That's excellent news!

Please Sign in or register to post replies

Write your reply to:

Draft