Skip to main content
This article applies to CrashPlan for Small Business.
Looking for information about Incydr or CrashPlan for Enterprise? Search or browse.

Incydr, no.

CrashPlan for Enterprise, no.

Code42 for Enterprise, no.

CrashPlan for Small Business, yes.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Unable to sign in to the Code42 console due to content filtering

Overview

Users cannot sign in to the Code42 console because a content filtering application is being used to monitor user access to the Internet. This article describes the problem and how to resolve it.

Symptom

CrashPlan for Small Business users attempt to sign in to the Code42 console, but are unable to connect. The errors returned in this situation may vary, though HTTP response codes 400 and 431 are most likely.

Background

Content filtering is a common practice to ensure employees do not access restricted Internet content. In most cases, the filter only is set to prevent access to certain areas of the Internet that are restricted by your company's policies. However, if your company's content filtering software uses a web proxy, it can interfere with the ability of users to sign in to the Code42 console.

Recommended solution

If you suspect that content filtering may be the cause, add the Code42 domains your company uses to access the Code42 console to your content filtering software's allowlist. Doing so will ensure that users can access the Code42 console without interference from your company's content filtering software.