Login Loop when running Bamboo behind a reverse proxy
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After switching Bamboo to work with a reverse proxy users cannot log in, Bamboo keeps redirecting to the All plans page.
Environment
Bamboo running behind a reverse proxy
Cause
Cause 1: Unsupported browser
Bamboo is being accessed via internet explorer, as this is not a supported Web Browser, it might cause unexpected behaviours.
Cause 2: Incomplete reverse proxy configuration
To prevent users from being tricked into unintentionally submitting malicious data, Bamboo uses XSRF security protection. Which blocks any requests from a different origin than the one configured in Bamboo, this security feature can be responsible for causing this behaviour when, for example, the Bamboo base URL is not correct or the proxy configuration on the server.xml file is not configured properly.
Solution
Solution 1: Use a different browser
Access Bamboo using one of the supported Web browsers, listed on:
Solution 2: Adjust reverse proxy configuration
To check the base URL follow the steps below:
Navigate to <Bamboo home>/xml-data/configuration, or <Bamboo shared home>/configuration if running Bamboo 8;
Open administration.xml file;
Check if <myBaseUrl> is pointing to the same URL being used;
If it's not, change it and restart Bamboo.
For the server.xml file, we have two Knowledge base articles with an example configuration for Nginx and Apache. We need to check to make sure secure, scheme, proxyName, and proxyPort were added to the connector and are pointing to the correct port and FQDN.
Was this helpful?