Skip to main content

This article applies to version 6.

Other available versions:

Version 5 | Version 4icon.qnmark.png

Available in:

StandardPremiumEnterprise
Small Business
Code42 Support

"Unable to login to server" error when performing a web restore

This article applies to version 6.

Other available versions:

Version 5 | Version 4icon.qnmark.png

Available in:

StandardPremiumEnterprise
Small Business

Overview

Using the administration console to restore archives from storage servers may result in an "Unable to login to server" error. This is usually due to a self-signed or invalid SSL certificate on the storage server and the need to manually accept this certificate when connecting to the Code42 server.

Recommended solution

Install CA-signed certificates on each of your storage servers.

A properly signed certificate prevents the web browser from prompting the user to accept the unsigned certificate. If you already installed CA-signed certificates on each storage server, verify that the storage server's hostname matches the name in the certificate.

Alternative solution

If you cannot get signed certificates, connect to the administration console on each of your storage servers over HTTPS on port 4285, and accept the self-signed certificate.

When connecting to the storage server directly, your browser should prompt you to either temporarily accept or permanently add an exception for the certificate.

Once the certificate is added to the exception list in the browser, web restores should function normally from the authority server over HTTPS.