← Documentation: Menu Order Push Notifications


The tunnel gives mobile devices an HTTPS URL for your ntfy server. This example assumes cloudflared runs on the host and can reach ntfy at localhost:8095.

1. Prepare a tunnel

Use a Cloudflare-managed domain and an existing tunnel with its credentials file. For a new tunnel, follow Cloudflare's creation guide first.

If cloudflared runs in Docker, use the service name and port reachable from its Docker network instead of host localhost.

2. Route the ntfy hostname

Add the ntfy ingress to /etc/cloudflared/config.yml, preserving other routes and the final fallback:

tunnel: YOUR_TUNNEL_NAME
credentials-file: /root/.cloudflared/tunnel-credentials.json

ingress:
  - hostname: n8n.YOUR_DOMAIN.com
    service: http://localhost:5678

  - hostname: ntfy.YOUR_DOMAIN.com
    service: http://localhost:8095       # ← ntfy port

  - service: http_status:404

Restart the host service with systemctl restart cloudflared. Configure the ntfy DNS CNAME to YOUR_TUNNEL_ID.cfargotunnel.com with proxying enabled.

Set the same public hostname in ntfy's base-url.

3. Verify the actual client path

Open https://ntfy.YOUR_DOMAIN.com/v1/health; a healthy server returns {"healthy":true}. Then test authenticated publishing and mobile subscription on your protected topic. Health alone does not verify permissions or delivery.

Keep ntfy authentication enabled. An interactive browser-login gateway can interrupt mobile subscriptions; clients must be able to reach ntfy using their configured credentials.

Continue with 03 - Setup the n8n Workflow.