Problems having one virtual host for all my Atlassian products Edited

Hi Atlassian Comunity,this is my first question so Sorry if I'm wrong in post my problem.

We have 3 servers:
- SERVER-A: IIS Frontend that reverse proxy for all atlassian software (same virtual host)
- SERVER-B: Confluence Server (multiple instance configured with different context path)
- SERVER-C: Jira Server (multiple instance configured with different context path)

So the urls is for example:

http://SERVER-A/confluencecontextpath1, http://SERVER-A/confluencecontextpath2, and so on

http://SERVER-A/jiracontextpath1, http://SERVER-A/jiracontextpath2, and so on

We configure IIS following the Atlassian KB https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-microsoft-internet-information-services-iis-833931378.html doing some modification in URL rewrite rules.
Having all contexts in the same virtual host, we change the rules specifying each context path

<rewrite>
<rules>
<clear />
<rule name="Synchrony Context1 HTTP" enabled="true" stopProcessing="true">
<match url="synchrony-proxy/(.*)" />
<conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
<action type="Rewrite" url="http://SERVER-B:8093/synchrony-proxy/{R:1}" />
</rule>
<rule name="Confluence Context1 Rule" stopProcessing="true">
<match url="confluencewfm(.*)" />
<conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
<action type="Rewrite" url="http://SERVER-B:8093/confluencecontext1{R:1}" />
</rule>
<rule name="Jira context1 Rule" enabled="true" stopProcessing="true">
<match url="jirawfm(.*)" />
<conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
<action type="Rewrite" url="http://SERVER-C:8083/jiracontext1{R:1}" />
</rule>
<rule name="Confluence context2" stopProcessing="true">
<match url="confluenceenelgds(.*)" />
<conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
<action type="Rewrite" url="http://SERVER-B:8094/confluencecontext2{R:1}" />
</rule>
<rule name="Jira context2" stopProcessing="true">
<match url="jiraenelgds(.*)" />
<conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
<action type="Rewrite" url="http://SERVER-C:8080/jiracontext2{R:1}" />
</rule>

Since Confluence 6.x introduce collaborative editing, we have some problems to proxy it.
Using the direct to synchrony approach (https://confluence.atlassian.com/doc/administering-collaborative-editing-858772086.html), we are able to enter in editing mode in a page but we cannot save.
A warning in the bottom of the page say that the server is unreachable.
Using internal proxy all works fine.
We must declare the context path of internal synchrony proxy in IIS because we have multiple context path proxyed
by the same virtual hos.
The internal proxy context path isn’t customizable (is it true?), so at the moment we use collaborative editing in only one instance.
Where we are wrong in the configuration? How can we do?

Before using ARR and URL rewrite (before confluence 6.x) we use AJP protocol and ISAPI extension and all works fine.
Atlassian support say us that AJP is no longer supported on newest versions.

Going to Jira, we experiencing some problems creating new issue o editing existing issue if we operate from filters page.
If we create a new issue from homepage (dashboard) or from an issue page and if we edit an issue from its page all works fine.
From filters page start loading circle and never goes on.
We try to explicitly declare allowed PUT, DELETE and GET verbs in IIS but the problem persists.
If we try bypassing proxy all works fine.
With chrome developers tools we’ve fond that we receive a 400 Bad Request error from batch.js. here some screenshots.

Immagine 08_05_2017-15_43_06.pngImmagine 08_05_2017-15_43_50.png

 

Another problem is with "link issue" functionality. Linking issues remain in "loading" circle icon

Immagine 12_05_2017-10_52_45.pngImmagine 12_05_2017-10_54_28.png

Where is the problem?

Thanks in advance
Regards

1 answer

0 vote
Ann Worley Atlassian Team Jun 26, 2017

 

I am not sure what is causing the issue with JIRA behind IIS. If the Synchrony context path is causing IIS not to work with collaborative editing in Confluence, you may change it with the system property:

synchrony.context.path

Please see Configuring System Properties and Recognized System Properties.

 

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Kesha Thillainayagam
Posted Apr 13, 2018 in Confluence

We want to hear how your non-technical teams are using Confluence!

Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...

375 views 20 10
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you