Open topic with navigation
Private Node Server provides a web-based Control Panel where you can configure the private node settings and see the monitoring status. Control Panel is the default GUI of Private Node Server. You can also access the Control Panel from any browser on the same network, using this URL:
where <IP address> is that of your private node. Use https for Private Node Server 2.x and http for versions up to 1.9.
The default login and password are:
insiteadm / 1nSitePa$$ for Private Node Server 2.x
admin / password for earlier versions.
Make sure to change the default password to something more secure.
* Features available only after Private Node Server registration.
† Features also available in the Private Node Server console.
This is the main page you see when you log in to Private Node Server Control Panel.
It shows the following information:
Note: Activity timestamps are in the time zone selected in your AlertSite account settings, whereas the private node system time displayed in the top right of the Control Panel is GMT-based.
The first thing you need to do is to register your Private Node Server in AlertSite UXM. This adds the private node as a new location to your global locations list, so you can use it in your monitors. For step-by-step instructions, see Registering Private Node Server as Location in AlertSite.
Once your Private Node Server is registered, you can change the admin password for logging into the Private Node Server Control Panel. Enter the current password and the new password, and click Apply Changes.
The password can be up to 10 characters long.
In certain cases, if you request technical support for your Private Node Server, our engineers may need remote access to it. Remote access is done via Secure Shell (ssh) with authentication.
You can enable or disable remote access on this page. Access remains open for 12 hours, or until you manually disable it.
Note: Remote access requires that outbound traffic is allowed on port 22 to insiterepair.alertsite.com.
On this page you can see your Private Node Server software version and check for updates.
If an update is available, select it and click Upgrade. If multiple updates are available (for example, 1.7.1, 1.7.2 and 1.8.0), install the next major revision (1.8.0).
To reboot the private node, open this page and click Reboot. Monitoring will not occur while the node is rebooting.
To check when the node is back up, you can:
Available only in Private Node Server versions up to 1.9, this page lets you reset your private node to its default settings. This clears any configuration changes you made (such as network and proxy settings, and so on), and deletes any log data collected. It is a complete reset, as if you just deployed the private node.
Important: Only do this if you have been instructed to by AlertSite Customer Support.
After the reset, you will need to re-register your private node using its existing location ID. You can find this ID in AlertSite UXM: go to > Account, click Manage InSite / Private Node Locations, then click next to the location name.
By default, Private Node Server obtains its IP address through Dynamic Host Configuration Protocol (DHCP). If you need to use a static IP address, you can configure it on this page:
(Optional) To add additional DNS servers, click Advanced DNS Configuration and enter their addresses.
To remove an added name server, clear its entry.
If you connect to Internet via proxy, specify the proxy settings on this page. Private Node Server supports HTTP, SSL, and SOCKS proxy.
Proxy configuration is used for private node registration, reporting to the AlertSite platform, and also for Web URL, DéjàClick Firefox and SoapUI monitors.
To configure the proxy:
Specify both the HTTP Proxy and SSL Proxy. If you need ServerAgent, specify the SOCKS proxy, as well.
In Private Node Server 2.1, you can use both the host name and IP addresses for proxy. Earlier versions require IP addresses.
If your proxy requires authorization, enter the Userid and Password.
Note: If the Userid includes a domain name, such as DOMAIN\user, you need to use a double backslash: DOMAIN\\user.
To return to the “no-proxy” mode:
Note: Proxy is not used for:
Private Node Server sends email alerts on port 25. If your local network does not allow outgoing connections through the firewall on port 25, you need to specify a mail relay host on your local network to send alerts through.
On this page you can configure the mail relay:
Note: If your mail relay host requires authentication or works over SSL (like Gmail), please contact SmartBear Support for assistance.
Private Node Server does not retry alerts if it cannot reach the mail relay host.
Network Time Protocol (NTP) is a common method to synchronize computer time with public time servers on the Internet. To learn more about NTP, visit http://www.ntp.org.
Private Node Server uses NTP to maintain the system time. It can synchronize with one or two NTP servers. The default servers are:
For Private Node Server 2.x:
For Private Node Server 1.9 and earlier:
If you have an NTP server in your private network or at your ISP, you can use those for greater accuracy. Or you may want to use the NTP servers local to your continent or country. For local NTP servers, use:
where XX is your continent name or two letter country code. For a list of public NTP servers, see http://www.pool.ntp.org/zone/@.
NTP servers for Europe:
Unlike previous versions, Private Node Server 2.1 includes two versions of SoapUI:
On this page, you can choose the version that will be used to run SoapUI monitors on this private node. You may want to use a specific version if your projects run successfully in one version, but not the other, due to some breaking changes.
Note: Earlier versions of Private Node Server include only one version of SoapUI. Private Node Server and InSite v. 1.6–2.0.2 include Ready! API 1.1, and InSite 1.5 includes SoapUI 4.5.
Private Node Server’s system time is GMT and is displayed in the top right corner of the Control Panel.
Maintaining the correct time is important so that your monitoring data has accurate timestamps. Private Node Server synchronizes system time with the public time servers using Network Time Protocol (see NTP Configuration).
If the time difference between the node and the NTP server is large (say, several hours), time will not sync. In this case you need to manually set the system time to the approximate correct time, so the time can start syncing.
You can adjust the system time on this page. Enter the time in GMT (not your local time), and click Apply Changes.
Private Node Server includes the ServerAgent that monitors the node health, such as the CPU, memory and disk usage, and results of the heartbeat check. ServerAgent sends this information to AlertSite, and you can see it in the AlertSite 1.0 console.
For instructions on how to set up the ServerAgent, see Configuring ServerAgent for Private Node Server.
Note: If you need to delete and reconfigure the ServerAgent, you must disable it first in order to register a new ServerAgent.
Use this page to check the connectivity to AlertSite hosts and ports required for proper functioning of Private Node Server (see Network Connectivity). Tests are performed using the network parameters configured for this private node, including the proxy server, DNS server, and so on.
The results are displayed after some time (about a minute). Please do not refresh the page during this time.
If there are problems when connecting to certain hosts, make sure your firewall allows traffic from the private node to these hosts. You can run a detailed traceroute to these hosts in Diagnostics > Diagnostic Tests to see if the problem lies within or outside of your network.
A failed registration check means your private node is not registered yet. If the error appears for a registered node, register it again using its 32-character location ID you can find on the list of your private locations in AlertSite.
Here you can run various tests to check connectivity from the Private Node Server.
Ping – Check if an IP address or domain is accessible.
Note: For lookup, ping and traceroute, enter the domain name without http://.
AlertSite Web Test – Check if a web page is accessible, and measure its response time.
Note: Private Node Server must be registered to use this feature.
On this page you can send your Private Node Server system logs to SmartBear support for troubleshooting. Select the check box next to a log you want to send, then click Send Logs in the top right.
Note: The log files may be large, so please send one at a time and not all at once.
Private Node Server can send alerts via e-mail, SMS, VoIP and SNMP traps. On this page you can send test alerts to verify alert delivery. The page lists all compatible recipients configured in your AlertSite account. Click the recipient in the list to send a test alert to it.