Skip to main content

Who is this article for?

CrashPlan Cloud
CrashPlan for Small Business
CrashPlan On-Premises

Find your product plan in the Code42 console on the Account menu.
Not a CrashPlan On-Premises customer? Search or browse Incydr and Instructor, CrashPlan Cloud, or CrashPlan for Small Business.

Instructor, no.

Incydr Professional, Enterprise, Gov F2, and Horizon, no.

Incydr Basic, Advanced, and Gov F1, no.

CrashPlan Cloud, no.

Retired product plans, yes.

CrashPlan for Small Business, no.

Code42 Support

IP addresses and ports used by the Code42 platform


The Code42 server, the Code42 app, and other products in your Code42 environment use certain network ports to function normally. If you have network connectivity issues with Code42 for Enterprise, verify that your firewall rules permit traffic over these ports.


Open only the necessary ports
As a best practice, configure firewalls to open only those ports required by your software.
Deny inbound traffic at all other ports.
Port 4282 is no longer supported in the Code42 cloud
Computers using legacy port 4282 can no longer back up to or restore from the Code42 cloud. Use port 443 and 4287 instead. For more information, see End of support for port 4282 in the Code42 cloud.

Code42 server network ports

The following tables list the default Code42 server ports.

Inbound ports

In firewalls:

  • Open port 4287 for inbound requests from Code42 apps.
  • Open port 4285 for inbound requests from browsers and from Code42 apps version 6.5 and later.
  • Open 4280 only in the rare case where your server does not use TLS security.
Port forwarding
You can use port forwarding, also called port mapping, to avoid port conflicts and port restrictions within your Code42 environment and on other networks.
Port(s) Protocol Source Destination Description

4287 (TLS)

  • LAN networks
  • Internet

Your authority server

  • Backup traffic from internal and external endpoints
  • Statistics and job status from internal and external endpoints
Your storage servers Backup traffic from internal and external endpoints
4280 (HTTP)
4285 (HTTPS)
  • LAN networks
  • Internet
Your authority server and storage servers
  • Browser access to Code42 consoles, and to web restore to internal and external endpoints
  • For Code42 servers 6.5 and later deploying Code42 apps 6.5 and later, access for client deployment and customization.
Inbound IP addresses

For best results, we recommend that you allow inbound requests to your Code42 authority server from all the Code42 cloud storage IP addresses.

Outbound ports

In firewalls:

  • Open ports 25, 53, 123, and 443 to let your Code42 servers send requests to mail, DNS, NTP (Network Time Protocol) servers, and the Code42 license server.
  • Open an LDAP or RADIUS port only if you use one of those services.
  • Open port 5432 only for a server that uses a PostgreSQL database.
    • Open 5432 if PostgreSQL resides at an IP address other than the server's address,
    • Or open 5432 if PostgreSQL and your server share the same address, but your firewall otherwise blocks connections to localhost.
Specific IPs
For specific Code42 IP addresses, contact our Customer Champions for support.
Port(s) Protocol Source Destination Description
25 TCP Your Code42 server Mail Server(s) SMTP services
53 UDP Your Code42 server DNS Server(s) DNS services
123 UDP Your Code42 server NTP Server(s) NTP services
443 TCP Your Code42 server

Code42 product license/subscription service

TCP Your Code42 server

Managed appliance and monitored authority upgrade files

389 (LDAP)
636 (LDAPS)
TCP Your authority server LDAP or Active Directory Server(s) Integration with LDAP or Active Directory services
UDP Your Code42 server RADIUS Server(s) RADIUS services
5432 TCP Your Code42 server PostgreSQL Database service

Multi-server deployment ports

If you use multiple Code42 servers, most likely one authority server and one or more storage servers, then in the firewall that protects each server:

  • Open 4283 only in the rare cases where your servers do not use TLS security.
  • Open port 4287 and 4288, both inbound and outbound, for server-to-server communications using TLS security.
  • (Version 7.0 and earlier) Open port 4286, both inbound and outbound, also for server-to-server communications.
