Client certificate for syslog is failing


Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.

L3 Networker

Client certificate for syslog is failing

Im trying to setup a syslog forward from a loggcollector with tls, i get this error in the syslog log on the collector.


Certificate subject does not match configured hostname; hostname='scrubbed', certificate=''

However the certificate has the correct hostname as a san name (aswell as, however it has lots of san names (10+), is the last one in the list of san name if i check the certificate with openssl from a other host. Has anyone run into issue with lots of san names on a palo while using client certificate?

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!