Version 5 Manual

Web Interface

PingPlotter Professional has a built-in web interface, allowing you to view data and access several PingPlotter functions from a web browser without having immediate access to the machine collecting data.

Enabling the built-in web interface

We recommend installing PingPlotter as a service if you're going to use the web interface. This will ensure PingPlotter is running in the background and makes security permissions slightly easier to configure.

To enable the web interface, go to EditOptionsWeb Server and select Enable built-in web server. By default, the web interface is configured to use port 7464, but this may be changed to accommodate your specific network environment. You may also set a login and password for the interface to restrict access.

Accessing the web interface

To access the web interface from your local machine, launch your preferred web browser and navigate to the following address:

http://localhost:[port], where [port] is the port set in the web interface settings.

This should open the PingPlotter web interface. By default, the web interface address is http://localhost:7464.

Using the web interface

The web interface functions almost identically to the PingPlotter application. From the web interface, you can:

  • Add/remove targets
  • Create a custom summary screen (and add/remove targets from it)
  • Add/remove columns and customize column widths
  • Examine a target’s data by:
    • Changing the focus period
    • Changing the period of time on the timeline graph
    • Toggling Timeline Graphs
    • Downloading sample data for analysis within a local instance of PingPlotter
    • Conducting a Whois lookup through www.whois.sc

Shared functionality between PingPlotter and the web interface

The web interface is an extension of the installed instance of PingPlotter, creating a consistent experience between the two. Changes made within the application will be reflected in the web interface (and vice versa).

For example, if someone accessing the web interface starts a trace to a new target, the new target will appear in the Summary window within the PingPlotter application.

There are some PingPlotter functions only accessible through the application:

  • PingPlotter settings, such as Engine settings and named configurations, can only be modified from within the application. However, once a configuration is created, it can be selected from the web interface.
  • PingPlotter alerts may only be set and modified in-app.

Browser requirements

PingPlotter 5's web interface requires that Javascript be enabled. We recommend using at least Chrome, IE11, Firefox 10+, or any other browser less than a few years old.

Web server security settings

PingPlotter’s web interface can be secured via HTTPS with TLS using PingPlotter’s self-signed web certificate, a certificate you provide, or through Let’s Encrypt.

There are important things to consider when using web certificates with PingPlotter:
  • PingPlotter's certificate can be invalidated by changing the password in the application. If this happens, you can delete the certificate from the default data directory - PingPlotter will generate a new one upon startup
  • If changing from one certificate to another (or after generating a new one from default), you will need to clear the browser's cache for it to accept a new certificate
  • If you'd like to store PingPlotter's certificate, navigate to the default data directory and open the certificate file. A password will be required and is located in the server_settings.json file within the same directory
  • Enabling Let's Encrypt will bypass any certificate preferences

Using PingPlotter’s self-signed certificate

To use PingPlotter’s self-signed web certificate, go to EditOptionsWeb Server and select both Enable HTTPS and Force HTTPS.

In certain browsers, you may be prompted with a warning. This is due to how PingPlotter handles administrator privileges. Simply choose to proceed to the localhost destination to access the interface. To avoid this message, be sure to install PingPlotter as a service.

When the web interface is enabled for the first time, PingPlotter will generate its certificate within the default data directory.

Using a self-provided certificate

To use a self-provided web certificate, go to EditOptionsWeb Server and select Enable HTTPS. You will then have the option to Browse to the certificate location or enter its file path manually. You will also be required to enter the password for your selected certificate.

Your certificate must have a private key and use either the .pfx or .p12 file format.

Using Let’s Encrypt

Let’s Encrypt is a free, automated, and open certificate authority that allows you to set up an HTTPS server that automatically obtains a browser-trusted certificate.

Within PingPlotter, go to EditOptionsWeb Server and select Enable HTTPS, then Use Let’s Encrypt. Once enabled, enter your Let’s Encrypt credentials.

Using IIS as a web server

PingPlotter 5 uses a completely different architecture - one that does not work with VBScript or Classic ASP. Currently, it also doesn't work with IIS. If you need IIS (for security, stability, scalability reasons), you might want to keep using PingPlotter V4.

Advanced configurations

Over the years, we know our users have customized the web interface to do things we didn't really design PingPlotter to do - and we've helped with some of this. PingPlotter 5 changes what's possible here. If you're using V4 with modifications to the web interface to allow read-only views, REST calls to add targets, surfacing custom data and similar, please contact us for help. Many things are possible, but it's different than V4.

**The feature in this topic is exclusive to PingPlotter Pro. See our product comparison page for more details**