HTTP Server and SSL for the Mirror

In the HTTP Server section of the Mirror tab you can specify the Server port where the HTTP server will listen as well as the type of Authentication used by the HTTP server. By default, the Server port is set to 2221.

The Authentication option defines the method of authentication used for accessing the update files. The following options are available: None, Basic, and NTLM. Select Basic to use base64 encoding with basic username and password authentication. The NTLM option provides encoding using a safe encoding method. For authentication, the user created on the workstation sharing the update files is used. The default setting is None, which grants access to the update files with no need for authentication.



Authentication data such as Username and Password is intended only for accessing the mirror HTTP server. Complete these fields only if a username and password are required.

Append your Certificate chain file, or generate a self-signed certificate if you want to run HTTP server with HTTPS (SSL) support. The following certificate types are available: ASN, PEM and PFX. For additional security, you can use HTTPS protocol to provide update files for download. It is almost impossible to track data transfers and login credentials using this protocol. The Private key type option is set to Integrated by default (and therefore the Private key file option is disabled by default). This means that the private key is a part of the selected certificate chain file.


Self-signed certificates for HTTPS mirror

If you are using an HTTPS mirror server, you need to import its certificate to the trusted root store on all client machines. See Installing the trusted root certificate in Windows.