Check certificate expiration for different IPs

[lorenzo93]

Integration name

Certificate Expiry

Link to integration documentation on our website

https://www.home-assistant.io/integrations/cert_expiry/

Describe the enhancement

Hi,

it would be wonderful if the integration have also the possibility to specify the IP addresses on which test the website and not just the hostname. A single service could than have more entities, one for IP.

Use cases

I have multiple servers serving the same website (for example one over IPv4 and another one over IPv6, or as another example copies of the same website over different servers). It would be excellent if I could specify a list of IP addresses so that I could check if the certificate expiration is syncronized or if one of the servers have the wrong certificate.
I cannot rely just on the hostname because all servers have the same hostname and I can't use just the IP address for server aliasing reasons.

Anything else?

No response

[github-actions[bot]]

🏷️ I've automatically added the integration: cert_expiry label to help categorize this feature request.

[mik-laj]

Personally, I'm not sure this is a common use case for home users. If you have more than one server or a more advanced environment, dedicated tool for server monitoring are probably better suited for this purpose than Home Assistant.

If you still want to do it in HA, you can use command_line integration, which will allow you to run an arbitrarily complex command that will read a certificate from any server.

[lorenzo93]

Having more servers I understand is not common use case, but IPv6 deployment is alive and spreading.

On the other hand, this integration is created for advanced users. Otherwise the same argument could be made for the Proxmox integration or other similar ones.

It is not uncommon to have a single reverse proxy for IPv4 (because usually ISPs give just one public IPv4) that handles HTTPS traffic for IPv4 and an IPv6 address directly on containers of different services handing IPv6 HTTPS, hence two servers/containers/VMs for the same website that should synchronize the certificate with some scripts.

Your other argument is fine, of course there are some advanced systems to monitor this kind of things (e.g., Zabbix) but HA is already configured to give me notifications, warnings, to show problems on screens around the house, is already testing basic connectivity using pings, etc. Setting up another monitoring system would be "overkill" for just certificate checking.