Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I have setup IIS7 and using ARR for my reverse proxy.

I have setup a blank rule with the rule https: //*) which redirects to https://localhost:8443/{R:1}.

This seems to be working well except I am getting a 403 error...

Any recommendations?

(Can only post one URL so the space is intentional)

share|improve this question

You mentioned 'redirects' to https://localhost:8443. Does the URL Rewrite rule actually use a 'redirect'? If so, it's not utilizing ARR and is causing a client-side redirect to localhost, which the end users won't have access to (well, it will depend on if they have a site listening on their local computer on port 8443).

Instead of a redirect, use "Route to Server Farm", and point to a functioning server farm. That will cause it to function like a reverse proxy.

Check the health tests on the server farm to confirm that it is online and functional.

Additionally, if you're trying to use a site that is on the ARR server (i.e. localhost), then you may not need URL Rewrite or ARR. Just change your binding from 8443 to on port 80 and it should work directly.

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.