KB Article #189704
Sentinel server starts but the interface is not accessible
Problem
Sentinel server starts, but the interface is not accessible.
The sentinel.log file shows the following warning:
TemplateServer.doAfterHttpServerNotStarted - Server 'HTTPServer' did not start. Maximum attempts to check server started reached.
Resolution
This error could be caused by several factors.
Here are some elements you could check:
1. Check the Sentinel/broadcast/commit folder for any strange files that should not be there.
2. In a Firewall context please check if the ports 1308 and 1309 are open.
3. Stop the Sentinel server and run the configure script in the main installation folder, just to go through the screens without changing anything. During this process make sure however that the parameter "Verifiy database configuration" is set to True and also check the next point.
4. During the above configure process, you will go through all the screens, with the option Next.
Make sure you can go past the Sentinel Webdashboard database section, meaning the connection to this database is possible.
If you encounter any issues here and the connection is not possible, this is what prevents the HTTP Server to start. You might have to restart the database or check if the provided details are correct.
5. Check if the certificates you are using (default or custom) are still valid.