Skip to content

WebClient setup

This topic describes the requirements and certificate considerations for installing the WebClient.

The WebClient must be installed on a computer running Octoplant server version 105.0 or later. The installation requires Windows Server. Supported Windows Server versions are 2019, 2022, and 2025. Specific .NET and ASP.NET Core frameworks are also required. Internet Information Services (IIS) must not be installed because it can interfere with WebClient operation.

Administrator privileges are required to run the installer. The installation wizard supports English, German, and Spanish, and includes steps for configuring the web server and importing SSL certificates. The process temporarily restarts the VDog MasterService, so schedule the installation during planned downtime.

After installation, a desktop shortcut is created for easy access. The WebClient can also be reached from other devices in the local network by using the same URL. Supported browsers include Google Chrome and Microsoft Edge.

The WebClient must be installed after the Octoplant server is installed and configured. During server setup, a self-signed certificate is created and stored in the <server archive>\configuration\local folder.

To ensure secure and trusted connections, we recommend that you:

  • Replace the self-signed certificate with one from a trusted CA.
  • Use the same certificate for both server authentication and WebClient SSL/TLS communication.

For instructions, see Use your own security certificate.

Info

Replacing the certificate means that you must change every client computer.

Leaving the self-signed certificate in place is a valid option. However, every browser displays a security warning until a proper certificate is installed.

After replacing the certificate, you must do the following:

  • Make sure that every Octoplant client has any required updates to trust the new certificate.

  • Otherwise, delete the knownhosts.txt file from the following locations:

    Client archive: \vdClientArchive\VD$A\Configuration\Local

    Server archive: \vdServerArchive\VD$A\Configuration\Local

    This step ensures that clients can reconnect securely.

If you install a certificate from a trusted Certificate Authority (CA), the client-side browser might still warn that the certificate is not trusted. In this case, review the installation instructions from your CA.

Even with a trusted CA certificate, warnings may occur for the following reasons:

  • Missing CA in the browser’s trusted store, which is common on older systems: Keep systems updated to receive new CA certificates through Windows Update.
  • Missing intermediate certificates: Make sure that your server provides the full certificate chain, including intermediate and root certificates.
  • Expired certificate: Renew or replace the certificate as needed.

Your IT department should be able to address any of these issues.

Related topics