Legacy Manual

Legacy Web UI Remote Access

PingPlotter does not currently have internal support for remote access to the web UI. However, there are alternative solutions available.

Creating a reverse proxy server using NGINX

Begin by downloading NGINX and configuring it as normal. Within the default nginx.conf file, use the following code. You should replace 'localhost' and the listen port (9999) with whatever values you need.

server {
listen 9999;
server_name localhost;
location / {
proxy_pass http://127.0.0.1:7464/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
}

Note

The last three lines in this configuration technically are not necessary. However, without them, PingPlotter will communicate using long-polling rather than WebSockets, which dramatically slows down the responsiveness of the web UI.

If this configuration does not work for your situation, the following configuration also achieves a working reverse proxy by utilizing WebSockets:

map $http_upgrade $connection_upgrade {
default upgrade;
' ' close;
}
server {
listen 9999;
server_name localhost;
location / {
proxy_pass http://127.0.0.1:7464/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
}
}

If you're looking to set up the web UI with HTTPS and are running Windows (macOS coming at a later date), we have an excellent resource for that in the PingPlotter manual.

Using IIS as a web server

PingPlotter 5 uses an architecture that is incompatible with VBScript or Classic ASP. Currently, PingPlotter 5 is also incompatible with IIS.

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