Use the following documentation to determine which ports and URLs HelpSystems Insite and different Insite modules use for various tasks. This information will, for instance, allow you to create firewall exclusions to allow Insite to function. Some helpful firewall links for Windows Server and Linux.

General Insite Server Ports

The ports listed below are the default port numbers presented during installation. The port numbers can be changed during installation.

  • 3029 - Insite Server Shutdown Port
  • 3030 - Insite Server Connector Port
  • 5432 - Database Port

Insite Analytics Ports

The ports listed below are the default port numbers presented during installation. The port numbers can be changed during installation.

  • 9000 - Insite Analytics Shutdown Port
  • 9001 - Insite Analytics Connector Port

Insite Integration Service Ports

Insite Integration Services has different default ports, but they can be changed during installation. These are the service ports that need to be exposed for other services to be able to interact with them. If these ports are closed or blocked by firewall restrictions, Insite will not function correctly. You may need to create firewall exclusions for these ports.

  • 5432 – Database Port - The database will be installed with the Integration Services component.  The port needs to be open so Insite can read the database.
  • 8998 – Server Port - Integration Services starts a HTTP web server to handled product registration.  
  • 9092 – Message Broker Port - Used for the Insite messaging service.  Services need to be able to send messages to function.
  • 2181 – Coordinator Port - Used to coordinate messages.
  • 8200 – Secure Storage Port - Needs to be open for future component access.

Insite to IBM i Connections

Note: This section applies to all Insite modules that connect to IBM i.

HelpSystems Insite uses the following ports on the IBM i:

449 446
8470 8471
8472 8473
8474 8475
8476  

Insite uses IBM's Toolbox. For more information on which ports are used for IBM's Toolbox, see Toolbox for Java and JTOpen on their website.

Your IBM connections won't work if the above ports are closed.

Browser Connection

The connection between the Insite server and a user accessing Insite through a browser is via HTTP over port 3030 by default. If Insite is configured to use SSL (see Configuring Insite for SSL and Setting up Insite with a Trusted Certificate), the connection is via HTTPS over port 8443.

Deployment Manager

  • Deployment Manager uses the following URL patterns and port combinations:

    https://s3.amazonaws.com/hsinsite/*

    https://s3.amazonaws.com/hsinsite/deployment.json is hard coded and has the following URLs inside it:

    "baseUrl" : https://s3.amazonaws.com/
    "baseDownloadUrl" : hsinsite/download/
    "hsWebsiteUrl" : http://www.helpsystems.com/
    "insiteUrl" : hsinsite/deployment.json	

    Loading and staging products (which uses secure port 443) won't work if these URLs are inaccessible, and pages in Deployment Manager may fail to load properly.

  • ELA (Enterprise License Agreement) functionality inside Deployment Manager uses this URL pattern:

    https://lss.helpsystems.com

    Licensing products and adding ELA keys (which uses secure port 443) won't work if this URL is inaccessible.

Robot Network

Insite uses a peer connection to link to servers that have a Robot Network host or node installed. For this to work, the following ports must be open on the IBM i:

  • 7474: sends and receives data on the primary host system

  • 4444: sends and receives data from the host system

The Robot Network host appears offline if either of these ports are closed.

Automate Ops Console

Automate Ops Console has default ports (9708 is the default when setting up a product connection), but it can be changed when configuring the Automate Ops Console connection. The connection appears offline or is unable to connect if the specified port is closed.

Automate Schedule Ops Console

Automate Schedule Ops Console has default ports (8008 and 7432 are the defaults when setting up a product connection), but they can be changed when configuring the Automate Schedule Ops Console connection. The connection appears offline or is unable to connect if the specified port is closed.

GoAnywhere MFT

GoAnywhere MFT has default port (8000 is the default when setting up a product connection), but it can be changed when configuring the GoAnywhere MFT connection. The connection appears offline or is unable to connect if the specified port is closed.

Intermapper

Intermapper has default port (80 is the default when setting up a product connection), but it can be changed when configuring the Intermapper connection. The connection appears offline or is unable to connect if the specified port is closed.

Powertech Event Manager

Powertech Event Manager has default port (19180 is the default when setting up a product connection), but it can be changed when configuring the Powertech Event Manager connection. The connection appears offline or is unable to connect if the specified port is closed.

Vityl IT & Business Monitoring

Vityl IT & Business Monitoring has default port (19180 is the default when setting up a product connection), but it can be changed when configuring the VItyl IT & Business Monitoring connection. The connection appears offline or is unable to connect if the specified port is closed.

Powertech Antivirus

This is the mapping of the services HelpSystems Insite and Powertech Antivirus run and the ports used. The ports shown are default ports. If they are already in use during the installation, a different port is used.

The following ports must be open in order for Insite to function:

  • 8998: HTTP port used for product registration (can be selectively enabled in firewall)
  • 3030: Insite web port
  • 9092: Communication port

The remaining ports are only used for local communication under a single server Insite installation.

Single server configuration

Dual server configuration

For a dual server installation, the database port (5432 by default) also needs to be open.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: April 09, 2019