nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

IIS reverse proxy with Confluence

Aaron Newark

I am setting up a reverse proxy in IIS for Confluence (eventually Jira, Bitbucket and Bamboo too) based on the directions here (https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-microsoft-internet-information-services-iis-833931378.html) and I can't get it to work. I am trying to setup the proxy from https://server.domain.com/confluence and based on my understanding of the documentation I change the context path from this:

to this:

and I commented out the default connector for the HTTPS Proxying one from the config file and set it up as recommened like this

I setup the rules for the URL rewrite, and Syncology setup via the IIS Manager UI and it saves my changes to web.config as the following:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name="Confluence Proxy" stopProcessing="true">
                    <match url="(.*)" />
                    <action type="Rewrite" url="http://server.domain.com:8090/{R:1}" />
                </rule>
                <rule name="Synchrony HTTP" stopProcessing="true">
                    <match url="synchrony/(.*)" />
                    <conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
                    <action type="Rewrite" url="http://localhost:8091/synchrony/{R:1}" />
                </rule>
                <rule name="Synchrony Web Sockets Reverse Proxy" stopProcessing="true">
                    <match url="ws://(.*)" />
                    <conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
                    <action type="Rewrite" url="ws://localhost:8091/{R:1}" />
                </rule>
                <rule name="Confluence Reverse Proxy" enabled="false" stopProcessing="true">
                    <match url="(.*)" />
                    <conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
                    <action type="Rewrite" url="http://localhost:8090/{R:1}" />
                </rule>
            </rules>
        </rewrite>
        <security>
            <requestFiltering allowDoubleEscaping="true" />
        </security>
        <caching enabled="false" enableKernelCache="false" />
    </system.webServer>
</configuration>

But then after I save all config changes, and start the Confluence server I get this error from Tomcat when I go to https://server.domain.com/confluence almost immediately:

HTTP Status 404 – Not Found

Type Status Report

Message Not found

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

Apache Tomcat/9.0.10

However if I keep all my settings the same but remove the /confluence from the context path, the browser will load for a bit and then attempt to bring up the login page but doesn't append the /confluence folder to the end (due to the context path not being there I assume). With either configuration when I check the Tomcat logs (C:\Program Files\Atlassian\ApplicationData\Confluence\logs) there are no errors in the log and the warnings that are there are the same as I saw before setting this up, so nothing seems out of what is expected there. What am I missing here in the setup? Let me know if you need any other information on this.

Accepted answers

Micko_9o0ad6

The rules above are good but the first one redirects to the wrong location.

I came across this exact same issue two years later and this post helped. My URL Rewrite rules in IIS were broken. I was effectively dropping the confluence from the redirect using {R:1} with the pattern below.

(^confluence/(.*))|(^confluence$)

For "https://domain.com/confluence", the pattern matched but only {R:0} and {R:3} contained the path required for the rewrite. Adding a trailing back slash or using {R:0} rectified the issue so I had to revisit my rules.

If you're seeing this issue, double check the URL Rewrite rules in IIS and retest your patterns.

All comments

JP _AC Bielefeld Leader_

Hi Aaron,

when you change the path in the connector section, did you also change the path at the context section:

Best

Aaron Newark

Yes I tried that at first and only removed it to see if it would help with the 404 errors, which it kind of did. As soon as I put in the context path it gives me the 404, but if I remove it the web server seems to come up and is accessible, but doesn't redirect to the proper proxy folder as it doesn't have the context path. That's what the issue is here it seems. Thanks for the suggestion though!

Micko_9o0ad6

The rules above are good but the first one redirects to the wrong location.

(^confluence/(.*))|(^confluence$)

If you're seeing this issue, double check the URL Rewrite rules in IIS and retest your patterns.

Aaron Newark

I think what you're saying makes sense, but back when I couldn't get help I switched from an IIS proxy to an NGINX proxy, the setup was way easier, and met the needs well enough. Thanks for the follow-up answer, I'm going to accept it, but I don't' have a way to verify it.

Zhi Lu

Hi Micko,

I am running into exactly the same problem...

Have tried to update the URL rewrite to {R:0} but still it doesn't work.

"Adding a trailing back slash" - could you please exlain more on this? thanks.

Zhi url rewrite.png

Micko_9o0ad6

My current rule uses {R:1}. My description of the solution is misleading.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server

atlassian-support

reverse-proxy

iis