- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
11-17-2026 09:20 AM - edited 11-17-2026 09:25 AM
Hello, LiveCommunity team!
I have created this post to share my experience with a GlobalProtect issue affecting some users in Uruguay, who are unable to connect to GlobalProtect deployed across Prisma Access locations (India West, US NorthWest, Chile)—even with the app configuration (App-Setting) adjusted to set the source region to "ANY"!!
Mobile Users in Uruguay attempting to connect to GlobalProtect are experiencing VPN issues, in response to which the GlobalProtect agent displays the error message: "The network connection is unreachable or the gateway is unresponsive. Check the network connection and reconnect." as shown below:
Uruguay's Mobile User GlobalProtect Agent Error Message
Even in the Prisma Access GlobalProtect application configuration settings, we set the "Source Region" to "ANY," but the issue with the VPN persists.:
Prisma Access GlobalProtect App-Setting > External Gateways
However, other Mobile Users in various countries are able to establish the VPN agent connection with Prisma Access GlobalProtect without any issues.
This is the Prisma Access GlobalProtect topology:
Palo Alto Prisma Access GlobalProtect Topology
In the following section, I will share the troubleshooting steps, workarounds, and the root cause analysis (RCA).
Best Regards,
Daniel Romero
Senior Network/Security Engineer
PANW Partner
YouTube: @DanielRomeroNetSecurity
11-17-2026 04:11 PM - edited 11-17-2026 04:20 PM
Hello, LiveCommunity team!
I share the troubleshooting, workarounds, and the root cause analysis (RCA) of this particular Prisma Access GlobalProtect issue, where mobile users in Uruguay cannot connect to the gateways deployed in (India West, US NorthWest, Chile) even with the app configuration (App-Setting) adjusted to set the source region to "ANY"!!
Troubleshooting Steps
1- To verify the actual underlying issue, we ask the user to generate the GlobalProtect agent logs with dump level.
2- On the PanGPS.log file we see the next messages where the GlobalProtect agent make a IP-to-Region Mapping based on the user's source public IP address to connect to the faster Gateway first on the same Region.
GLOBALPROTECT PANGPS.LOG
(P4420-T3332)Debug(9214): 11/13/26 22:56:51:677 REGION-PRIO, region code is UY
(P4420-T3332)Debug(17171): 11/13/26 22:56:51:677 REGION-PRIO, save region code UY
(P4420-T3332)Debug( 407): 11/13/26 22:57:00:229 REGION-PRIO, no match at all, error
(P4420-T3332)Debug( 407): 11/13/26 22:57:00:229 REGION-PRIO, no match at all, error
(P4420-T9440)Debug( 724): 11/13/26 22:57:02:505 gateway 0 of india-west-centrode.123123123.gw.gpcloudservice.com is manual select only, will not be in rediscover list
(P4420-T9440)Debug( 691): 11/13/26 22:57:02:505 REGION-PRIO, gateway 1 is not selectable base on region
(P4420-T9440)Debug( 691): 11/13/26 22:57:02:505 REGION-PRIO, gateway 2 is not selectable base on region
(P4420-T9440)Debug( 759): 11/13/26 22:57:02:505 There is no gateway suitable to discovery
(P4420-T9440)Error(7835): 11/13/26 22:57:02:505 NetworkDiscoverThread: failed to discover external network.
(P4420-T9440)Debug(7859): 11/13/26 22:57:02:505 Network discovery failed, set error as The network connection is unreachable or the gateway is unresponsive. Check the network connection and reconnect.
(P4420-T9440)Debug(8931): 11/13/26 22:57:02:505 --Set state to Disconnected
We see GlobalProtect assign a priority -2 for the Gateways available at India West, US Northeast and Chile, it means the GP agent will never try to connect to that Gateways, as shown below:
INDIA WEST GATEWAYS REGION MATCHING AND PRIORITY
(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 REGION-PRIO, after search for exact region match, i=10, m_nRegions=10
(P4420-T3332)Dump ( 390): 11/13/26 23:47:19:927 REGION-PRIO, no exact match, search for ANY
(P4420-T3332)Debug( 407): 11/13/26 23:47:19:927 REGION-PRIO, no match at all, error
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority -2, bManual=0
US NORTHWEST GATEWAYS REGION MATCHING AND PRIORITY
(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 REGION-PRIO, after search for exact region match, i=16, m_nRegions=16
(P4420-T3332)Dump ( 390): 11/13/26 23:47:19:927 REGION-PRIO, no exact match, search for ANY
(P4420-T3332)Debug( 407): 11/13/26 23:47:19:927 REGION-PRIO, no match at all, error
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority -2, bManual=0
CHILE GATEWAYS REGION MATCHING AND PRIORITY
(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 REGION-PRIO, after search for exact region match, i=4, m_nRegions=4
(P4420-T3332)Dump ( 390): 11/13/26 23:47:19:927 REGION-PRIO, no exact match, search for ANY
(P4420-T3332)Debug( 407): 11/13/26 23:47:19:927 REGION-PRIO, no match at all, error
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority -2, bManual=0
Root Cause Analysis (RCA)
Based on these logs, we know that the GP agent evaluates whether the user's region Uruguay (UY) matches the available regions implemented/supported at each Prisma Access location (India West, US Northwest, and Chile); however, none of these locations include a region that matches with the user's region Uruguay (UY).
Even if the source region is set to "ANY" in the App-Setting rule, the issue persists; this is because there is an underlying list of regions ("countries") available for each Prisma Access location. If the actual user's source region does not match any of the regions available in that list for a given Prisma Access location, the GlobalProtect (GP) agent assigns a default priority of -2 to prevent the use of those Gateways.
GLOBALPROTECT REGION PRIORITY TABLE
Palo Alto Networks Prisma Access offers over 100 locations across 76 countries to accommodate worldwide deployments and provide a localized experience. These regions and locations are dynamically updated.
This entire design addresses issues of performance, redundancy, and internal considerations. These underlying lists are dynamic and can be updated.
Palo Alto Networks strongly recommends enabling at least one of the regional and global fallback locations during mobile user onboarding for redundancy in case the in-country location becomes unavailable.
Source: Securing Internet Access for Mobile Users by Using Tunnel Mode: Design Guide - Palo Alto Networks
Solution and Workarounds
As a solution we must deployed a new Prisma Access Location at Uruguay, then the GP agent was able to connect to the Uruguay Gateway!!
PRISMA ACCESS GLOBALPROTECT ENABLE NEW URUGUAY LOCATION
Note: After we enable the new Uruguay location we need to activate the new Egress IPs and push the configuration to the changes take effect!!
After this, the PanGPS.log file shows the underlying list with the exact region Uruguay UY available for the Uruguay users!
GLOBALPROTECT PANGPS.LOG
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority -2, bManual=0
(P4420-T3332)Dump ( 886): 11/13/26 23:47:19:927 REGION-PRIO, found new tag, we use new logic
(P4420-T3332)Dump ( 899): 11/13/26 23:47:19:927 REGION-PRIO, gateway 3(Uruguay), 0, region = UY, priority = 1, portalRegion=UY
(P4420-T3332)Dump ( 909): 11/13/26 23:47:19:927 REGION-PRIO, get configuration base on region, region code=UY
(P4420-T3332)Dump ( 355): 11/13/26 23:47:19:927 REGION-PRIO, regionCode=UY
(P4420-T3332)Dump ( 380): 11/13/26 23:47:19:927 REGION-PRIO, i = 0, region code=UY, region=UY
(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 REGION-PRIO, after search for exact region match, i=0, m_nRegions=1
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority 1, bManual=0
(P4420-T17000)Dump (6604): 11/13/26 23:47:20:549 gateway chile-centrode.123456.gw.gpcloudservice.com priority is 1
(P4420-T17000)Dump ( 703): 11/13/26 23:47:20:549 pg, pg is , gateway ip is chile-centrode.123456.gw.gpcloudservice.com, remotehoststr=NULL, remotehoststrv6=, prefergatewaysource=0, isprelogonInProcess is 0
(P4420-T17000)Dump ( 741): 11/13/26 23:47:20:549 start the 0 thread for gateway chile-centrode.123456.gw.gpcloudservice.com
(P4420-T4884)Dump (6030): 11/13/26 23:47:20:549 Process gateway: host chile-centrode.123456.gw.gpcloudservice.com, description Uruguay
(P4420-T17000)Dump (1289): 11/13/26 23:47:20:732 ignore gateway india-west-centrode.123123123.gw.gpcloudservice.com, duration time is 0xFFFFFFFF, priority=-2
(P4420-T17000)Dump (1289): 11/13/26 23:47:20:732 ignore gateway us-east-g-centrode.123123123.gw.gpcloudservice.com, duration time is 0xFFFFFFFF, priority=-2
(P4420-T17000)Dump (1289): 11/13/26 23:47:20:732 ignore gateway chile-centrode.123123123.gw.gpcloudservice.com, duration time is 0xFFFFFFFF, priority=-2
(P4420-T17000)Dump (6604): 11/13/26 23:47:20:732 gateway chile-centrode.123456.gw.gpcloudservice.com priority is 1
(P4420-T17000)Dump (1306): 11/13/26 23:47:20:732 REGION-PRIO, gateway chile-centrode.123456.gw.gpcloudservice.com get priority 1 for region
(P4420-T17000)Debug(1430): 11/13/26 23:47:20:732 gateway Uruguay (chile-centrode.123456.gw.gpcloudservice.com), priority=1, duration=80 ms, assign 20 as its weight
(P4420-T17000)Info (1469): 11/13/26 23:47:20:732 CPanGatewayList::PickGatewayBaseOnWeight, PAN_NEW_GATEWAY_SELECTOR, chose prefered gateway index =3, gateway is Uruguay
(P4420-T17000)Debug(4064): 11/13/26 23:47:21:737 REGION-PRIO, gateway region code is UY
(P4420-T17000)Debug(4096): 11/13/26 23:47:21:737 REGION-PRIO, portal and gateway have same region code
Palo Alto Prisma Access GlobalProtect Topology New Uruguay Location
Possible Workaround
Additionally, as an alternative solution if deploy a new Prisma Access Location it's not possible, by adding the source user "Uruguay (UY)" explicitly as a source region within the application setting rules (App-Setting), alongside "gpcloudservice.com" or a specific Gateway FQDN it appears that this force the underlying list to permit the users to connect to those Gateways. (We need to test it to confirm this workaround) 😁
The App-Setting rules that include more specific source regions take precedence over a rule with source region defined as "ANY".
Prisma Access GlobalProtect App-Setting > External Gateways
If the rule in the application settings is defined with the origin region set to "ANY," this implies that the selection of the region or gateway location will be based on the dynamic underlying list of supported/available regions of each location.
If you have any questions or comments, let me know in the comments section!
Thank you for your time, and I hope this information is helpful in your daily cybersecurity work. I would greatly appreciate your support by liking or accepting this as a useful post; it would help me a lot in becoming a CyberElite!
Best Regards,
Daniel Romero
Senior Network/Security Engineer
PANW Partner
YouTube: @DanielRomeroNetSecurity
11-17-2026 04:11 PM - edited 11-17-2026 04:20 PM
Hello, LiveCommunity team!
I share the troubleshooting, workarounds, and the root cause analysis (RCA) of this particular Prisma Access GlobalProtect issue, where mobile users in Uruguay cannot connect to the gateways deployed in (India West, US NorthWest, Chile) even with the app configuration (App-Setting) adjusted to set the source region to "ANY"!!
Troubleshooting Steps
1- To verify the actual underlying issue, we ask the user to generate the GlobalProtect agent logs with dump level.
2- On the PanGPS.log file we see the next messages where the GlobalProtect agent make a IP-to-Region Mapping based on the user's source public IP address to connect to the faster Gateway first on the same Region.
GLOBALPROTECT PANGPS.LOG
(P4420-T3332)Debug(9214): 11/13/26 22:56:51:677 REGION-PRIO, region code is UY
(P4420-T3332)Debug(17171): 11/13/26 22:56:51:677 REGION-PRIO, save region code UY
(P4420-T3332)Debug( 407): 11/13/26 22:57:00:229 REGION-PRIO, no match at all, error
(P4420-T3332)Debug( 407): 11/13/26 22:57:00:229 REGION-PRIO, no match at all, error
(P4420-T9440)Debug( 724): 11/13/26 22:57:02:505 gateway 0 of india-west-centrode.123123123.gw.gpcloudservice.com is manual select only, will not be in rediscover list
(P4420-T9440)Debug( 691): 11/13/26 22:57:02:505 REGION-PRIO, gateway 1 is not selectable base on region
(P4420-T9440)Debug( 691): 11/13/26 22:57:02:505 REGION-PRIO, gateway 2 is not selectable base on region
(P4420-T9440)Debug( 759): 11/13/26 22:57:02:505 There is no gateway suitable to discovery
(P4420-T9440)Error(7835): 11/13/26 22:57:02:505 NetworkDiscoverThread: failed to discover external network.
(P4420-T9440)Debug(7859): 11/13/26 22:57:02:505 Network discovery failed, set error as The network connection is unreachable or the gateway is unresponsive. Check the network connection and reconnect.
(P4420-T9440)Debug(8931): 11/13/26 22:57:02:505 --Set state to Disconnected
We see GlobalProtect assign a priority -2 for the Gateways available at India West, US Northeast and Chile, it means the GP agent will never try to connect to that Gateways, as shown below:
INDIA WEST GATEWAYS REGION MATCHING AND PRIORITY
(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 REGION-PRIO, after search for exact region match, i=10, m_nRegions=10
(P4420-T3332)Dump ( 390): 11/13/26 23:47:19:927 REGION-PRIO, no exact match, search for ANY
(P4420-T3332)Debug( 407): 11/13/26 23:47:19:927 REGION-PRIO, no match at all, error
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority -2, bManual=0
US NORTHWEST GATEWAYS REGION MATCHING AND PRIORITY
(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 REGION-PRIO, after search for exact region match, i=16, m_nRegions=16
(P4420-T3332)Dump ( 390): 11/13/26 23:47:19:927 REGION-PRIO, no exact match, search for ANY
(P4420-T3332)Debug( 407): 11/13/26 23:47:19:927 REGION-PRIO, no match at all, error
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority -2, bManual=0
CHILE GATEWAYS REGION MATCHING AND PRIORITY
(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 REGION-PRIO, after search for exact region match, i=4, m_nRegions=4
(P4420-T3332)Dump ( 390): 11/13/26 23:47:19:927 REGION-PRIO, no exact match, search for ANY
(P4420-T3332)Debug( 407): 11/13/26 23:47:19:927 REGION-PRIO, no match at all, error
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority -2, bManual=0
Root Cause Analysis (RCA)
Based on these logs, we know that the GP agent evaluates whether the user's region Uruguay (UY) matches the available regions implemented/supported at each Prisma Access location (India West, US Northwest, and Chile); however, none of these locations include a region that matches with the user's region Uruguay (UY).
Even if the source region is set to "ANY" in the App-Setting rule, the issue persists; this is because there is an underlying list of regions ("countries") available for each Prisma Access location. If the actual user's source region does not match any of the regions available in that list for a given Prisma Access location, the GlobalProtect (GP) agent assigns a default priority of -2 to prevent the use of those Gateways.
GLOBALPROTECT REGION PRIORITY TABLE
Palo Alto Networks Prisma Access offers over 100 locations across 76 countries to accommodate worldwide deployments and provide a localized experience. These regions and locations are dynamically updated.
This entire design addresses issues of performance, redundancy, and internal considerations. These underlying lists are dynamic and can be updated.
Palo Alto Networks strongly recommends enabling at least one of the regional and global fallback locations during mobile user onboarding for redundancy in case the in-country location becomes unavailable.
Source: Securing Internet Access for Mobile Users by Using Tunnel Mode: Design Guide - Palo Alto Networks
Solution and Workarounds
As a solution we must deployed a new Prisma Access Location at Uruguay, then the GP agent was able to connect to the Uruguay Gateway!!
PRISMA ACCESS GLOBALPROTECT ENABLE NEW URUGUAY LOCATION
Note: After we enable the new Uruguay location we need to activate the new Egress IPs and push the configuration to the changes take effect!!
After this, the PanGPS.log file shows the underlying list with the exact region Uruguay UY available for the Uruguay users!
GLOBALPROTECT PANGPS.LOG
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority -2, bManual=0
(P4420-T3332)Dump ( 886): 11/13/26 23:47:19:927 REGION-PRIO, found new tag, we use new logic
(P4420-T3332)Dump ( 899): 11/13/26 23:47:19:927 REGION-PRIO, gateway 3(Uruguay), 0, region = UY, priority = 1, portalRegion=UY
(P4420-T3332)Dump ( 909): 11/13/26 23:47:19:927 REGION-PRIO, get configuration base on region, region code=UY
(P4420-T3332)Dump ( 355): 11/13/26 23:47:19:927 REGION-PRIO, regionCode=UY
(P4420-T3332)Dump ( 380): 11/13/26 23:47:19:927 REGION-PRIO, i = 0, region code=UY, region=UY
(P4420-T3332)Dump ( 386): 11/13/26 23:47:19:927 REGION-PRIO, after search for exact region match, i=0, m_nRegions=1
(P4420-T3332)Dump ( 429): 11/13/26 23:47:19:927 REGION-PRIO, regioncode=UY, return priority 1, bManual=0
(P4420-T17000)Dump (6604): 11/13/26 23:47:20:549 gateway chile-centrode.123456.gw.gpcloudservice.com priority is 1
(P4420-T17000)Dump ( 703): 11/13/26 23:47:20:549 pg, pg is , gateway ip is chile-centrode.123456.gw.gpcloudservice.com, remotehoststr=NULL, remotehoststrv6=, prefergatewaysource=0, isprelogonInProcess is 0
(P4420-T17000)Dump ( 741): 11/13/26 23:47:20:549 start the 0 thread for gateway chile-centrode.123456.gw.gpcloudservice.com
(P4420-T4884)Dump (6030): 11/13/26 23:47:20:549 Process gateway: host chile-centrode.123456.gw.gpcloudservice.com, description Uruguay
(P4420-T17000)Dump (1289): 11/13/26 23:47:20:732 ignore gateway india-west-centrode.123123123.gw.gpcloudservice.com, duration time is 0xFFFFFFFF, priority=-2
(P4420-T17000)Dump (1289): 11/13/26 23:47:20:732 ignore gateway us-east-g-centrode.123123123.gw.gpcloudservice.com, duration time is 0xFFFFFFFF, priority=-2
(P4420-T17000)Dump (1289): 11/13/26 23:47:20:732 ignore gateway chile-centrode.123123123.gw.gpcloudservice.com, duration time is 0xFFFFFFFF, priority=-2
(P4420-T17000)Dump (6604): 11/13/26 23:47:20:732 gateway chile-centrode.123456.gw.gpcloudservice.com priority is 1
(P4420-T17000)Dump (1306): 11/13/26 23:47:20:732 REGION-PRIO, gateway chile-centrode.123456.gw.gpcloudservice.com get priority 1 for region
(P4420-T17000)Debug(1430): 11/13/26 23:47:20:732 gateway Uruguay (chile-centrode.123456.gw.gpcloudservice.com), priority=1, duration=80 ms, assign 20 as its weight
(P4420-T17000)Info (1469): 11/13/26 23:47:20:732 CPanGatewayList::PickGatewayBaseOnWeight, PAN_NEW_GATEWAY_SELECTOR, chose prefered gateway index =3, gateway is Uruguay
(P4420-T17000)Debug(4064): 11/13/26 23:47:21:737 REGION-PRIO, gateway region code is UY
(P4420-T17000)Debug(4096): 11/13/26 23:47:21:737 REGION-PRIO, portal and gateway have same region code
Palo Alto Prisma Access GlobalProtect Topology New Uruguay Location
Possible Workaround
Additionally, as an alternative solution if deploy a new Prisma Access Location it's not possible, by adding the source user "Uruguay (UY)" explicitly as a source region within the application setting rules (App-Setting), alongside "gpcloudservice.com" or a specific Gateway FQDN it appears that this force the underlying list to permit the users to connect to those Gateways. (We need to test it to confirm this workaround) 😁
The App-Setting rules that include more specific source regions take precedence over a rule with source region defined as "ANY".
Prisma Access GlobalProtect App-Setting > External Gateways
If the rule in the application settings is defined with the origin region set to "ANY," this implies that the selection of the region or gateway location will be based on the dynamic underlying list of supported/available regions of each location.
If you have any questions or comments, let me know in the comments section!
Thank you for your time, and I hope this information is helpful in your daily cybersecurity work. I would greatly appreciate your support by liking or accepting this as a useful post; it would help me a lot in becoming a CyberElite!
Best Regards,
Daniel Romero
Senior Network/Security Engineer
PANW Partner
YouTube: @DanielRomeroNetSecurity
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

