Users are not able to connect to GlobalProtect with the error message: "Could not connect to the GlobalProtect service."
854
Created On 12/02/25 17:01 PM - Last Modified 01/02/26 21:45 PM
Symptom
- Unable to connect to GlobalProtect Portal/Gateway
- GlobalProtect App GUI shows the intermittent errors listed below.
- Could not connect to the GlobalProtect service
- Gateway <GW name>: The network connection is unreachable, or the gateway is unresponsive. Check the network connection and reconnect.
- PanGPS logs show the connection failing at the portal or gateway pre-login, with error the message.
(P7512-T7760)Debug(3731): 12/01/25 10:11:41:639 ----Gateway Pre-login starts----
(P7512-T7760)Debug(14013): 12/01/25 10:11:41:639 Check cert of server 192.168.1.100
(P7512-T7760)Info ( 166): 12/01/25 10:11:41:640 SSL_CTX_new() failed: error retrieving entropy
(P7512-T7760)Debug(14028): 12/01/25 10:11:41:640 File C:\Program Files\Palo Alto Networks\GlobalProtect\tca.cer does not exist.
(P7512-T7760)Debug( 939): 12/01/25 10:11:41:640 SSL connecting to 192.168.1.100
(P7512-T7760)Debug( 584): 12/01/25 10:11:41:670 Network is reachable
(P7512-T7760)Error( 449): 12/01/25 10:11:41:694 Server error: Create SSL context failed
(P7512-T7760)Debug( 956): 12/01/25 10:11:41:694 connect() failed
(P7512-T7760)Error(14060): 12/01/25 10:11:41:694 ConnectSSL: Failed to connect to '192.168.1.100:443'. Disconnect ssl.
(P7512-T7760)Debug(14111): 12/01/25 10:11:41:694 Cannot get server cert of 192.168.1.100
(P7512-T7760)Debug(6870): 12/01/25 10:11:41:694 Already tried both ipv4 and ipv6 for gateway test-vpngw.com
(P7512-T7760)Error(3817): 12/01/25 10:11:41:694 Failed to connect to gateway test-vpngw.com.
(P7512-T7760)Debug(6197): 12/01/25 10:11:41:695 Show Gateway Testvpn-GW: The network connection is unreachable or the gateway is unresponsive. Check the network connection and reconnect.
Environment
- PAN-OS
- AMD64 Family Processors
- GlobalProtect Gateway
- GlobalProtect Portal
Cause
Software Issue.
Resolution
- The issue is resolved under GPC-24048
- Upgrading to the fixed versions of 6.3.3-h4 (6.3.3-c828) and 6.2.8-h5 (6.2.8-c416) will resolve the issue.