[GH-ISSUE #1339] IOS does note recieve push #948

Open
opened 2026-05-07 00:29:01 +02:00 by BreizhHardware · 18 comments

Originally created by @Elefai on GitHub (May 15, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1339

Just check it to see! IOS systems does not be notified by ntfy app. Can you check this?

Originally created by @Elefai on GitHub (May 15, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1339 Just check it to see! IOS systems does not be notified by ntfy app. Can you check this?
Author
Owner

@simploai commented on GitHub (May 17, 2025):

https://docs.ntfy.sh/known-issues/

<!-- gh-comment-id:2888246051 --> @simploai commented on GitHub (May 17, 2025): https://docs.ntfy.sh/known-issues/
Author
Owner

@lylebrown commented on GitHub (May 28, 2025):

This seems to surpass the known issues page.

After switching phones (iPhone 14 Pro to iPhone 16 Pro, also with a minor version update to iOS 18.5) I am no longer receiving notifications. I am able to see them after refreshing the ntfy app, but only as items in the main app - there is never a notification.

I've tried reinstalling the app. I've tried both selfhosted and ntfy.sh. Nothing is working.

I'm would be happy to send over logs if there's a way to capture them in the iOS app. But I suspect something weird is going on with the ntfy.sh firebase server or connection.

<!-- gh-comment-id:2914664683 --> @lylebrown commented on GitHub (May 28, 2025): This seems to surpass the known issues page. After switching phones (iPhone 14 Pro to iPhone 16 Pro, also with a minor version update to iOS 18.5) I am no longer receiving notifications. I am able to see them after refreshing the ntfy app, but only as items in the main app - there is never a notification. I've tried reinstalling the app. I've tried both selfhosted and ntfy.sh. Nothing is working. I'm would be happy to send over logs if there's a way to capture them in the iOS app. But I suspect something weird is going on with the ntfy.sh firebase server or connection.
Author
Owner

@paraita commented on GitHub (May 28, 2025):

Noticed the same behavior today on both ntfy.sh and self hosted

<!-- gh-comment-id:2915246622 --> @paraita commented on GitHub (May 28, 2025): Noticed the same behavior today on both ntfy.sh and self hosted
Author
Owner

@benwjr commented on GitHub (May 28, 2025):

i got the same issue

<!-- gh-comment-id:2916134977 --> @benwjr commented on GitHub (May 28, 2025): i got the same issue
Author
Owner

@skjdghsdjgsdj commented on GitHub (May 30, 2025):

Likewise. I'm certain all my settings are correct. Notifications only come through when I manually refresh on iOS. ntfy is otherwise working because running ntfy publish in one terminal window and ntfy subscribe in another shows the message come in immediately.

My ntfy instance is running in a Proxmox LXC as installed via apt in Debian, not Docker. My file permissions look correct. My log shows no errors, just messages like:

INFO Server stats (emails_received=0, emails_received_failure=0, emails_received_success=0,
  emails_sent=0, emails_sent_failure=0, emails_sent_success=0, messages_cached=15,
  messages_published=15, subscribers=1, tag=manager, topics_active=1, users=2, visitors=3)

I'm on iOS 18.5. I uninstalled and reinstalled the app from the App Store and it made no difference. The app is granted notification permission.

iOS is a critical part of my workflow so unfortunately if iOS doesn't work I can't deploy ntfy in my environment.

ntfy apt version:

# apt info ntfy
Package: ntfy
Version: 2.12.0
Priority: optional
Section:
Maintainer: Philipp C. Heckel <philipp.heckel@gmail.com>
Installed-Size: 64.3 MB
Homepage: https://heckel.io/ntfy
Download-Size: 27.3 MB
APT-Manual-Installed: yes
APT-Sources: https://archive.heckel.io/apt debian/main amd64 Packages
Description: Simple pub-sub notification service

My instance is running on ntfy.example.com (obviously not that, but a subdomain of a real one). ntfy.example.com on my LAN points to the LAN IP of my Caddy reverse proxy. Publicly it points to Cloudflare which proxies the traffic to the same reverse proxy. Cloudflare never shows any request, blocked or otherwise. The Caddy logs only show the POST when I do a test publish.

<!-- gh-comment-id:2922793228 --> @skjdghsdjgsdj commented on GitHub (May 30, 2025): Likewise. I'm certain all my settings are correct. Notifications only come through when I manually refresh on iOS. ntfy is otherwise working because running `ntfy publish` in one terminal window and `ntfy subscribe` in another shows the message come in immediately. My ntfy instance is running in a Proxmox LXC as installed via `apt` in Debian, not Docker. My file permissions look correct. My log shows no errors, just messages like: ``` INFO Server stats (emails_received=0, emails_received_failure=0, emails_received_success=0, emails_sent=0, emails_sent_failure=0, emails_sent_success=0, messages_cached=15, messages_published=15, subscribers=1, tag=manager, topics_active=1, users=2, visitors=3) ``` I'm on iOS 18.5. I uninstalled and reinstalled the app from the App Store and it made no difference. The app is granted notification permission. iOS is a critical part of my workflow so unfortunately if iOS doesn't work I can't deploy ntfy in my environment. ntfy `apt` version: ``` # apt info ntfy Package: ntfy Version: 2.12.0 Priority: optional Section: Maintainer: Philipp C. Heckel <philipp.heckel@gmail.com> Installed-Size: 64.3 MB Homepage: https://heckel.io/ntfy Download-Size: 27.3 MB APT-Manual-Installed: yes APT-Sources: https://archive.heckel.io/apt debian/main amd64 Packages Description: Simple pub-sub notification service ``` My instance is running on `ntfy.example.com` (obviously not that, but a subdomain of a real one). `ntfy.example.com` on my LAN points to the LAN IP of my Caddy reverse proxy. Publicly it points to Cloudflare which proxies the traffic to the same reverse proxy. Cloudflare never shows any request, blocked or otherwise. The Caddy logs only show the `POST` when I do a test publish.
Author
Owner

@SlIdE42 commented on GitHub (May 31, 2025):

Same issue (both ntfy.sh and self hosted)...

<!-- gh-comment-id:2924602976 --> @SlIdE42 commented on GitHub (May 31, 2025): Same issue (both ntfy.sh and self hosted)...
Author
Owner

@CrazyBunQnQ commented on GitHub (Jun 10, 2025):

Same issue (both ntfy.sh and self hosted)...

<!-- gh-comment-id:2958879138 --> @CrazyBunQnQ commented on GitHub (Jun 10, 2025): Same issue (both ntfy.sh and self hosted)...
Author
Owner

@sebastianweaver commented on GitHub (Jun 14, 2025):

+1 here. Running self-hosted docker container and pushing through to iOS app. Stopped receiving notifications around the end of May.

<!-- gh-comment-id:2972978066 --> @sebastianweaver commented on GitHub (Jun 14, 2025): +1 here. Running self-hosted docker container and pushing through to iOS app. Stopped receiving notifications around the end of May.
Author
Owner

@CrazyBunQnQ commented on GitHub (Jun 14, 2025):

Same issue (both ntfy.sh and self hosted)...

I solved this problem by sharing to the home screen via Safari and turning on message notifications. The messages will not be delayed by Apple servers. You can directly refer to the official documentation.
image

<!-- gh-comment-id:2972998850 --> @CrazyBunQnQ commented on GitHub (Jun 14, 2025): > Same issue (both ntfy.sh and self hosted)... I solved this problem by sharing to the home screen via Safari and turning on message notifications. The messages will not be delayed by Apple servers. You can directly refer to the official documentation. ![image](https://github.com/user-attachments/assets/f2038381-f08d-4756-a761-368a4b9b59a6)
Author
Owner

@bharathkarumudi commented on GitHub (Jun 22, 2025):

I had exactly same issue, when I switched my phone from iPhone 13 to iPhone 16, 5 month ago. I Googled it, not resolved and I left it.

Today, I noticed when I created a new topic from my phone, I was able to receive push notifications instantly for the new topic, but old topic is still behaving with the same issue.

So I deleted (Unsubscribed) the old topic, and created again from my phone.

I have tested by closing the app on my iPhone, and sent a notification to both topics using curl, and both received instantly.

PS: I am using self hosted ntfy service.

Thanks!

@elefantemarketing @lylebrown @SlIdE42 @CrazyBunQnQ @sebastianweaver @skjdghsdjgsdj @benwjr @paraita @simploai

<!-- gh-comment-id:2994445312 --> @bharathkarumudi commented on GitHub (Jun 22, 2025): I had exactly same issue, when I switched my phone from iPhone 13 to iPhone 16, 5 month ago. I Googled it, not resolved and I left it. Today, I noticed when I created a new topic from my phone, I was able to receive push notifications instantly for the new topic, but old topic is still behaving with the same issue. So I deleted (Unsubscribed) the old topic, and created again from my phone. I have tested by closing the app on my iPhone, and sent a notification to both topics using `curl`, and both received instantly. PS: I am using self hosted ntfy service. Thanks! @elefantemarketing @lylebrown @SlIdE42 @CrazyBunQnQ @sebastianweaver @skjdghsdjgsdj @benwjr @paraita @simploai
Author
Owner

@Elefai commented on GitHub (Jul 2, 2025):

@bharathkarumudi I tried a lot of things but without sucess!

<!-- gh-comment-id:3029470596 --> @Elefai commented on GitHub (Jul 2, 2025): @bharathkarumudi I tried a lot of things but without sucess!
Author
Owner

@victory460 commented on GitHub (Oct 26, 2025):

同样的问题(ntfy.sh 和自托管)...

我通过 Safari 分享到主屏幕并开启消息通知解决了这个问题。消息不会被 Apple 服务器延迟。您可以直接参考官方文档。 image

hello, IOS 18.7.1 not work with safira pwa, how to to next?

<!-- gh-comment-id:3447970701 --> @victory460 commented on GitHub (Oct 26, 2025): > > 同样的问题(ntfy.sh 和自托管)... > > 我通过 Safari 分享到主屏幕并开启消息通知解决了这个问题。消息不会被 Apple 服务器延迟。您可以直接参考官方文档。 ![image](https://github.com/user-attachments/assets/f2038381-f08d-4756-a761-368a4b9b59a6) hello, IOS 18.7.1 not work with safira pwa, how to to next?
Author
Owner

@thefaboss commented on GitHub (Oct 26, 2025):

Hello there,
I'm new to ntfy on iOS and after some readings, here how I manage to have ntfy notifications on iOS 26 with selfhosted docker image:

  1. First, start ntfy with docker and connect to your image :
    docker exec -it ntfy sh

  2. Then, create a couple of private/public keys :
    ntfy webpush keys

  3. Copy them and exit the docker prompt.

  4. Shutdown the docker image

  5. Edit your docker-compose.yml to add the following variables (change values between <>) :

NTFY_UPSTREAM_BASE_URL: https://ntfy.sh
NTFY_WEB_PUSH_FILE: /var/lib/ntfy/webpush.db
NTFY_WEB_PUSH_PUBLIC_KEY: <public_key>
NTFY_WEB_PUSH_PRIVATE_KEY: <private_key>
NTFY_WEB_PUSH_EMAIL_ADDRESS: <email>
  1. Restart ntfy with docker

Now you should receive ntfy notifications on your iOS app if your iOS ntfy user is allowed to :)

<!-- gh-comment-id:3448590256 --> @thefaboss commented on GitHub (Oct 26, 2025): Hello there, I'm new to ntfy on iOS and after some readings, here how I manage to have ntfy notifications on iOS 26 with selfhosted docker image: 1. First, start ntfy with docker and connect to your image : `docker exec -it ntfy sh` 2. Then, create a couple of private/public keys : `ntfy webpush keys` 3. Copy them and exit the docker prompt. 4. Shutdown the docker image 5. Edit your docker-compose.yml to add the following variables (change values between <>) : ``` NTFY_UPSTREAM_BASE_URL: https://ntfy.sh NTFY_WEB_PUSH_FILE: /var/lib/ntfy/webpush.db NTFY_WEB_PUSH_PUBLIC_KEY: <public_key> NTFY_WEB_PUSH_PRIVATE_KEY: <private_key> NTFY_WEB_PUSH_EMAIL_ADDRESS: <email> ``` 6. Restart ntfy with docker Now you should receive ntfy notifications on your iOS app if your iOS ntfy user is allowed to :)
Author
Owner

@CrazyBunQnQ commented on GitHub (Jan 9, 2026):

同样的问题(ntfy.sh 和自托管)...

我通过 Safari 分享到主屏幕并开启消息通知解决了这个问题。消息不会被 Apple 服务器延迟。您可以直接参考官方文档。 image

hello, IOS 18.7.1 not work with safira pwa, how to to next?

Did you not receive an activation notification after adding it to the desktop? After adding it to the desktop, you need to treat it like an app and search for it in the settings to enable its notification permissions

<!-- gh-comment-id:3728674965 --> @CrazyBunQnQ commented on GitHub (Jan 9, 2026): > > > 同样的问题(ntfy.sh 和自托管)... > > > > > > 我通过 Safari 分享到主屏幕并开启消息通知解决了这个问题。消息不会被 Apple 服务器延迟。您可以直接参考官方文档。 ![image](https://github.com/user-attachments/assets/f2038381-f08d-4756-a761-368a4b9b59a6) > > hello, IOS 18.7.1 not work with safira pwa, how to to next? Did you not receive an activation notification after adding it to the desktop? After adding it to the desktop, you need to treat it like an app and search for it in the settings to enable its notification permissions
Author
Owner

@Elefai commented on GitHub (Jan 16, 2026):

@thefaboss Hey thanks but I do use

  - upstream-base-url=https://ntfy.sh
  - NTFY_BASE_URL=https://my.ntfy.website
  - NTFY_UPSTREAM_BASE_URL=https://ntfy.sh
  - NTFY_BEHIND_PROXY=true
  - NTFY_LOG_LEVEL=trace

but it´s not working

<!-- gh-comment-id:3757527689 --> @Elefai commented on GitHub (Jan 16, 2026): @thefaboss Hey thanks but I do use - upstream-base-url=https://ntfy.sh - NTFY_BASE_URL=https://my.ntfy.website - NTFY_UPSTREAM_BASE_URL=https://ntfy.sh - NTFY_BEHIND_PROXY=true - NTFY_LOG_LEVEL=trace but it´s not working
Author
Owner

@thefaboss commented on GitHub (Jan 16, 2026):

@thefaboss Hey thanks but I do use

  - upstream-base-url=https://ntfy.sh
  - NTFY_BASE_URL=https://my.ntfy.website
  - NTFY_UPSTREAM_BASE_URL=https://ntfy.sh
  - NTFY_BEHIND_PROXY=true
  - NTFY_LOG_LEVEL=trace

but it´s not working

That's because you didn't add these lines :

NTFY_UPSTREAM_BASE_URL: https://ntfy.sh
NTFY_WEB_PUSH_FILE: /var/lib/ntfy/webpush.db
NTFY_WEB_PUSH_PUBLIC_KEY: <public_key>
NTFY_WEB_PUSH_PRIVATE_KEY: <private_key>
NTFY_WEB_PUSH_EMAIL_ADDRESS: <email>

Please follow the 6 steps I've described. You have to create private/public keys.

<!-- gh-comment-id:3760804245 --> @thefaboss commented on GitHub (Jan 16, 2026): > [@thefaboss](https://github.com/thefaboss) Hey thanks but I do use > > ``` > - upstream-base-url=https://ntfy.sh > - NTFY_BASE_URL=https://my.ntfy.website > - NTFY_UPSTREAM_BASE_URL=https://ntfy.sh > - NTFY_BEHIND_PROXY=true > - NTFY_LOG_LEVEL=trace > ``` > > but it´s not working That's because you didn't add these lines : ``` NTFY_UPSTREAM_BASE_URL: https://ntfy.sh NTFY_WEB_PUSH_FILE: /var/lib/ntfy/webpush.db NTFY_WEB_PUSH_PUBLIC_KEY: <public_key> NTFY_WEB_PUSH_PRIVATE_KEY: <private_key> NTFY_WEB_PUSH_EMAIL_ADDRESS: <email> ``` Please follow the 6 steps I've described. You have to create private/public keys.
Author
Owner

@Elefai commented on GitHub (Jan 16, 2026):

@thefaboss Hey thanks but I do use

  - upstream-base-url=https://ntfy.sh
  - NTFY_BASE_URL=https://my.ntfy.website
  - NTFY_UPSTREAM_BASE_URL=https://ntfy.sh
  - NTFY_BEHIND_PROXY=true
  - NTFY_LOG_LEVEL=trace

but it´s not working

That's because you didn't add these lines :

NTFY_UPSTREAM_BASE_URL: https://ntfy.sh
NTFY_WEB_PUSH_FILE: /var/lib/ntfy/webpush.db
NTFY_WEB_PUSH_PUBLIC_KEY: <public_key>
NTFY_WEB_PUSH_PRIVATE_KEY: <private_key>
NTFY_WEB_PUSH_EMAIL_ADDRESS: <email>

Please follow the 6 steps I've described. You have to create private/public keys.

Thanks a lot now It´s working!

Btw using the main server to send to IOS will be limited up to 250 requisitons per day?

<!-- gh-comment-id:3762233539 --> @Elefai commented on GitHub (Jan 16, 2026): > > [@thefaboss](https://github.com/thefaboss) Hey thanks but I do use > > ``` > > - upstream-base-url=https://ntfy.sh > > - NTFY_BASE_URL=https://my.ntfy.website > > - NTFY_UPSTREAM_BASE_URL=https://ntfy.sh > > - NTFY_BEHIND_PROXY=true > > - NTFY_LOG_LEVEL=trace > > ``` > > > > > > > > > > > > > > > > > > > > > > > > but it´s not working > > That's because you didn't add these lines : > > ``` > NTFY_UPSTREAM_BASE_URL: https://ntfy.sh > NTFY_WEB_PUSH_FILE: /var/lib/ntfy/webpush.db > NTFY_WEB_PUSH_PUBLIC_KEY: <public_key> > NTFY_WEB_PUSH_PRIVATE_KEY: <private_key> > NTFY_WEB_PUSH_EMAIL_ADDRESS: <email> > ``` > > Please follow the 6 steps I've described. You have to create private/public keys. Thanks a lot now It´s working! Btw using the main server to send to IOS will be limited up to 250 requisitons per day?
Author
Owner

@wunter8 commented on GitHub (Jan 17, 2026):

If you're using a self-hosted PWA, the message limit is configurable on your server.

If you're using the native iOS app or the ntfy.sh PWA, you're limited to 250 messages/day on the free/anonymous tier (even if you use your self-hosted server in the native iOS app since message IDs are related through the public ntfy.sh server)

<!-- gh-comment-id:3762424370 --> @wunter8 commented on GitHub (Jan 17, 2026): If you're using a self-hosted PWA, the message limit is configurable on your server. If you're using the native iOS app or the ntfy.sh PWA, you're limited to 250 messages/day on the free/anonymous tier (even if you use your self-hosted server in the native iOS app since message IDs are related through the public ntfy.sh server)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#948
No description provided.