Skip to main content

Who is this article for?
Find your product plan in the Code42 console on the Account menu.

Incydr Professional and Enterprise
Incydr Basic and Advanced
Other product plans

Incydr Professional and Enterprise, yes.

Incydr Basic and Advanced, yes.

CrashPlan Cloud, yes.

Other product plans, yes.

CrashPlan for Small Business, no.

This article applies to Code42 cloud environments.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Device cannot connect due to deep packet inspection

Overview

A device running the Code42 app cannot connect to a destination because an administrator is using deep packet inspection to examine traffic from devices to the Code42 cloud. This article describes the problem and how to resolve it.

Symptom

The Code42 app connects to the Code42 cloud then disconnects immediately. 

Background

Communication between devices and the Code42 cloud uses transport-layer security (TLS). When an administrator uses a deep packet inspection tool to examine Code42 traffic, it can interfere with TLS. 

Deep packet inspection is a common technique for analyzing traffic going over 443 and works well in most situations. However, using deep packet inspection for TLS traffic over port 443 can cause communication interruptions. 

Recommended solution

To resolve the issue, we advise you to either turn off deep packet inspection altogether, or add our our IP addresses to the allowlist in the deep packet inspection tool. 

Also do the following:

For more ideas to resolve connection problems, see Cannot connect to destination.

  • Was this article helpful?