Get Started Free 
Resolving Salesforce Login Issues Caused by IP Restrictions
Who this affects
If you're unable to log in to Salesforce from a Xappex product (XL-Connector, XL-Connector 365, G-Connector, or Xappex CRM) and your Salesforce org uses IP range restrictions, this article explains why the login fails and how to fix it. Common symptoms include:
-
Login fails with an error such as “Your login attempt has been blocked” or a generic authentication error
-
Login works from your office network but fails through the Xappex product
-
Logins stopped working after updating to the latest version of a Xappex product
Why this happens
Our updated login flow is server-based: the OAuth authentication request is processed through Xappex servers rather than directly from your local machine. This change is part of the security improvements required by Salesforce for all partner applications (PKCE, refresh token rotation, and related settings). If your Salesforce org restricts logins to specific IP ranges — either at the profile level or in the connected app policies — Salesforce will block the authentication request because it originates from a Xappex server IP that isn't on your allowlist. How to fix it Ask your Salesforce administrator to add the following Xappex server IP addresses to your org's trusted IP ranges:
-
54.187.178.73
-
100.20.136.27
-
184.34.3.225
Where to add them
-
Option 1 — Network Access (org-wide trusted IPs): In Salesforce Setup, enter Network Access in the Quick Find box, click New for each IP address Enter the IP in both the Start IP Address and End IP Address fields. Save.
-
Option 2 — Profile-level IP restrictions: If your org restricts login IPs on user profiles: In Setup, go to Profiles and select the affected user’s profile Under Login IP Ranges, click New, Add each IP above as both the start and end of the range Save If your org uses both, the IPs need to be permitted in each place where restrictions are enforced.
After whitelisting
Once the IPs are added, try logging in again from the Xappex product. No reinstall is needed — simply retry the connection.
Still having trouble?
If login still fails after whitelisting the IPs, contact our support team and include:
-
The product and version you’re using
-
A screenshot of the error message
-
Whether your org uses Login IP Ranges on profiles, Network Access restrictions, or both.
