After finishing the initial configuration of Kerio Connect on a Linux deployment, the Kerio Connect service is restarting, as seen in the screenshot below. Once it has restarted, the configuration wizard needs to be filled again from the start and this occurs endlessly.
systemctl status kerio-connect.service from the command-line to check the Kerio Connect service's status, it throws the error
Can't open PID file /run/kms.pid (yet?) after start: No such file or directory
The below message is seen repeatedly in the error log file indicating that the server is in a blank state:
externalLogger.cpp: FullText [external]: SEVERE Bad response, tag domain not found,
or no users on the server (IndexingMessageHandler.handleUsers)
- Manually stop the Kerio Connect service.
- Open the Kerio Connect installation folder. The default location is
- Open the mailserver.cfg file and modify the value of the
- Save the changes.
- Start the Kerio Connect service.
Accessing the Kerio Connect administration console no longer opens the Configuration Wizard and you can continue with actual the Kerio Connect setup.