These instructions are for setting up a TLS connection between a user’s desktop and the Sequel Web Interface/Sequel Web Server (SWS). This is not for the ‘back-end’ connections to the Host and other databases.

IMPORTANT: Before configuring TLS, you must obtain a valid certificate, comprised of two files:

  • certificate-name.crt (or certificate-name.cert)
  • certificate-name.key


  1. Install the two certificate files into a folder on the SWS server. You may use any folder location, however the recommended location is C:\Program Files (x86)\SEQUEL\SEQUELHttpServer\certs.

    Note: Depending on your current SWS software level the \certs subfolder may not exist. If using this default location, create the certs folder if necessary.

  2. Using Windows Services, stop the following three services:
    • Sequel Http Server
    • Sequel Web Server
    • SequelDatabaseServer
  3. Using Windows Explorer, navigate to folder : C:\Program Files (x86)\SEQUEL\SEQUELHttpServer\conf
  4. Using a text editor, edit the file httpd.conf and remove the leading # to un-comment the following lines:
    1. #LoadModule ssl_module modules/
    2. #Include conf/extra/httpd-ssl.conf

  5. Save your changes.
  6. Open the extra folder and edit the file httpd-ssl.conf as follows:
    1. Use the text editor’s Replace function to replace all instances of c:/Apache2 with c:/Program Files (x86)/SEQUEL/SEQUELHttpServer.
    2. Find the line beginning ServerName and replace localhost with your fully qualified server name. This must match the server name on your certificate.

      Example : ServerName

    3. Find the line beginning with ServerAdmin and replace the example email address with a valid email address.
    4. Find the line beginning with SSLCertificateFile and replace the entire string with the path and name of your Certificate file (see step 1 for path).
    5. Find the line beginning with SSLCertificateKeyFile and replace the entire string with the path and name of your Certificate Key file (see step 1 for path).

  7. Save your changes.
  8. Restart the services
  9. Test that the SWS server now accepts secure connections.

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 05, 2021