IP access control: your IP address is not allowed

Your current IP address or network range is not included in the instance's IP Access Control List (ACL) configuration. (high likelihood)

Recent VPN connection changes have altered your public IP address to one outside the approved IP ranges. (high likelihood)

Network infrastructure changes such as datacenter migrations, ISP changes, or new proxy servers have changed your originating IP address. (medium likelihood)

IP Access Control is enabled but no IP ranges have been properly configured, blocking all access except from localhost. (medium likelihood)

ServiceNow is incorrectly detecting your IP address due to proxy headers or load balancer configuration issues. (low likelihood)

Step 1: Identify your current public IP address by visiting whatismyipaddress.com or using the command 'curl ifconfig.me' from your terminal.

Step 2: Contact your ServiceNow administrator to check if IP Access Control is enabled by navigating to System Security > IP Address Access Control in the instance.

Step 3: Have the administrator review the IP Access Control table (sys_ip_access_control) to verify if your IP address or CIDR range is listed and active.

Step 4: If your IP is missing, request the administrator to add a new IP Access Control rule with your current IP address or appropriate CIDR range (e.g., 192.168.1.0/24).

Step 5: Verify the new rule is active by checking the 'Active' checkbox and ensuring the 'Type' field is set to 'Allow' in the IP Access Control record.

Step 6: Clear your browser cache and cookies for the ServiceNow instance, then attempt to access the instance again after the rule is saved.

Step 7: If the error persists, check the System Log at System Diagnostics > Logs > System Log for additional IP access control entries that may provide more specific error details.

Step 8: As a temporary workaround, administrators can disable IP Access Control by setting the system property 'glide.security.use_ip_access_control' to false, though this reduces security.