---
title: "Catchpoint Enterprise Nodes Prerequisites"
slug: "catchpoint-enterprise-nodes-prerequisites"
updated: 2025-03-07T17:20:11Z
published: 2025-03-07T17:20:11Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Catchpoint Enterprise Nodes Prerequisites

## Introduction

Catchpoint Enterprise Nodes allow you to perform synthetic monitoring from locations within your organization. They are typically deployed as physical or virtual appliances in data centers, branch offices, call centers, or brick-and-mortar stores.

When it comes to deploying Enterprise nodes, there are many layers of complexity in a node's environment that may require changes to work with the Catchpoint node software. These layers include but are not isolated to:

- Operating Systems
- Firewall
- Policies
- Proxy
- Third-party software
- Infrastructure security policies

### Here is a list of factors Catchpoint do not control when nodes are deployed:

- **Customer Locations**  

Network architecture, security policies, device(s) policies, active   directory, authentication and proxy settings may vary across   locations.  

1 - Changes made in your network or security polices can impact node   performance.  

2 - URLs that are to be tested need to be mde accessible from the   node.
- **Browser**  

We do not have control over the defects or issues across browsers.
- **Operating System**  

We are not responsible for any issues with operating   system patches or defects.
- **Updates** We are not responsible for any issues due to security patches, OS updates, browser updates or features the Catchpoint node relies on.

### As there are many factors that are outside of Catchpoint's control, we can assist with node troubleshooting as far as the items documented in the following checklist.

## **Checklist:**

- **Whitelisting Catchpoint and testing URLs and IPs**  

Security policies in your environment should allow the node to   communicate with our Command and Control servers.  

1 - Catchpoint URLs and IP addresses: [Enterprise Node Command & Control](/v1/docs/enterprise-node-command-amp-control)  

2 - Customers must also whitelist the URLs they would like to   synthetically test on your environment.
- **Open the following ports** Our services communicate using the following ports and they should   be explicitly available for our services.
  - 80: If you have another service already running on port 80, then   this will likely interfere with Catchpoint services.
  - 443: HTTPs port should be opened for our services.
  - 50120: This port only needs to be open when troubleshooting via a   Catchpoint debugging tool. It is sufficient to allow only localhost   access to this port.
- **Proxy setup** Customers should confirm whether a user on the server can use Chrome to go through the proxy and reach the URLs you would like to   test. If the Node cannot reach the URL, our services/software on the node   will not be able to reach the URL either.
  - Proxy supported: **WPAD, PAC, or Fixed proxy** We do not support other types of proxies today.
- **3rd party Software/Framework/Libraries** Security policies in your environment should allow the node to install 3rd party software/Frameworks/Libraries to be installed on   the node.
  - Allow the node to use administrative privileges
  - Allow our node to use certain settings, which are not customer   configurable.