Skip to main content
Question

CMA - Peer name is not in peer certificate

  • August 27, 2026
  • 0 replies
  • 2 views
S
Forum|alt.badge.img

Hello,

I’m testing Windows monitoring through CMA but I keep getting errors when using TLS.

Configuration : 

  • Connection : Agent to poller
  • Encryption : TLS
  • Public certificate : /etc/pki/cma/server.crt (644)
  • Private key : /etc/pki/cma/server.key (644)
  • CA : Left blank (as per the documentation)

When using the poller’s FQDN (server.domain.corp) in the agent’s config, I get these errors on the agent’s side :

[2026-08-27 17:29:10.422] [centreon-monitoring-agent] [error] [bireactor.cc:98] 0x195a862a240 client peer:server.domain.corp:4317 fail read from stream
[2026-08-27 17:29:10.484] [centreon-monitoring-agent] [error] [bireactor.cc:148] 0x195a862a240 client peer server.domain.corp:4317 fail write to stream
[2026-08-27 17:29:10.484] [centreon-monitoring-agent] [error] [bireactor.cc:189] 0x195a862a240 peer:server.domain.corp:4317 client::OnDone(failed to connect to all addresses; last error: UNKNOWN: ipv4:x.x.x.x:4317: Peer name server.domain.corp is not in peer certificate)

and this error log on the poller’s side :

[2026-08-27T17:29:05.756+02:00] [grpc] [error] [12427] No match found for server name: server.domain.corp


When using the poller’s IP address (x.x.x.x) in the agent’s config, I only get these errors on the agent’s side :

[2026-08-27 17:39:33.853] [centreon-monitoring-agent] [error] [bireactor.cc:148] 0x1ad8a8df270 client peer x.x.x.x:4317 fail write to stream
[2026-08-27 17:39:33.853] [centreon-monitoring-agent] [error] [bireactor.cc:98] 0x1ad8a8df270 client peer:x.x.x.x:4317 fail read from stream
[2026-08-27 17:39:33.853] [centreon-monitoring-agent] [error] [bireactor.cc:189] 0x1ad8a8df270 peer:x.x.x.x:4317 client::OnDone(failed to connect to all addresses; last error: UNKNOWN: ipv4:x.x.x.x:4317: Peer name x.x.x.x is not in peer certificate)

The server’s certificate is signed by our Intermediate CA and contains FQDN in the Subject and both the IP and FQDN in the SAN : 

Certificate:
    Data:
        Version: 3 (0x2)
[...]
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C = XX, DC = corp, DC = xxx, O = XXX, OU = XXX, CN = XXX Intermediate CA
        Validity
            Not Before: Aug 27 13:36:06 2026 GMT
            Not After : Aug 26 13:36:06 2028 GMT
        Subject: C = XX, ST = XXX, L = XXX, O = XXX, OU = XXX, CN = server.domain.corp, emailAddress = xxx
[...]
        X509v3 extensions:
            X509v3 Subject Alternative Name:
                DNS:server.domain.corp, IP Address:x.x.x.x
[...]

Both the Root CA and the Intermediate CA are trusted by the agent.

Did anyone else encounter and managed to solve this issue ?

Centreon v25.10.16
Centreon Monitoring Agent v25.10.8

Terms & ConditionsAccessibility statement