- Code42 CrashPlan (previously CrashPlan PROe)
This article describes the solution for a known issue in which the CrashPlan app does not apply the TCP packet QoS priority settings.
Code42 environments that both:
- Use IPv4 (or a mix of IPv4 and IPv6)
- Use CrashPlan app version 5.3.0 or later on OS X and Linux
- This solution is only available for devices using CrashPlan app version 5.3.0 or later.
- You must repeat these steps each time you upgrade the CrashPlan app. These changes are reverted during the upgrade process.
- If you are using the CrashPlan app on Windows, contact our Customer Champions for Code42 for Enterprise support.
Before you begin
For customers with an on-premises authority server, you must upgrade your Code42 environment to Code42 server version 5.3.0 and CrashPlan app 5.3.0 or later.
To enforce the TCP Packet QoS setting:
Update configuration file
- On the device where the CrashPlan app is installed, navigate to the CrashPlan app configuration file:
- OS X
- Installed for everyone: /Library/LaunchDaemons/com.crashplan.engine.plist
- Installed per user: ~/Library/LaunchAgents/com.crashplan.engine.plist
- Linux: /usr/local/crashplan/bin/run.conf
- OS X
- Open the file in a text editor.
- Add this line to the configuration file: Djava.net.preferIPv4Stack=true
- Save your changes.
- Restart the device.
Disable TLS and restart the authority server
(Code42 server versions 5.4.1 and later with CrashPlan apps on OS X and/or Linux)
When you disable TLS, Code42 server and CrashPlan app communication occurs over the Code42 custom protocol. That protocol uses different ports than TLS does. For more information, see Enabling TLS Messaging.
Step 1: Disable TLS
Disable TLS for server and CrashPlan app connections:
- Sign in to the console.
- Double-click the Code42 logo in the upper left corner.
The command-line interface appears.
- Enter the following command to disable server connections:
setting.set system c42.sabre.listen_enabled false
- Enter the following command to disable CrashPlan app connections:
setting.set system c42.sabre.outgoing_client_enabled false
Step 2: Restart the authority server
After disabling TLS, restart the authority server by following the steps below.
- Enter the following command to restart the authority server from the CLI:
- The authority server process restarts, and you are temporarily disconnected from the administration console.