Some users were having issues with using Sscoutbees (HTTP/S Scout) to check certificate expiration on web servers – specifically, it was missing revoked certificates. A potential solution to this issue was suggested by another user, who asked for more details on the output of Scoutbees and whether there may be potential to set up an alert on it. There were also mentions of potential issues after upgrading to v1233 and using predefined Hives or custom Hives. This discussion took place within ControlUp.
Read the entire ‘Troubleshooting Certificate Expiration Checks with HTTP/S Scout on ControlUp v1233’ thread below:
We use Sscoutbees (HTTP/S Scout) to check Cert Expiration on web servers. It seems to miss if a cert was revoked. Any way to test for that?
Adding the PM for visibility. This is an interesting use case. Do you have a screenshot of the revoked cert output in SB? I’m thinking this is something Workflows may be able to address as well. @member
It doesn’t show any error or issue in scoutbees using an http scout. I did try making a site load scout but it just failed. I don’t recall the actual message. We have since fix the cert.
I understand. I was trying to see if it showed any output results to see if we can setup an alert on it.
Our team has an issue post upgrading to v1233 as Site Load scout will end up showing cert issue. we have disabled many site loads as it will not pass through.

cc @member
the sites you are running the site load scout configured with an active and valid certificate?
@member
ControlUp’s Hive or your own custom Hive?
Are these internal sites or public facing sites?
I’m on v1233 and all mine are working as expected.
I haven’t tested or checked cloud hives but this one is for custom hives v1233.
Continue reading and comment on the thread ‘Troubleshooting Certificate Expiration Checks with HTTP/S Scout on ControlUp v1233’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers, ControlUp Synthetic Monitoring, ControlUp Workflows
