Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Securing the Controller

If you plan on using the Uptime Controller by integrating API functions with the Uptime Infrastructure Monitor Web interface, consider doing the following to prevent several common browser-related warnings when navigating secure and non-secure pages within the same web page:

  • Enable SSL for the Uptime Infrastructure Monitor Web interface, using the instructions found in Implementing SSL for the Web Interface.
  • Purchase a valid SSL certificate for the Uptime Infrastructure Monitor Web interface to avoid warnings about a self-signed certificate in the browser.
    The Controller installs an unsigned and unverified certificate as part of its installation process. For installations in a production environment, a valid key should be purchased and installed on the Controller.

Reflecting Configuration Changes in the Proxy

As part of the Uptime Infrastructure Monitor installation process, a proxy is configured in the <uptimeDirectory>\apache\conf\httpd.conf file. This provides ease of use with the Uptime Controller, as it simplifies many API programming tasks, and helps to ensure the Controller remains secure.


After making any change, restart the Uptime Web Server service (on the correct Uptime Infrastructure Monitor instance, if applicable) to apply these changes. Then verify that you correctly configured the proxy by browsing to https://<uptimeMonitoringStation>/api. The behavior should be identical to browsing to the Uptime Controller at https://<uptimeController>/api.

Controller Configuration Parameters

The following list details several common Uptime Controller configuration tasks.