Skip to main content
Code42 Support

SSL key error prevents access to the administration console

Applies to:
  • CrashPlan PROe

Overview

If an enterprise server in your Code42 environment is using a version of Java that does not meet the Code42 platform system requirements, you may see one of the following SSL errors when connecting to your administration console:

  • ERR_SSL_WEAK_SERVER_EPHEMERAL_DH_KEY
  • Server has a weak ephemeral Diffie-Hellman public key.
  • SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.

To resolve this issue, update Java on your enterprise server.

Affects

This issue affects enterprise servers that meet all of the following conditions:

  • Use Java Runtime Environment (JRE) version 6
  • Use enterprise server version 4.2 or later

Recommended solution

These steps refer to the main application directory of the enterprise server. By default, that directory is:

  • Linux: /opt/proserver
    Applies to enterprise servers installed as root on Ubuntu
  • Windows: C:\Program Files\CrashPlan PROe Server
  • OS X: /Applications/PROServer.app/

Linux

Step 1: Identify your Java installation

  1. Stop the enterprise server.
  2. Navigate to the main application directory.
  3. Open the file .install.vars in a plain text editor.
  4. Read the line JAVA_HOME.
    • If your JAVA_HOME refers to a path within the main application directory, use Option 1: Bundled Java.
    • if your JAVA_HOME refers to a path outside the main application directory, use Option 2: System Java.

Step 2: Reinstall Java

Select an option based on the location of your Java installation.

Option 1: Bundled Java
  1. Within the main application directory, rename the jre directory to jre_old as a backup.
  2. Create an empty jre directory in the main application directory.
    This replaces the original jre directory.
  3. Download the 64-bit tarball for the latest version of Oracle JRE 7.
  4. Extract the tarball to the jre directory in the main application directory.
  5. Continue to Step 3: Start Your Enterprise server.
Option 2: System Java
  1. Use your operating system to uninstall the outdated JRE and reinstall a supported JRE.
  2. Continue to Step 3: Start Your Enterprise server.

Step 3: Start your Enterprise server

  1. Start the enterprise server.
  2. Sign in to your administration console.
  3. On your file system, navigate to the main application directory.
  4. Remove the jre_old directory.

Windows

  1. Stop the enterprise server.
  2. Navigate to the main application directory, which contains the jre directory.
  3. Rename the jre directory to jre_old as a backup.
  4. Create an empty jre directory in the main application directory.
    This replaces the original jre directory.
  5. Download the 64-bit Windows EXE for the latest version of Oracle JRE 7.
  6. Install the JRE to the jre directory within the main application directory.
    1. Double-click the EXE.
    2. Select Change destination folder.
    3. Click Change.
    4. Browse to the jre directory.
    5. Click Next to complete the JRE installation.
  7. Start the enterprise server.
  8. Sign in to your administration console.
  9. On your file system, navigate to the main application directory.
  10. Remove the jre_old directory.

OS X

  1. Stop the enterprise server.
  2. Download the Mac OS X x64 DMG for the latest version of the Oracle JDK 7.
    You must download the JDK, not the JRE.
  3. Mount the DMG.
  4. Double-click the PKG and follow the prompts to install the Oracle JDK 7.
  5. Start the enterprise server.
  6. Sign in to your administration console.

Alternative solution

Linux and Windows only

You can also uninstall and reinstall the Code42 enterprise server. This solution is applicable only to Linux and Windows because installers for those operating systems include a bundled JRE installation.

Step 1: Create a database dump

  1. Sign in to the administration console.
  2. Navigate to Settings > Server.
  3. From the action menu, choose Dump Database.
    The enterprise server dumps a copy of its database to:
    • Linux: /var/opt/proserver/dumps
      Applies to enterprise servers installed as root on Ubuntu
    • Windows: C:\ProgramData\PROServer\dumps
    • OS X: /Library/Application Support/CrashPlan/PROServer/dumps
  4. Copy the database dump folder to another location in order to preserve the database dump through uninstallation.
Database dump locations
If your Code42 environment includes storage servers, each storage server also contains a copy of the database dump.

Step 2: Uninstall and reinstall the Enterprise server

  1. Uninstall the enterprise server software.
  2. Reinstall the enterprise server software.

Step 3: Import the database dump

  1. Sign in to the administration console.
  2. Navigate to Settings > Server.
  3. From the action menu, select Import Database.
  4. Select your database dump.
  5. Click Submit.
    The enterprise server restarts to import your database dump.
  6. Sign in to the administration console after the enterprise server restarts.
    The administration console appears without displaying an SSL error.