Issue Summary

When custom domains are configured for both Jira and Confluence, once they are deactivated one by one, only the later deactivated Custom Domain can be accessed, and the first deactivated one can't.

Steps to Reproduce

1. Activate both Custom Domains for Jira and Confluence, both custom domains can be accessed
2. Deactivate Confluence Custom Domain first and then deactivate Jira Custom Domain, 
3. Reactivate both Custom Domains, both Custom Domains can be accessed
4. Deactivate the Jira Custom Domain first and then deactivate the Confluence Custom Domain

Expected Results

Both Custom Domains can be accessed in step 2 and step 4

Actual Results

• In step 2, accessing Confluence's custom domain will land on a "Page unavailable" screen, causing a 403 error. However, accessing the customer domain for Jira will redirect correctly to the cloud site.
• In step 4, Accessing Jira's custom domain will land on a "Page unavailable" screen, causing a 403 error. However, accessing the customer domain for Confluence will redirect correctly to the cloud site.

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available