Overview

Occasionally, customers will report that their HTTP/S service will not auto-start regardless of the setting in the Admin UI. This will cause an interruption in the mail flow as the service needs to be manually started. The following steps will provide the fix for this issue.

Requirements

Admin access to the Kerio Connect server.

Root Cause

Incorrect HTTP/S service settings and values.

Resolution

Step 1: Verify if the startup type is set to Automatic

1. Log into Kerio Connect Administration.
2. Go to Configuration > Services and make sure the Startup Type is set to Automatic.
   
   
   
   
3. If the Startup Type is not set to Automatic, advise the customer to select each service in the table and set the type to Automatic. Upon restating Kerio Connect, the service should auto-start.

Step 2: Check the AutoStart value in mailserver.cfg

If the above does not fix the issue, you will need to check the AutoStart value in the mailserver.cfg file.

1. Stop Kerio Connect.
2. Go to the Kerio Connect installation directory and edit the mailserver.cfg file. Locate the table name for the service with the issue, similar to below and make sure that the AutoStart has a value of 1.

<table name="service-https">
<variable name="Port">443</variable>
<variable name="AutoStart">1</variable>

3. Save the mailserver.cfg file and start Kerio Connect.

Validation

If the actions were successful, the services will autostart.