Secure Connection
By default, the communication between an OPSWAT product instance and a My OPSWAT On-premises server is not encrypted. If HTTPS is enabled, encrypted communication between the server and the product instances can be enforced. This section describes how to enable HTTPS connection for My OPSWAT On-premises.
Requirements
In order to enable HTTPS on My OPSWAT On-premises server, a trusted certificate issued by a certificate authority provider or a self-signed certificate along with their private key and password (if needed) files must be provided.
Adding Certificates
To add a certificate for the Secure Connection settings, please refer to Certificates.
Enabling HTTPS
- On the left navigation, navigate to Settings > Server tab > Secure Connection section.

- Toggle Enable HTTPS to ENABLE
- Choose a certificate you added in the Certificates tab.
- Select the TLS version(s) you want to enforce HTTPS for. The port configuration currently cannot be changed.
- Click Save to confirm your selection.
- My OPSWAT On-premises should immediately refresh itself for the new settings to take effect. Please note that the refresh process can take several minutes and the server cannot be accessed until its completion.
Please note that when using a self-signed certificate to enable HTTPS mode, the managed product instances should have this certificate in their trust store to be able to establish a connection to the My OPSWAT server.
For MetaDefender Kiosk L-series instances, they should be on version 5.6.2 or newer.
Disabling HTTPS
- On the left navigation, navigate to Settings > Server tab > Secure Connection section.
- Toggle Enable HTTPS to DISABLE.
- Click SAVE.
- My OPSWAT On-premises should immediately refresh itself for the new settings to take effect. Please note that the refresh process can take several minutes and the server cannot be accessed until its completion.
Server URL
The Server URL setting is used to set the My OPSWAT On-premises' server address, such as when generating download URLs for product reports. The server URL can be either a domain or an IP address.
For example, with the server URL http://myopswat.local, a report's download URL is formatted as http://myopswat.local/console/reports/<report>/location>/report.json
Please note that the chosen Server URL should be resolvable by the system that you are using to browse the My OPSWAT On-premises console.
The Enable HTTPS setting affects the protocol scheme used for the server URL, which is either http or https.
