Skip to content

WebClient installation

The WebClient must be installed on a computer running octoplant server version 105.0 or higher. The installation requires Windows Server (2016–2025), along with specific .NET and ASP.NET Core frameworks. Internet Information Services (IIS) must not be installed, as it can interfere with the WebClient operation.

Administrator privileges are necessary 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 it should be scheduled during planned downtime.

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

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

It is recommended that in order to ensure secure and trusted connections:

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

Instructions on this can be found under Use your own security certificate.

Info

Please note that replacing the certificate will result in the need to change every client computer.

Leaving the self signed certificate there is a valid option, however, you will see a security warning in every browser until a proper certificate is installed.

After replacing the certificate, you must:

  • Ensure every octoplant client has any required updates to trust the new certificate.

  • Otherwise, delete the knownhosts.txt file from:

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

    This step ensures clients can reconnect securely.

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

Even with a trusted CA certificate, warnings may occur due to:

  • Missing CA in browser’s trusted store (common on older systems): Keep systems updated to receive new CA certificates via Windows Update.
  • Missing intermediate certificates: Ensure your server provides the full certificate chain (intermediate + root).
  • Expired certificate: Renew or replace as needed.

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

Related topics