mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #1482] ntfy android problems in logs #1047
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#1047
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 @shaohme on GitHub (Nov 6, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1482
🐞 Describe the bug
I am investigating notification issues with my Element X Android client which involves my Matrix homeserver and a ntfy service I host myself. My Android phone does not always receive notifications from Matrix homeserver to ntfy, it seems. When opening ntfy logs on Android I find lines like these:
I also see connection error lines like these.
This puzzles me because these errors occurs when the smartphone ought to have a stable WIFI or LTE connection to the ntfy server. The reverse proxy error logs on the ntfy server does not show errors, and the access logs only reports the smartphone getting 200, 101 responses as expected.
This is not to imply ntfy has problems related to my Matrix notification issues. I realize Element X has its own problems. I'm merely reporting this issue to ask the community whether these errors are harmless, or a symptom of something else.
💻 Components impacted
GrapheneOS (latest)
ntfy 2.14, behind reverse proxy
ntfy for android 1.17.8
💡 Screenshots and/or logs
ntfy android log (censored)
ntfy3.log
ntfy server log shows no errors, only boring lines like these:
🔮 Additional context
ntfy on android should run battery Unoptimized and with GrapheneOS exploit protections disabled, just to make sure, they are not interfering.
@binwiederhier commented on GitHub (Feb 1, 2026):
java.net.SocketException: Software caused connection abortis typically your phone killing the connection. There is nothing the Android app can do if you have battery optimization turned off. It may also be your proxy not liking long-running connections and killing them every now and then. It should re-connect quickly though.Problems like this are best for trouble-shooting in Discord/Matrix. Feel free to drop in, see https://docs.ntfy.sh/contact/.
@shaohme commented on GitHub (Feb 1, 2026):
It's been a while since I've checked up on this. I'll browse through the logs again and check the reverse proxy timeouts. Thanks for the hints.