Port(s) Protocol Source Destination Description


4287 (TLS)

4288 (TLS)


Your Code42 server

Your Code42 server Data balancing between Code42 servers

(Version 7.0 and earlier)

Your Code42 server

Your Code42 server Statistics traffic between Code42 servers

Code42 app ports

You must have port 443 or 4287 open for use by Code42 apps.

In firewalls that protect your devices and the LANs where they reside:

  • Open 4287 for outbound messages to your authority server.
  • If you use Code42 cloud storage, open port 443 for outbound messages to storage server.
  • Open port 4244 if your firewall blocks connections from localhost to localhost to enable the Code42 app and the Code42 service to run on the same device. If the default port 4244 is in use when the Code42 app installs, the app uses some other available port. See the app.log file
  • To enable the optional web restore function, open port 4285 for outbound messages from browsers to storage servers, on-premises or in the Code42 cloud.
Port(s) Protocol Source Destination Description


  • Authority server
  • Storage servers
Default ports for communication from the device to Code42 server(s) in on-premises environments
443 TCP LANs Code42 cloud storage Communication from the device to storage in the Code42 cloud
4244 TCP Localhost Localhost Default port for Code42 app connection to the Code42 service
4285 TCP Browsers in LANs Your storage server For web restore, user activity profilesSSO sign in, and authentication API calls.

Monitoring ports

Only apply firewall rules for monitoring if you use Code42's managed appliance monitoring.

Specific IPs
For specific IPs, contact our Customer Champions for support.
Port(s) Protocol Source Destination Description

(Cloud OS only)

TCP Your Code42 server

Code42 Monitoring Address

Remote monitoring (Zabbix)

(Pre-Cloud OS only)

TCP Your Code42 server

Code42 Monitoring Address

Remote monitoring (Zabbix)
22 TCP

Code42 Remote Access IP

Your Code42 server Remote SSH access from Code42 offices

Code42 Remote Access IP

Your Code42 server Remote console access from Code42 offices

Code42 Remote Access IP

Your authority server's IPMI Interface Remote IPMI access from Code42 offices
623 TCP Your authority server's IPMI Interface

Code42 Remote Access IP

Remote IPMI access from Code42 offices


Code42 cloud storage IP addresses

Code42 uses the following IP addresses to provide access to Code42 cloud storage. To ensure uninterrupted access to the Code42 cloud, open your firewall to the following IP addresses:

  • was formerly used but is now retired and no longer in use. You do not need to open your firewall to this range anymore. If you previously opened your firewall to this range, we strongly recommend removing it because Code42 will not control it after January 1, 2021.

IP address updates
  • This information is subject to change, and we recommend that you subscribe to our announcements page in the Code42 community to learn about upcoming changes to IP addresses. See the table below for the revision history of this article.
  • To ensure uninterrupted connectivity to the Code42 cloud, you should have opened your firewall to all available IP addresses listed above before August 11, 2020. For more information, see IP address updates in August 2020.

Revision history

The table below lists previous updates to this page. To learn more about IP address and network port updates, go to

Date Updates
May 5, 2021

Added the following IP address ranges to the list of Code42 cloud storage IP addresses:


If your use of Code42 cloud storage was provisioned on or before May 5, 2021, you have until November 5, 2021 to open firewall access to these ranges.

August 12, 2020 Added a note that IP address range is retired.
May 8, 2020

Noted that IP addresses are scheduled to be updated August 7, 2020, and that you should allow inbound requests to all Code42 IP addresses. In addition, inbound rules for  . For more information, see IP address updates in August 2020.

January 7, 2020 Removed mention of port 4282 because port 4282 is no longer supported.
September 6, 2019

Added new inbound IP address ranges: and 

March 13, 2019
  • Added new IP address range:
  • Published all IP addresses. Previously, IP addresses were only available by contacting our Customer Champions or your Customer Success Manager (CSM).