# Certificate validation failed: code 7: certificate signature failure

**URL:** <https://community.icinga.com/t/certificate-validation-failed-code-7-certificate-signature-failure/15584>\
**Category:** Icinga 2\
**Tags:** icinga2\
**Created:** [September 25, 2026, 1:13am UTC](https://community.icinga.com/t/certificate-validation-failed-code-7-certificate-signature-failure/15584 "2026-09-25T01:13:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![monigacom](https://community.icinga.com/letter_avatar_proxy/v4/letter/m/bb73d2/32.png) [@monigacom](https://community.icinga.com/u/monigacom)\
**Post date:** [September 25, 2026, 1:13am UTC](https://community.icinga.com/t/certificate-validation-failed-code-7-certificate-signature-failure/15584/1 "2026-09-25T01:13:27Z")

</div>

Hello,

I’m seeing this error on both HA satellites in only one zone. Both satellites can talk to the masters and not certificate issue reported on the master for them. This error is only seen between the two satellites when they try to communicate with each other.

I’ve checked ca.crt and their own cert/keys which seemed good to me. This may have started when the auto renewal of certs didn’t work at the time and the certs were manually signed on the master. Any idea about the issue here? Thanks

I’ve Icinga2 2.15.1-1 running on Ubuntu 24.04 LTS.

---

<div class="post-metadata">

**Author:** ![monigacom](https://community.icinga.com/letter_avatar_proxy/v4/letter/m/bb73d2/32.png) [@monigacom](https://community.icinga.com/u/monigacom)\
**Post date:** [September 29, 2026, 1:37pm UTC](https://community.icinga.com/t/certificate-validation-failed-code-7-certificate-signature-failure/15584/2 "2026-09-29T13:37:23Z")

</div>

Never mind. The issue was with old satellites having the same name as the new ( production ) ones duh!