Why does the "site not enabled" error occur in Salesforce?

Problem Statement

When you create a Chargebee Quote from an Opportunity, or run any Chargebee action in your Salesforce dashboard, you see a site not enabled error. The same error can appear in the Chargebee CB Logs in Salesforce.

Related Scenarios

• Encountering a "site not enabled" error when creating a Chargebee Quote from an Opportunity in Salesforce.
• Understanding sandbox site expiration and its impact on testing in Salesforce UAT environments.
• Seeing the "site not enabled" error in the Salesforce CB Logs.

Solution

The error occurs when the Chargebee site linked to your Salesforce integration no longer has the integration enabled — most often because the linked site is an expired Chargebee sandbox.

Additional sandbox sites are active for 90 days from creation. During the last 45 days of that period you can extend the expiry, and after a sandbox expires you can activate it again from the Sandbox Sites table. For details, see Retention and expiry of sandbox sites.

To resolve the error and continue testing:

1. Verify the Chargebee site status. Confirm the Chargebee site is active and that you can access it. If it is a sandbox site, confirm that it has not expired.
2. Switch to your primary test site. Your primary test site does not expire and is suited to ongoing development. Point your Salesforce integration to the primary test site, and update any references in your Salesforce setup to use it.
3. Re-enable the integration. Contact Chargebee Support to re-enable the integration on your site.

Important Notes

• Sandbox expiry: Additional sandbox sites are active for 90 days. You can extend the expiry during the last 45 days, and reactivate an expired sandbox from the Sandbox Sites table.
• Primary test site: Use the primary test site for long-term testing, as it does not expire.
• Integration settings: Keep your Salesforce integration pointed at an active Chargebee site to avoid the error.