---
type: Known
product: GlobalProtect
version: 6.2.8-h6
---

## GPC-24931

When GlobalProtect app has Enforcer and endpoint traffic policy enforcement enabled, it may fail to connect after a Wi-Fi switch, manual gateway change, or machine reboot. The error message "Could not connect to the authentication server," is displayed even when the device has an active internet connection. Disconnecting the GlobalProtect connection allows browsing, but attempting to reconnect immediately redirects to embedded browser Security Assertion Markup Language (SAML) authentication, which then displays the "Can't reach auth server" error.

## GPC-24922

After waking up from modern standby, the GlobalProtect app may get stuck at finding the best available gateway. Disconnecting and reconnecting does not resolve the issue, even though the portal FQDN is reachable.

## GPC-24842

(macOS only) GlobalProtect crashes when you click **Change Portal** on setups that include two or more portal entries and have a preferred gateway marked. This issue can corrupt the NSUserDefaults plist file leading to subsequent crashes.

**Workaround**: Do one of the following:

- Reinstall GlobalProtect.
- Remove the corrupted plist file located at ~/Library/Preferences/com.paloaltonetworks.GlobalProtect.client.plist.
- Remove portal entries only from the plist file using the following steps:
  1. $ launchctl unload -S Aqua /Library/LaunchAgents/com.paloaltonetworks.gp.pangpa.plist
  2. $ defaults delete com.paloaltonetworks.GlobalProtect.client PanPortalList
  3. killall cfprefsd
  4. launchctl load -S Aqua /Library/LaunchAgents/com.paloaltonetworks.gp.pangpa.plist
