Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

am setting up my mercurial repo using the ACL extension. When I configure the ACL.deny section I am trying to deny a specific group of users. When blocking them individually ACL works as intended and aborts their change sets. However, when trying to add all these users to one group, and then block the group Mercurial gives a 502 Bad Gateway error.

When looking through my IIS logs I get no meaningful error message, and at this point am basically stuck. Does anyone have experience with this, or have an idea on what could be causing this?

Does the 502 error and the setting up of groups have anything in common, or is that misconfiguration of our IIS or SSL? I have looked and have seen no versions of this problem before, so I am thinking it is not a mercurial issue, but am asking for help with diagnostics.

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.