Skip to content Skip to main navigation Skip to footer

Error Message: “Unable to login to your organization” or “Cannot Access Org”

Error Message may display as:
“Error: Unable to login to your organization”
“Error: Cannot login to your organization”
“Error: Can’t Access Org”
“Fax App could not update your Salesforce Org”
Or if you are unable to Grant Access and get a blank screen.

You may see this error message when trying to click the “Grant Access” button under Opero Fax Configuration tab to authorize the app. Please review the following steps to troubleshoot:

  • Check that the latest version of Opero Fax is installed: https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3000000B5FogEAF
  • Check that the user who granted access to Opero Fax is active, has an Administrator profile, and has the Fax Admin permission set assigned: https://kb.opero.com/fax/knowledge-base/basic-configuration/
  • If you had a recent Sandbox refresh, this changes the org Id and therefore could cause one of the above errors. You will need to contact support . Include a copy of the error details, provide the new Sandbox org Id, and any existing fax number you need moved over. Or inform Support that you no longer require a Sandbox org to be active and would like to cancel the additional fax line subscription as well as release Sandbox org fax line.
  •  Using Salesforce Professional Edition and do not have API enabled, which is a requirement to use Opero Fax. In this case, you can submit a request to Salesforce support to request for the API to be enabled and/or convert instance org to UE from PE. Or you can use any other Salesforce edition that already has API enabled out of the box.
  • If you have API enabled and API calls available and error continues, you may have some strict IP settings and need to modify them:
  • If you are restricting Login IP Ranges, you must allow connection of Azure app by whitelisting the following two (2) IP addresses: 
51.143.43.208
20.43.231.188
  • Session Settings must enable connection.
  • API Enabled must be enabled on Profile.
  • Go to Setup > Security Controls > Session Settings and UNCHECK following boxes:
  • “Lock sessions to the IP address from which they originated” (under Session Settings Section) and also uncheck the box.
  • “Enable Stricter Content Security Policy” (under Content Security Policy Prevention section).