Reconnect your Git Provider

CloudCannon syncs your Sites using the account connected to your Git Provider. If your Git Provider revokes CloudCannon's access, or CloudCannon cannot fetch information about your connected account, CloudCannon may not be able to sync the Sites that use that Git Provider. The Authentication tab on the Git Provider's page under Org Settings shows an error message and a Reconnect button.

Access to a Git Provider applies to your whole Organization, so retrying an individual Site will not resolve the problem. You can reconnect your Git Provider without unauthenticating it first.

To reconnect your Git Provider:

1. Click the Org Settings button in the App Sidebar. CloudCannon will open the Details page.
2. Navigate to the page for your Git Provider under the Files heading.
3. Click the Reconnect button on the Authentication tab.
4. Sign in to your Git Provider as the account already connected to your Organization.
5. Follow your Git Provider's instructions to authenticate access.

CloudCannon will return you to the Authentication tab and show your connected account. Any Sites that failed to sync while CloudCannon could not access your Git Provider will sync again when you retry them. For more information, please read our documentation on resolving Syncing errors.

Change the connected account or token#

For GitHub, GitLab, and Bitbucket, CloudCannon will show an error message instead of reconnecting if you sign in as a different account. To connect a different account, unauthenticate your Git Provider first, then authenticate it with the new account. For more information, please read our documentation on unauthenticating your Git Provider.

For GitHub Enterprise Server and self-hosted GitLab, CloudCannon reconnects with whichever account you sign in as, and that account replaces the one already connected.

If you authenticated GitLab or self-hosted GitLab with a group access token, you cannot renew your token with the Reconnect button. For GitLab, CloudCannon treats the GitLab user account you sign in with as a different account and will not reconnect it. For self-hosted GitLab, reconnecting replaces your token with the user account you sign in with. To replace an expired or revoked token, unauthenticate your Git Provider, then authenticate again with a new token.