topic Re: Global Protect connection Failed could not verify the server certificate of the gateway in GlobalProtect Discussions

Global Protect connection Failed could not verify the server certificate of the gateway

EliyaDafna — Mon, 13 Jun 2022 14:27:08 GMT

Hi,

I set up a VPN connection according to the guide and after entering a username and password I get the following error:

" global protect connection Failed could not verify the server certificate of the gateway"
I did not find anything on the Internet, can anything help?

Re: Global Protect connection Failed could not verify the server certificate of the gateway

BPry — Mon, 13 Jun 2022 14:40:01 GMT

@EliyaDafna,

Did you setup a valid certificate on your GlobalProtect Portal and Gateway that would be trusted by your client? Seems like you may have missed that step. If you're just doing this to test things out before a full deployment, you can always use a self-signed certificate and just import it on the test client, otherwise you'd want to actually have a trusted certificate prior to a production deployment.

Re: Global Protect connection Failed could not verify the server certificate of the gateway

EliyaDafna — Tue, 14 Jun 2022 06:35:45 GMT

In the beginning I made two local certificates on the Palo and inserted them into the computer running the client.

Re: Global Protect connection Failed could not verify the server certificate of the gateway

IMPL-PANSupport — Tue, 06 Dec 2022 08:03:03 GMT

We are also facing the same problem. We use a certificate signed by a trusted third party CA. Any suggestions are welcome.

Re: Global Protect connection Failed could not verify the server certificate of the gateway

wesprather — Wed, 08 Oct 2025 22:50:23 GMT

I know this post is WAY OLD, but 1) I never saw a satisfactory response and 2) I'm having this same issue with GP 6.3.3-676 on a MacBook Pro (Sonoma 14.8.1). I exported the self-signed certificate (from the Palo) and it should have included the root, then I added it to the Mac trusted certificates list, but I still get this error. Pesky issue I've had for years - thought I'd see what I was doing wrong...