This article provides a process to configure secure browsing (HTTPS) to the Uptime IM web interface over SSL. The steps are guaranteed to work with up.time 7.3 to Uptime IM 7.6. If you are looking for a similar solution for Uptime IM 7.7 and later, please see Implementing HTTPS Browsing for the Web Interface with Apache 2.4.x.
To configure SSL browsing in the Uptime web interface, you must generate a server certificate, which identifies that server is using SSL for security, and perform some platform-specific configuration. The following steps will cover this process.
Generate or obtain a server certificate
Alternately, you can generate your own non-recognized certificate. A non-recognized certificate is one that does not come from a certificate-issuing authority. To generate a non-recognized certificate, download and install the OpenSSL software. OpenSSL binaries for Windows can be obtained from Shining Light Productions.
Once OpenSSL is installed, enter the following commands (changing <openssl_dir> to the proper path for the OpenSSL installation directory) at the command line to generate the certificate key.
Move the files to the Uptime Infrastructure Monitor directory
Copy the following files to the <uptime_dir>/apache/conf directory where <uptime_dir> is the installation directory of Uptime (the default installation directory is C:\Program Files\uptime software\uptime on Windows and /usr/local/uptime on Linux).
The following changes to the web server configuration file (httpd.conf) will allow it to use SSL.
Open <uptime_dir>/apache/conf/httpd.conf for editing. Where <uptime_dir> appears below, change it to reflect the directory where you have Uptime installed (ex. c:/Program Files/uptime software/uptime). All path slashes in httpd.conf need to be forward slashes (rather than the usual backslash that is used in Windows).
To make browsing to the Uptime UI easy for users, have it listen on the default Uptime UI port, 9999, as well as the typical HTTP and HTTPS ports, 80 and 443.
Above the line "Listen 9999", add the following two lines:
To handle requests on each of these ports, 80, 443, and 9999, and redirect (actually rewrite) them properly, we will leverage the mod_rewrite.so module, so we need to enable it. In the httpd.conf file, uncomment the following two lines.
On Linux installations of Uptime Infrastructure Monitor 7.2 and earlier, the mod_rewrite.so file is not bundled with Uptime Infrastructure Monitor, so it is necessary to download it from here (mod_rewrite.so) and copy it to the <uptime_dir>/apache/modules directory.
Then, in httpd.conf, add the "LoadModule rewrite_module modules/mod_rewrite.so" line after "# LoadModule foo_module modules/mod_foo.so". If issues are experienced with the version of mod_rewrite.so attached, try creating a symlink to the mod_rewrite.so file provided by the Linux distribution instead.
Finally, the last part is to add entries in httpd.conf that will rewrite the requests as HTTPS. At the bottom of the httpd.conf file, add these lines, changing <uptime_dir> to the directory of your Uptime installation. Please note that the following example uses a specific list of ciphers. You can change the list of ciphers according to your security requirements.
Open the <uptime_dir>/uptime.conf file for editing and change the httpContext parameter (which begins with "httpContext=http://") to reflect the use of SSL:
Restart the services
For the changes to take effect, restart the Uptime Data Collector and Uptime Web Server on Windows or uptime_core and uptime_httpd on Linux.