topic Re: Validation of Local client certificate failed resulting in error 58, Problem with the local SSL cert in General Topics

Validation of Local client certificate failed resulting in error 58, Problem with the local SSL cert

FarzanaMustafa — Wed, 13 Feb 2019 01:48:43 GMT

Hello,

Has anyone encoutered this error message below? I could not find much info on this.

Using PA500 with PAN-OS 8.1.4

domain: 1 receive_time: 2019/02/09 10:16:13 serial: 00xxxxxxxx seqno: 4858056 actionflags: 0x0 type: SYSTEM subtype: wildfire config_ver: 0 time_generated: 2019/02/09 10:02:12 dg_hier_level_1: 0 dg_hier_level_2: 0 dg_hier_level_3: 0 dg_hier_level_4: 0 vsys_name: device_name: FW01 vsys_id: 0 vsys: eventid: wildfire-auth-failed object: fmt: 0 id: 0 module: general severity: critical opaque: Validation of Local client certificate failed resulting in error 58, Problem with the local SSL certificate

Re: Validation of Local client certificate failed resulting in error 58, Problem with the local SSL

BPry — Wed, 13 Feb 2019 02:41:48 GMT

@FarzanaMustafa,

By chance are you using a WF-500 and custom certificates?

Re: Validation of Local client certificate failed resulting in error 58, Problem with the local SSL

FarzanaMustafa — Wed, 13 Feb 2019 06:45:20 GMT

The alert is being emailing from the Pan. We are not using the Wildfire on prem box.

Re: Validation of Local client certificate failed resulting in error 58, Problem with the local SSL

BPry — Wed, 13 Feb 2019 16:49:16 GMT

@FarzanaMustafa,

The only time I've seen that issue in the past was when running WF-500 boxes and custom certificates for auth. If the firewall issues the error more than once I would reach out to TAC and see if they can help you figure out exactly why you are seeing this error. If you are using the public WildFire cloud you shouldn't be getting this error at all.

Re: Validation of Local client certificate failed resulting in error 58, Problem with the local SSL

jasonwald — Mon, 20 Jan 2020 13:39:51 GMT

Same error here on 8.1.11 with a PA-220 and no local wildfire box

Re: Validation of Local client certificate failed resulting in error 58, Pr

mprintz — Wed, 15 Jul 2020 20:02:53 GMT

Did you guys ever resolve this? I'm now experiencing the same issue. No local WF box, but I did just upgrade our PA-3020s to 9.1.3 yesterday (never saw the error before that). Thanks.

Re: Validation of Local client certificate failed resulting in error 58, Pr

FarzanaMustafa — Wed, 15 Jul 2020 21:29:32 GMT

For our case, TAC suggested below.

-- Regarding the error message I see that the error started surfacing starting from 5th Nov 20:55:53.
-- However, the root cause of the issue is the sysd and snmpd crash on 6th Nov around the specified time.
-- We have seen similar issues before for PAN OS 8.0.x which is related to group in MP memory.
-- I see that the firewall is on PAN OS 8.0.18.
-- PAN OS 8.0.x is end of life and is no longer supported.
-- Please upgrade the PAN OS to 8.1.11 to prevent this behavior in future.

Re: Validation of Local client certificate failed resulting in error 58, Pr

mnashik — Thu, 15 Oct 2020 20:25:55 GMT

I Guess this is addressed in 81.16.

https://docs.paloaltonetworks.com/pan-os/8-1/pan-os-release-notes/pan-os-8-1-addressed-issues/pan-os-8-1-16-addressed-issues.html

Re: Validation of Local client certificate failed resulting in error 58, Pr

mprintz — Fri, 16 Oct 2020 12:42:56 GMT

Thanks for the update. Unfortunately for me, it doesn't look like the fix made it into 9.1 yet (or I'm missing it in the addressed issues list).

Re: Validation of Local client certificate failed resulting in error 58, Problem with the local SSL cert

Ponrajesh — Thu, 29 Apr 2021 08:37:19 GMT

The issue is fixed at PAN-OS 9.1.10, its caused due to PAN ID PAN-157570

Re: Validation of Local client certificate failed resulting in error 58, Problem with the local SSL cert

mprintz — Fri, 11 Jun 2021 12:20:01 GMT

Now that 9.1.10 has been released, I checked out the release notes and I don't see that bug mentioned anywhere (either by number or description). Where did you get the info that the fix was in that release? Thanks.