Skip to main content
Code42 Support

"Unable To Login To Server" Error When Performing A Web Restore

Applies to:
  • CrashPlan PROe
When accessing the administration console over HTTPS, web restores 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 enterprise server.

Affects

CrashPlan PROe 3.x administration console

Recommended solution

Long-term secure fix

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.

Short-term workarounds

Two options to work around this problem:

  1. Connect over standard HTTP
  2. Log in to the administration console on each of the storage servers

Connect over standard HTTP

On your master server, turn off "Require SSL to access console:" and connect over standard HTTP on port 4280.

For web restores, the connection to the storage server happens using the same protocol by which you're connected to the master server, and connecting using HTTP doesn't use an SSL certificate.

Sign in to the admin console on each of the Storage server

A more secure short-term solution is to connect to the administration console on each of your storage server over HTTPS on port 4285 and accept the self-signed certificate.

When connecting to the enterprise 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 even when connected to the master server over HTTPS.