Registering Private Node Server as Location in AlertSite

Before you can run monitors on your Private Node Server, you need to register it in your AlertSite account. This adds the private node to your list of monitoring locations, so you can use it with your monitors.

Note: Before you can register a private node, make sure your firewall allows traffic to the hosts and ports listed in Network Connectivity.

In This Guide

Registering Private Node Server

  1. From the AlertSite UXM top menu, select Profile > Account.
  2. Click the Manage InSite / Private Node Locations tile.

    Manage private locations

  3. In the dialog that opens, click New InSite Location.

    Adding a new private location

  4. Enter the location parameters:

    Location name and parameters

  5. Click Add.
  6. This will generate the Location ID. Copy this value – you will need it later.

    Location ID

  7. Navigate to http://<IP address>, where <IP address> is the IP address of your private node.
  8. Log in. The default login and password are:
  9. From the top menu, select Manage InSite Location > Register Location.

    'Register Location' menu command

  10. Enter your AlertSite Login and Password, and the Location ID that you copied from AlertSite.

    Register Private Node Server

  11. Click Register.

  12. You should see a message informing you that the location has been registered successfully.

    Your InSite by AlertSite has been successfully registered

  13. Now when you select locations for a monitor, you will see your private location in the list.

    Private location in the locations list

Verifying That Private Node Server Is Registered

When Private Node Server is registered properly, its version number shows up in your list of private locations in Profile > Account > Manage InSite / Private Node Locations.

Private Node Server software version

The Control Panel (web interface) of your Private Node Server should also display the location name and number:

Location name and number


If there is a problem registering your private node, make sure your firewall allows traffic from the node to the hosts and ports listed in Network Connectivity. If you use Private Node Server 2.0.2 or later, you can test the connection by using the Diagnostics > Connection Tests page in the node’s Control Panel (web interface).

What’s Next

There are a few more things left to do to have your Private Node Server truly up and running:

See Also

© 2017 SmartBear Software. All rights reserved.      Terms of Use · Privacy Policy