Proxying Atlassian server applications with NGinx

Cédric VASSEUR December 18, 2017

Hi all, 

I tried to install Jira, Confluence and BitBucket behind a reverse proxy (Nginx)
The installation works without reverse proxy, but when I activate the reverse proxy by following tutorials,

https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html
and
https://confluence.atlassian.com/jirakb/integrating-jira-with-nginx-426115340.html

I have the following problem:

BitBucket:
Display problem, screens do not display images, javascripts, etc.
Confluence:
I have a Warning: Can not check base URL
And for Jira:
Project creation: XSRF check fail

Can you tell me where it could come from ?
Thank you

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 19, 2017

For confluence: That error is an indication that the confluence application can not reach the URL that the base URL is set to.  This is a requirement that the application be able to reach the network address of the base URL.  Some older versions of Jira/confluence could work without this requirement, but all recent versions need to allow the application itself to reach that own base url over the network.   You want to make sure that both the server Confluence is running on, and the confluence application itself can reach the network address that this base url is set to.   Jira also has the same requirement.

The Jira XSRF, is an indication that the proxy is redirecting traffic to Jira, but Jira is not aware of this.  You will want to check on the $JIRAINSTALL/conf/server.xml and make sure that you have included the proxyName, proxyPort, and scheme parameters in the connector that is being used to serve up content to that proxy.   If these don't exist, or are incorrectly set, I would expect Jira to throw this kind of error.   Please note that if you have to make changes to server.xml, after you save that file, you need to restart Jira for this change to take effect.

As for bitbucket, I'm not really an expert for this application, but I suspect it could be a combination of both of these other problems seen by Jira and Confluence.

Suggest an answer

Log in or Sign up to answer