Ntfy-On-Start

Ntfy-On-Start is a lightweight container that sends an ntfy push notification the moment it starts, letting you know when a headless server or virtual machine…

  • Communication
  • Other
  • Tools & Utilities
Ntfy-On-Start is a lightweight container that sends an ntfy push notification the moment it starts, letting you know when a headless server or virtual machine has booted and is ready to connect, including after a Wake-on-LAN (WOL) request.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

28/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
351 install platform, install notes, Docker image
Light to run
95307 MB minimum RAM, runs on ARM

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 27 days ago

No GitHub repository data collected yet.

Checked 54 days ago - source: GitHub (nwithan8/docker-ntfy-on-start)

Resources & Compatibility

Minimum requirements: 307 MB RAM, 1 CPU core(s), 5 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start the server and pick a port Run ntfy serve to start the notification server; it listens on port 80 by default, or you can use ntfy serve --listen-http :8080 to switch to port 8080. If the port you chose is blocked or wrong, your phone or other devices won't be able to connect. source
  • Send a test notification Install Apprise with pip3 install apprise, then send a test with apprise -b "Hi there" ntfys://mytopic. Apprise is a helper program, and this quick test helps you spot connection or topic problems before relying on real alerts. source
  • What this does This container has no server or port of its own - it sends a single ntfy notification when it starts, so deploy it alongside the ntfy service you already use. source

Fetched 39 days ago - each note links to its source

Alternatives (5)

  • Gotify - Gotify is a self-hosted server for sending and receiving push notifications.
  • Healthchecks.io - Healthchecks.io is a service for monitoring cron jobs and similar periodic processes:
  • Pushbullet - Send links, files, photos, lists, and notes instantly between devices, mirror phone notifications to desktop, and access clipboard syncing…
  • Pushover - Pushover is a simple push notification service that integrates easily into web apps, network monitoring systems, shell scripts, and anythin…
  • ntfy - Ntfy is a simple HTTP-based publish-subscribe notification service that lets you send push notifications to your phone or desktop from any…

Checked 40 days ago - source: AlternativeTo

Common questions

Which ntfy server port should be reachable for Ntfy-On-Start to deliver its startup message?

The ntfy server listens on port 80 by default, or you can run it on another port such as 8080. If the chosen port is blocked or wrong, the phone or other devices won't be able to connect.

How can I verify that my self-hosted ntfy topic will accept a test notification before relying on Ntfy-On-Start?

Install Apprise with pip3 install apprise, then send a test with apprise -b "Hi there" ntfys://mytopic. This quick test helps spot connection or topic problems.

Does the ntfy phone app receive Ntfy-On-Start startup messages by polling?

No, the phone connects to the ntfy server via websockets. It is not polling, though when you open the app it asks the server for messages it has missed.

Why might self-hosted iOS notifications for Ntfy-On-Start not work?

Self-hosted servers may fail if no upstream-base-url is set or the base-url mismatches. The known-issues page points to the iOS instant notifications details for the workaround.

What basic installation issues are mentioned when a self-hosted Ntfy setup is not working?

A YunoHost support thread suggests considering hardware, version, and permissions when diagnosing a broken Ntfy setup.

Answers sourced from docs.ntfy.sh, docs.ntfy.sh, docs.ntfy.sh, forum.yunohost.org, www.reddit.com

Community

Collected 53 days ago - public community threads