Overview

You may be experiencing an issue with the renewal of the SSL certificate on Kerio Connect server running versions 9.4.x. When triggering a Let's Encrypt certificate renewal, you may be getting a pop-up error message in the Kerio web admin UI

When clicking on Show Data, the full error is shown, and you can see: ReferenceError: k_lib is not defined.

Solution

The issue was specific to Kerio Connect versions between 9.4.0 and 9.4.1, and it was fixed in version 9.4.2. Therefore, in order to fully fix the issue, please proceed with Upgrading Kerio Connect Server to the Latest Version. We strongly recommend upgrading, as the newer Kerio Connect versions contain a lot of improvements in this area, including a renewed root certification authority for Let's Encrypt certificates.

In case you are blocked by any reason to upgrade to the latest available version right away, you can also use the below workaround:

1. Download the attached hotfix file
2. Extract the ZIP archive.
3. Navigate to the following directory, based on installed OS. Defaults are:
   1. Windows: C:\Program Files\Kerio\MailServer\web\weblib\int\adm\
   2. Linux: /opt/kerio/mailserver/web/weblib/int/adm/
   3. Mac: /usr/local/kerio/mailserver/web/weblib/int/adm/
4. Rename widgets.js to widgets.js.bak
   
5. Copy the new widgets.js extracted from the downloaded ZIP archive.
6. Clear Cache on the client browser side to make sure the new widgets.js is downloaded.
   1. Chrome guide
   2. Firefox guide
   3. Edge guide

Summary

The issue with the SSL certificate renewal on the Kerio Connect server can be resolved by upgrading to the latest available version. If for some reason you can't upgrade right away and this is blocking your daily operations, you can follow the steps listed above to workaround the issue

FAQ

1. What does the error message "ReferenceError: k_lib is not defined" mean?
   This error message typically indicates a problem with the SSL certificate renewal process on the Kerio Connect server.
2. What if I can't upgrade right away to the newest version?
   The attached hotfix file can be used as a workaround.