I have 10 Windows Server 2019 servers running Certify The Web (mostly version 7.0.18.0, with a couple on 7.0.20.0).
On all 10 servers, the Certify.Service fails to auto-start on its own after a system reboot. I have to go in and start it manually every time. Has anyone else encountered this on Server 2019, or does anyone have ideas on how to fix it?
As a side note/feature request: It would be incredibly convenient if there was a way to trigger version updates or deployments directly from the web interface/management hub in environments with multiple servers like this.
For support questions you need to be emailing support at certifytheweb.com - this community forum gets checked periodically but it’s not the main support channel for licensed customers (or really for evaluation questions).
Service not auto starting is not a commonly reported issue and it would be great to be able to replicate the same behavior.
Is the service actually not running or does the desktop UI just say it’s not (that can be an ip/port problem)?
Is the service set to Automatic in windows? It should be by default but could vary if you choose advanced installation with a different users account etc.
Is there anything in the logs (C:\ProgramData\certify\logs)