Maintenance page for JIRA, Confluence at proxy level
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
Configure maintenance page for JIRA, Confluence, etc at proxy level during planned releases. You want to show the custom HTML page to users during release and at the same time allow admins/QA to access applications and don't break all existing application links.
Solution
Option1. Whitelist IP at proxy level. Allow connection from JIRA, Confluence, Stash, Fisheye/Crucible IP address to Apache Httpd, then add to this list your Admin/QA IPs. All other will be redirected to Maintenance landing page by mod_rewrite
Option2.
Before Maintenance
Configure additional VirtualHost with new IP at LB/proxy (IP2), use same SSL certificate, proxy to all required applications
Add this IP2 to hosts records at Admins/QA PC
Check that applications are accessible by them
Configure Whitelist IPs (from JIRA, Confluence etc IP address) for IP1 to allow communication between application.
During Maintenance
All requests will be temporally redirected to maintenance page.
Access applications though IP2
Revert configuration changes for IP1
Was this helpful?