mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #635] Healtcheck with custom listen-http #473
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#473
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Andersbiha on GitHub (Feb 23, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/635
I'm running Ntfy in a docker-compose setup with Traefik in front.
Upon upgrading from
1.31.0to2.0.1I'm no longer able to access Ntfy through Traefik.I've traced the issue down to the container health checks added in #555.
The health check doesn't take the
listen-httpsetting into account, causing issues for those of us who's not running Ntfy onlocalhost:80.This issue is easily fixed by either disabling the health check or overriding the default health check URL (See https://docs.docker.com/compose/compose-file/compose-file-v2/#healthcheck).
@binwiederhier commented on GitHub (Feb 23, 2023):
Do you suggest I remove the HEALTHCHECK in the Dockerfile entirely? Or let people override it like you did? Maybe this can be added to the docs somewhere?
I am leaning towards removal entirely, honestly. The healthcheck doesn't add much.
@Andersbiha commented on GitHub (Feb 24, 2023):
I would remove it and add a section to https://docs.ntfy.sh/install/#docker describing how to configure it.
I suspect leaving it in the Dockerfile is gonna be a source of confusion and it will most likely affect more people than removing it again.
@djraw commented on GitHub (Feb 26, 2023):
Deleting the healthcheck entirely gets my +1
I have a supposedly "unhealthy" ntfy because I don't run it on port 80 outside the container.
As I use watchtower to automatically update, the healthcheck disable or override using composer gets reset on the updates. So I would prefer to remove the healthcheck.
We will notice a not running ntfy container soon enough anyway when scripts fail to send notifications. ;)
@Andersbiha commented on GitHub (Feb 27, 2023):
I quickly whipped together a fix here .
Let me know if you want me to make a PR 👍
@binwiederhier commented on GitHub (Feb 27, 2023):
@Andersbiha That looks great. I'll happily accept that PR.
Sorry for the inconvenience, folks!
@Andersbiha commented on GitHub (Feb 27, 2023):
@binwiederhier Thank you for a great project and the quick merge. 👍