---
title: "Errors accessing bindings page after Jira subdomain change"
canonical: "https://support.appfire.com/space/SUPPORT/3406856453/Errors%20accessing%20bindings%20page%20after%20Jira%20subdomain%20change"
format: markdown
---
## Summary

This article addresses an issue where users encounter errors when attempting to open the **Bindings** page in the Connector for Salesforce & Jira settings after changing their Jira instance subdomain (Cloud Site Rename). This occurs because the existing OAuth authorization between Jira and Salesforce is tied to the previous URL.

## Environment

- **Product:** Connector for Salesforce & Jira
- **Platform:** Jira Cloud
- **Feature:** Cloud Site Rename (Subdomain change)

## Problem

After renaming a Jira Cloud site (e.g., from `old-name.atlassian.net` to `new-name.atlassian.net`), navigating to the **Bindings** page results in errors or the page failing to load correctly.

### Symptoms

- Errors appear when trying to open the **Bindings** page.
- Synchronization between Jira and Salesforce may stop working.
- Connection status might show as unauthorized or fail to refresh.

## Cause

The Connector for Salesforce & Jira is compatible with the Cloud Site Rename feature; however, the connection relies on OAuth tokens that are specific to the instance URL. When the subdomain changes, the existing authorization becomes invalid, leading to errors when the app tries to retrieve binding data using the old credentials.

## Solution

To resolve this, please reach out to the support team to do the necessary updates. Related articles

- [https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3091597377](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3091597377)
- [https://appfire.atlassian.net/wiki/spaces/SUPPORT/pages/3268378662](https://appfire.atlassian.net/wiki/spaces/SUPPORT/pages/3268378662)

**Proposed labels:** `connector-for-salesforce-jira`, `cloud-site-rename`, `subdomain-change`, `bindings-error`, `troubleshooting`