Icinga / Icinga/icinga-powershell-framework
Test-IcingaForWindows doesn't indicate the error "Certificate validation failed for IfW API on host 'localhost' [...] hostname mismatch"
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 87
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
After changing the hostname and creating a new certificate for the icinga2-agent, the icingaweb2-output of local plugins show
"Certificate validation failed for IfW API on host 'localhost' (SNI: 'hugo.my.domain'; CN: 'hugo') port '5668': code 62: hostname mismatch"
Running Test-IcingaForWindows doesn't indicate that there's any problem with a certificate.
BTW: executing Start-IcingaWindowsScheduledTaskRenewCertificate; solved the certificate-issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Test-IcingaForWindows entry point and reproduce the reported state after a hostname or certificate change. Compare its result with the icingaweb2-output error and the effect of Start-IcingaWindowsScheduledTaskRenewCertificate; done means the test indicates the certificate hostname-mismatch problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- security, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100