Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Node with multiple SSL certificates

Good morning/afternoon, I hope the thwackverse is doing well.

I'm sure this is easy but coming up with the magical search terms is not something I care to try so here goes.

I have a node that hosts multiple ssl certificates and I want each of them monitored for their expirations. When adding the node I use the host name which for my example will be node.something.org and it's polled though the use of a Linux agent. I try to add the application monitor for the ssl but the fqdn for site A is whizbang.something.org and there is no way that I can see to point the monitor to it, it wants to point to the host name. I could point it to the host name and hope that my ocd doesn't make me go completely crazy because the names don't match but then I need to add the second site. Site B has a fqdn of shazam.something.org which I again run into the same problem.

Node = 192.168.1.5 (3 Ip Address bound to the host)

Site A = 192.168.1.10 ssl - whizbang.something.org (standard 443 port)

Site B = 192.168.1.20 ssl - shazam.something.org (standard 443 port)

Any assistance is greatly appreciated.

Regards

Find more posts tagged with

Accepted answers

chad.every

I have had similar issues with with out of the box cert monitor. I created my own to get around this since i stack ssl certs on a single host.

SSL Certificate Expiration - SNI capable

You can assign this to your server and if you expand the component monitor just replace the 'Script Argument' of ${Node.Caption} to the FQDN of your site.

All comments

chad.every

I have had similar issues with with out of the box cert monitor. I created my own to get around this since i stack ssl certs on a single host.

SSL Certificate Expiration - SNI capable

You can assign this to your server and if you expand the component monitor just replace the 'Script Argument' of ${Node.Caption} to the FQDN of your site.

FormerMember

Thank you, I looked at that template but didn't try using it once I saw the word powershell, I assumed it to be windows specific but how you described it helped.

joe.tran

The PowerShell script monitor would run as in a local execution mod (i.e. executed and run from the Orion Poller), so it shouldn't matter if the cert is on a *nix server, if that's the concern.