ISPConfig – Hosting Control Panel

The ISPConfig Monitor App for Android is for all servers, not only for servers running ISPConfig. With the ISPConfig Monitor App, you can check your server status and find out if all services are running as expected. You can check TCP and UDP ports and ping your servers. In addition to that you can use this app to request details from servers that have ISPConfig installed (please note that the minimum installed ISPConfig 3 version with support for the ISPConfig Monitor App is 3.0.3.3!); these details include everything you know from the Monitor module in the ISPConfig Control Panel (e.g. services, mail and system logs, mail queue, CPU and memory info, disk usage, quota, OS details, RKHunter log, etc.), and of course, as ISPConfig is multiserver-capable, you can check all servers that are controlled from your ISPConfig master server.

Price

The ISPConfig Monitor App is available for EUR 3.99.

Download

The ISPConfig Monitor App can be downloaded from the Android Market – search for “ISPConfig Monitor” in the Android Market or use this link from your Android phone:

market://search?q=pname:org.ispconfig.monitor

You can also use this QR code (to read this code, you must have a barcode scanner app installed, e.g. like the free Barcode Scanner):

Usage

(If you want to use the ISPConfig Monitor App to fetch details from your ISPConfig servers, you must at least have ISPConfig 3 version 3.0.3.3 installed! Checking TCP/UDP ports and pinging is independent from ISPConfig which means you can use these features to check every host.

To fetch details from an ISPConfig 3 server, you must define a token in the ISPConfig control panel under System > Interface Config > Misc > Monitor keyword:

)
To add/modify/delete servers, click on Settings:

From there, follow the respective link (Add Server/Modify Server/Delete Server):

The Add Server/Modify Server form is structured as follows:

• Hostname (without http://): Fill in the hostname of the server to monitor (without http://), e.g. server1.example.com
• TCP Ports (comma-separated list): If you want to check TCP ports, fill them in here. You can fill in one or more TCP ports (separated by comma, e.g. 25,80,443). Leave this field empty if you don’t want to check any TCP port. Common TCP ports are listed below the form.
• UDP Ports (comma-separated list): Like TCP Ports, but for UDP.
• Do Not Ping Host/Ping Host: Select if you want the app to ping the host and display the outcome.
• Do Not Poll ISPConfig/Poll ISPConfig (If Installed): If the server hosts a master ISPConfig 3 installation, you can make the app display all items from ISPConfig’s Monitor module (e.g. services, mail and system logs, mail queue, CPU and memory info, disk usage, quota, OS details, RKHunter log, etc.), and it can do this for the master server itself and all ISPConfig slave servers controlled by the master (if any). (It is not possible to monitor a slave server only; you always have to fill in the master server to monitor a slave.) If you select to poll ISPConfig, three more form fields will be displayed:
• ISPConfig Token: Fill in the token that you specified for the ISPConfig master server in the ISPConfig control panel under System > Interface Config > Misc > Monitor keyword (see chapter 4.9.2.4 in the ISPConfig 3 Manual).
• ISPConfig Port (If Not 8080): If you have configured the ISPConfig 3 Control Panel to use a different port than 8080, fill in this port here (if you use the standard port 8080, you can leave this field empty).
• ISPConfig Does Not Use SSL/ISPConfig Uses SSL: If you have configured ISPConfig 3 to use https (SSL) instead of http, select ISPConfig Uses SSL here. Please note that ISPConfig 3 must use a trusted SSL certificate then; if you use a self-signed certificate, this app will not be able to connect to ISPConfig (more details in the HTTPS/SSL chapter at the bottom of this page).

After you have added the first server, you can find it on the first panel of the app (use the Back button to get there):

To monitor it, just tap on it. This will bring you to the panel with the monitoring results (TCP ports, UDP ports, ping outcome, ISPConfig Monitor) depending on what you defined for this server (please note that all monitoring results are cached for one minute, so if you modify a server – e.g. add a port, enable/disable pinging, etc. – you might have to wait a minute until your changes take effect in the monitoring results):

If output from the ISPConfig Monitor is shown, this output has two further drop-down menus:

The first drop-down menu contains all servers (master and slave) controlled by ISPConfig (if there are no slaves, just the master is listed here). If you select a different host than the one currently selected, the app will automatically load and display output for that host.

The second drop-down menu lists all the items that can be displayed (e.g. services, mail and system logs, mail queue, CPU and memory info, disk usage, quota, OS details, RKHunter log, etc.). If you select a different item than the one currently selected, the app will automatically load and display that output.

HTTPS/SSL

Trusted SSL Certificate

If you have configured ISPConfig 3 to use https (SSL) instead of http, you must use an SSL certificate from a trusted CA – if you use a self-signed certificate, the ISPConfig Monitor App will not be able to connect to ISPConfig!

If you use a trusted SSL certificate, you must select ISPConfig Uses SSL in the settings of the ISPConfing Monitor App (see the Usage chapter).

Self-Signed SSL Certificate

If you use an untrusted (self-signed) SSL certificate, there’s a workaround to make the ISPConfig Monitor App work with your ISPConfig installation. Simply create a non-SSL vhost explixitly for the monitor.php script on port 8082 on your ISPConfig master server (we have prepared such a vhost configuration for you; you can download it from http://www.ispconfig.org/downloads/ispconfig_monitor_app/ispconfigmonitorappnonssl.vhost for ISPConfig 3.0.5 and later and from http://www.ispconfig.org/downloads/ispconfig_monitor_app/ispconfigmonitorappnonssl.vhost_pre3.0.5 for ISPConfig 3.0.3/3.0.4).

On Debian and Ubuntu, you can create such a vhost as follows:

(Make sure you are logged in as root; on Ubuntu you can run

sudo su

to become root.)

For ISPConfig 3.0.5 and later:

cd /etc/apache2/sites-available/
wget http://www.ispconfig.org/downloads/ispconfig_monitor_app/ispconfigmonitorappnonssl.vhost
cd /etc/apache2/sites-enabled
ln -s /etc/apache2/sites-available/ispconfigmonitorappnonssl.vhost 000-ispconfigmonitorappnonssl.vhost
/etc/init.d/apache2 restart

For ISPConfig 3.0.3/3.0.4 and later:

cd /etc/apache2/sites-available/
wget -O ispconfigmonitorappnonssl.vhost http://www.ispconfig.org/downloads/ispconfig_monitor_app/ispconfigmonitorappnonssl.vhost_pre3.0.5
cd /etc/apache2/sites-enabled
ln -s /etc/apache2/sites-available/ispconfigmonitorappnonssl.vhost 000-ispconfigmonitorappnonssl.vhost
/etc/init.d/apache2 restart

In the ISPConfig Monitor App, you must then specify 8082 as the ISPConfig Port and select ISPConfig Does Not Use SSL (see the Usage chapter).