Setup guide
Connect Ack&Relax to your Zabbix 8.0 server in five steps.
Ack&Relax connects to Zabbix 8.0 with an API token. We recommend a dedicated user with only the permissions the app needs. All steps happen in the Zabbix frontend and need a Super admin.
1 Create a user role
- Name
- e.g.
Ack&Relax - User type
Useris enough.- Access to actions
-
Enable the actions you want to use in the app:
- Acknowledge problems
- Add problem comments
- Suppress problems (used for snooze)
- Change severity
- Close problems
- API access
- Enable it.
- API methods
-
Choose Allow list and add:
problem.get event.get event.acknowledge trigger.get host.get hostgroup.get item.get history.getAck&Relax also calls
apiinfo.version, which works without permissions.
2 Create a user group
- Name
- e.g.
Ack&Relax - Host permissions
-
Add the host groups you want to see in the app.
- Read is enough to see problems and data and to acknowledge, comment and snooze.
- Read-write is only needed to close problems or change their severity.
3 Create a user
4 Create an API token
- Name
- e.g.
iPhone - User
- The user from step 3
- Expires at
- Optional
Make sure Enabled is on, then copy the token. Zabbix shows it only once.
5 Connect the app
In Ack&Relax, enter:
- Server URL
- The address of your Zabbix frontend, e.g.
https://zabbix.example.com. The app findsapi_jsonrpc.phpitself. Ack&Relax only connects over HTTPS, so your API token is never sent unencrypted. - API token
- The token from step 4.
Troubleshooting
- “The token’s user isn’t allowed to call …”
- Add the named method to the role’s API allow list (step 1).
- “… enable ‘…’ under Access to actions”
- Enable that action in the role (step 1).
- “Zabbix rejected the API token”
- The token is incomplete, disabled or expired. Create a new one (step 4).
- “Ack&Relax requires Zabbix 8.0”
- Older Zabbix versions aren’t supported.
- A problem or host is missing
- The user group needs at least Read permission on its host group (step 2).
- “Ack&Relax needs an https address …”
- Your Zabbix frontend is only reachable over plain HTTP. Set up HTTPS for it, for example with a certificate from Let’s Encrypt or your company’s CA.
- Certificate errors
- iOS has to trust your server’s certificate. For a private CA, install its profile and enable full trust under Settings → General → About → Certificate Trust Settings.
Still stuck? The FAQ may help, or contact support.