ntfy notifications
Before you start
- Subscribe to a topic in your ntfy client.
- Choose https://ntfy.sh or an externally reachable self-hosted server. Enter the server URL and topic separately.
- For private notifications, protect the topic and supply an access token with publish permission. Public topics can be read by anyone who knows their name.
The server must be reachable from CertOne over the public internet. Private-network, localhost and reserved addresses are not supported. Use the final server URL directly; redirects are not followed.
Configuration
| Field | Required | Default |
|---|---|---|
| Server URL | Yes | https://ntfy.sh |
| Topic | Yes | — |
| Access token | No | — |
| Priority | Yes | 3 |
Test and enable
- In CertOne, add a notification target and choose this channel.
- Fill in the configuration and send a test message.
- Check that the message arrived at the intended destination, then save the target.
- Select the saved target in the settings for the notification events you need.
A successful API response means the service accepted the request. It does not prove that the final client or mailbox received it. If a request times out, delivery may already have occurred; check the destination before retrying.
Long messages are shortened to fit the channel limit and include a link to the console for full details.
Troubleshooting
- Subscribe to this topic in your ntfy client. Use a private topic with an access token for sensitive certificate alerts; unprotected topics can be read by others.
- Check token permissions, account quota, destination ID and server reachability.
- Sensitive credentials are not included in returned error messages.