mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1655] Unknown Host Exception on Android native app; only reboot of phone resolves it. #1154
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#1154
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 @DAE51D on GitHub (Mar 14, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1655
Something changed recently with the Android native app (past few weeks maybe?).
I have
ntfyrunning in an LXC on Proxmox. It has always been stopped for a backup every night then restarts. It has a static IP and gets the DNS http://ntfy.home.lan/ always too. However inspite of that, the app every morning now tells me it can't connect. The web page works fine (so DNS does resolve)Force stopping the app (or clearing app cache even) does NOT resolve this. Stopping and restarting the LXC also does not seem to fix the issue (but the LXC isn't the problem I don't think either). The ONLY way I've found that resolves this is to reboot my Samsung Galaxy S23 Ultra phone.
Again, this has NEVER been a problem with the app until recently. My proxmox backup of the LXC has been that way for years now (so that hasn't changed either). I'm using a Unifi DSM if that matters, but again, same as it always was and the DNS name is coming from Proxmox LXC name anyways (as any other LXC name is assigned). And also again, same phone resolves the hostname from Chrome, it's ONLY the native app that loses it... I'll also point out that other LXCs like my Arrstack/Plex, HomeAssistant, etc. ALL are part of this same nightly backup and no other app has these troubles to re-connect to the LXC host after it stops/backups/restarts.
I see this error in the app...
Here's Chrome on Android to my WEB http://ntfy.home.lan/ LXC works fine.

@binwiederhier commented on GitHub (Mar 14, 2026):
This is a DNS issue on your phone, not ntfy. ntfy uses a very common HTTP client (OkHttp) and it has not changed. "No address associated with hostname" is a dead givaway.
The "Connection lost" alert is new, which is probably why you are noticing this now. Feel free to join the Discord/Matrix and we'll help you trouble shoot.
@DAE51D commented on GitHub (Mar 16, 2026):
perhaps, but this is literally the ONLY android app that exhibits this problem. And again, the DNS resolves just fine from the same phone to the web ntfy server via Chrome... This also didn't used to happen; I hear what you're saying about "connection lost" being new, but I never had any troubles getting alerts and I use this app a LOT for my "arrstack" and other services so alerts come in all day long many times... or did.
@crispybegs commented on GitHub (Mar 18, 2026):
I just started getting this yesterday for the first time ever, also on an android phone. nothing's changed with my DNS or anything else.
my ntfy works fine on web etc and all parts of the stack seem fine, so it does seem like something's changed in the app behaviour
@cravl-dev commented on GitHub (Mar 30, 2026):
I just started experiencing what appears to be the same issue today. I'm using the default server; the error persists across network changes, private DNS on/off, cache clears, and force stops. Websocket or JSON stream doesn't matter either. Works fine in browser.
Weirdly, it sometimes crashes on me when I change a setting, here's one of those crash logs from when I toggled from WS to JSON stream in case it's related: https://paste.crdroid.net/geJIyM
Details
This is a log of the ntfy Android app. The log shows up to 1,000 entries. Server URLs (aside from ntfy.sh) and topics have been replaced with fruits 🍌🥝🍋🥥🥑🍊🍎🍑.Device info:
ntfy: 1.24.0 (fdroid)
OS: 4.9.227crDroid7+-g3b6d947d3274
Android: 11 (SDK 30)
Model: fajita
Product: OnePlus6T
Settings:
Logs
@DAE51D commented on GitHub (Apr 13, 2026):
I think this is websockets related and like something doesn't reset the socket (port) or whatever it needs and keeps trying to hang on to the old one even though the ntfy server has restarted because I noticed I can toggle my Wi-Fi on and off on the phone and that also seems to help fix it sometimes.
That's what also explain why we don't see this issue if the app uses HTTP(S) as that connection is new each time. NTFY is special in using websockets (and for good reason).
Is there a way the app can detect the disconnect and refresh something to get the new socket?