Self-hosting ntfy for Push Notifications

Table of Contents

• Table of Contents
• Introduction
• Common Issue: ntfy Not Working on HTTP
• Hosting ntfy with Caddy
  • Docker Compose Configuration
  • Caddy Configuration
• Mobile Setup
• Integration Example: Radarr
• Conclusion

Introduction

ntfy is a simple, lightweight notification service that allows you to send push notifications to your devices. This guide will walk you through self-hosting ntfy and integrating it with other services.

Common Issue: ntfy Not Working on HTTP

ntfy requires HTTPS for security reasons. We’ll address this by using Caddy as a reverse proxy.

Hosting ntfy with Caddy

Docker Compose Configuration

networks:
  caddy_net:
    external: true
    name: "caddy_net"

services:
  ntfy:
    image: "binwiederhier/ntfy:latest"
    container_name: "ntfy"
    command: ["serve"]
    environment:
      - "TZ=UTC"
      - "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
    networks:
      - "caddy_net"
    ports:
      - "8080:80/tcp"
    restart: "unless-stopped"
    user: "1000:1000"
    volumes:
      - "/etc/ntfy:/etc/ntfy"
      - "/var/cache/ntfy:/var/cache/ntfy"

Caddy Configuration

Add this to your Caddyfile:

ntfy.your-domain {
    reverse_proxy ntfy:80
}

Mobile Setup

1. Subscribe to a topic:

2. Test the notification by curl:

   curl -d "Hello World" ntfy.yourdomain.com/admin
   

3. Or Push notification via ntfy dashboard:

4. Mobile notification result:

Integration Example: Radarr

1. Configure Radarr to use ntfy:

2. Radarr notification result:

Conclusion

By self-hosting ntfy, you can have a secure, private notification system for various services. This setup using Docker and Caddy ensures HTTPS support and easy integration with other self-hosted applications.