mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1261] Image download issue when not on wifi #891
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#891
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 @witterally on GitHub (Jan 19, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1261
🐞 Describe the bug
I have several notifications set up and within them an image is attached, showing on the alert itself. Typically I'm on Wi-Fi but I've noticed that if an alert comes in while on my mobile network, I'll get a "download failed" error for the image.
💻 Components impacted
Android app
💡 Screenshots and/or logs
Screenshot
Log
🔮 Additional context
Example error from log while connected to mobile network:
NtfyAttachDownload Attachment download failed
Exception:
java.net.UnknownHostException: Unable to resolve host "m.media-amazon.com": No address associated with hostname
at java.net.Inet6AddressImpl.lookupHostByName(Inet6AddressImpl.java:156)
at java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:103)
at java.net.InetAddress.getAllByName(InetAddress.java:1152)
@wunter8 commented on GitHub (Jan 19, 2025):
It's possible your
base-urlconfiguration isn't set correctly. It's used to generate the attachment url. Make sure thebase-urlis a publicly accessible domain name/IP address and port that can be used to access the ntfy server when you're not on WiFi@witterally commented on GitHub (Jan 19, 2025):
Thanks for the reply. I'm using ntfy servers and not self-hosting. Would that still be applicable?
@wunter8 commented on GitHub (Jan 19, 2025):
Oh. No. Using the public instance, image attachments should work fine...
Looking closer at the error, it appears to be a DNS error with Amazon?
I'm not sure why that would be. Attachments are served by the ntfy server, which isn't even hosted on AWS.
These are attached "local files," right? Not just image URL links?
@witterally commented on GitHub (Jan 19, 2025):
Yes they are local. If I take that host address and visit it while on wifi the page resolves and just has a message that says "OK". If I turn wifi off and it's only my cell network, I get a 403 error.
The Amazon link is hosted there because they are alerts for Amazon products via the site.
@witterally commented on GitHub (Jan 19, 2025):
This doesn't seem to be an issue with ntfy itself so I'll get out of your hair. It's possibly something I need to figure out with my mobile network. I was hoping that by changing the DNS it would help but no luck there.
Thanks again!
@witterally commented on GitHub (Jan 19, 2025):
The resolution seems to be enabling mobile background data usage for ntfy in Android. Doh! It's working now.
@wunter8 commented on GitHub (Jan 19, 2025):
Glad you got it figured out!