GETTING STARTED
Connect Nagios to NagWatch
Set up your Nagios installation on iPhone or Mac and test the connection before using monitoring data and actions.
Not in the App Store yet
NagWatch is being prepared for the App Store. This guide explains the requirements and steps for a direct connection to your Nagios server ahead of release.
What you need
NagWatch connects directly to your Nagios installation. You need your server’s HTTPS address, a Nagios login created for this access and a network path to the server. If Nagios is only available on your company network, your iPhone or Mac must already reach it through LAN, Wi-Fi or your existing VPN. NagWatch does not create a VPN connection.
No account and no connector
Direct access requires neither a NagWatch account nor an additional server installation. The planned push connector is a later addition and is not needed for this setup.
Add a server on iPhone or Mac
On iPhone, open Instances and choose +. On Mac, open NagWatch Settings, go to Servers and choose + there. Enter a valid HTTPS URL, select the appropriate server type and provide the username and password for your Nagios access. Choose Test connection to check authentication, reachability and available data before saving the profile.
The app recognises common Core paths such as /nagios and /nagios4 during connection. Use the Core CGI interface. For Nagios XI, that means its included Core CGI access with Core 4.5.14; a web-only XI login or the XI REST API is not a supported sign-in path.
Confirm certificates deliberately
For a public certificate, NagWatch validates the TLS connection. For a self-signed certificate or private certificate authority, you can confirm that specific certificate after checking its issuer, validity and SHA-256 fingerprint. A changed certificate requires a new confirmation. The app does not provide a blanket exception for arbitrary or expired certificates.
Set up iPhone and Mac separately
Server profiles are set up on each device. The username and password stay in that device’s Keychain and are not synced through iCloud. Your Pro purchase applies to iPhone and Mac with the same Apple Account; it does not transfer the credentials.
Verified compatibility
These statements describe the tested scope. A similar version number alone is not a blanket approval for every installation or permission model.
| System | Access and test coverage |
|---|---|
| Nagios Core 4.5.14 | Verified over HTTPS with Basic authentication; reading, status, groups, history, comments, rechecks, acknowledgements and downtimes in the tested scope. |
| Nagios Core 4.4.6 | Verified over HTTPS with Digest authentication and the tested read and action functions. |
| Nagios Core 4.3.4 | Checked with recorded responses. Full live coverage of every downtime function has not been claimed. |
| Nagios XI 2026R2 | Verified through its included Core CGI access with Core 4.5.14, HTTPS and Basic authentication. XI REST and browser SSO are not supported; other XI versions have not been verified. |
| Other products | Icinga, Checkmk, Thruk, Centreon, Zabbix and other monitoring systems are not currently supported. |
When the connection fails
First check that the HTTPS address is reachable from the same network or VPN and that the login is valid for the Core CGI access. A read-only account can display data but cannot perform write actions such as acknowledgements, rechecks or downtimes. That is expected; the app reflects the permissions provided by the server.
If a certificate changed, review it again instead of using an unsafe exception. For setup questions, contact us at support@nagwatch.de.
Compatibility statements reflect the documented test status as of 13 October 2026.