Skip to main content
All CollectionsTroubleshooting & FAQs
Error re-authorizing sandbox in the Essentials Organizations tab
Error re-authorizing sandbox in the Essentials Organizations tab

Troubleshooting tips for resolving organization re-authorization error in the Essentials Organizations tab.

David Belove avatar
Written by David Belove
Updated over 2 weeks ago

If you are having trouble re-authorizing a sandbox in the Essentials Organizations tab this could be related to a Salesforce outage. Several times over the past year, Essentials users have reported that they can't re-authorize a sandbox from the Essentials Organizations tab.

The error message says: "It looks like the login user profile you have just used is currently IP restricted. In order for Copado to manage your deployments please modify your Salesforce user profile to show access from ip address 52.53.143.65." (See screenshot below.)
​

Potential Root Causes

There are two known reasons for this error.
​
1) The Essentials user has refreshed their sandbox during a Salesforce outage and their sandbox has been corrupted. Refreshing the sandbox fixes the issue.
​
Here are a few questions to ask:

  • Does the same thing happen when logging into this sandbox from Workbench or another third-party app?

  • Is the sandbox configured properly for Essentials--is our IP added to the profile or trusted network access list? Are they logging in with a Systems Admin profile?

  • Has there been a recent Salesforce outage (confirm at status.salesforce.com)?

  • Have they refreshed this sandbox recently?

  • Have they ever been able to log into this sandbox from Essentials?

If the answer to all of these question is yes, it is probably due to refreshing their sandbox during an Salesforce outage and the API connection has been corrupted.

2) The your org is undergoing Hyperforce migration, which interferes with access to the org via third-party apps like Essentials. One Essentials customer received this response from Salesforce Support:

"Upon checking with our internal team, we have identified that this is a replication issue. It was observed that the Hyperforce migration was completed on 20/11/2024 at 12:59 PM. Please note that it may take some time for the application to fully stabilize, as replication needs to propagate across the system."

For more information you may want to contact Salesforce Support.

Did this answer your question?