[GH-ISSUE #880 ] iOS not pushing notifications. Ntfy needs to be refreshed to view them. #622

Author

Owner

@naxels commented on GitHub (Sep 16, 2023):

I noticed something similar today: iOS itself would show the notification,
however, opening the app (having it open previously + on the subscribed topic)
would not show the notification even upon refresh of the list.

Closing the app & reopening it, would show the notification in the topic.

@naxels commented on GitHub (Sep 16, 2023): I noticed something similar today: iOS itself would show the notification, however, opening the app (having it open previously + on the subscribed topic) would not show the notification even upon refresh of the list. Closing the app & reopening it, would show the notification in the topic.

BreizhHardware commented

Author

Owner

@kevinlutzer commented on GitHub (Sep 17, 2023):

I am experiencing the same issue. I am running in a Kubernetes environment and here is my ConfigMap.

apiVersion: v1
kind: ConfigMap
metadata:
  name: ntfy
  namespace: ntfy
data:
  server.yml: |
    base-url: "https://myurl.com"
    upstream-base-url: "https://ntfy.sh"
    log-level: debug

I was able to refresh the subscription by pulling down on the view in IOS.

@kevinlutzer commented on GitHub (Sep 17, 2023): I am experiencing the same issue. I am running in a Kubernetes environment and here is my ConfigMap. ``` apiVersion: v1 kind: ConfigMap metadata: name: ntfy namespace: ntfy data: server.yml: | base-url: "https://myurl.com" upstream-base-url: "https://ntfy.sh" log-level: debug ``` I was able to refresh the subscription by pulling down on the view in IOS.

BreizhHardware commented

Author

Owner

@guisea commented on GitHub (Sep 18, 2023):

I too am unable to successfully receive push notifications to an iOS device.

Having tried this now on iPhone and iPad.

Was starting to feel crazy. I have company I see.

@guisea commented on GitHub (Sep 18, 2023): I too am unable to successfully receive push notifications to an iOS device. Having tried this now on iPhone and iPad. Was starting to feel crazy. I have company I see.

BreizhHardware commented

Author

Owner

@kaiwei commented on GitHub (Sep 25, 2023):

Count me in as another user facing the same issue.

@kaiwei commented on GitHub (Sep 25, 2023): Count me in as another user facing the same issue.

BreizhHardware commented

Author

Owner

@guisea commented on GitHub (Oct 1, 2023):

@kaiwei I found notifications work perfectly fine if using the Progressive Web App instead of IOS native application.

Count me in as another user facing the same issue.

@guisea commented on GitHub (Oct 1, 2023): @kaiwei I found notifications work perfectly fine if using the Progressive Web App instead of IOS native application. > Count me in as another user facing the same issue.

BreizhHardware commented

Author

Owner

@weirlive commented on GitHub (Oct 3, 2023):

same

@weirlive commented on GitHub (Oct 3, 2023): same

BreizhHardware commented

Author

Owner

@Trystan34 commented on GitHub (Oct 9, 2023):

@ctschach's comment reported that a reinstall of the iOS app worked. Have any of you tried that?

@Trystan34 commented on GitHub (Oct 9, 2023): [@ctschach's comment](https://github.com/binwiederhier/ntfy/issues/898#issuecomment-1747310255) reported that a reinstall of the iOS app worked. Have any of you tried that?

BreizhHardware commented

Author

Owner

@guisea commented on GitHub (Oct 11, 2023):

I had tried re-installing a time or three on a couple devices to no avail.

However I have re-installed from App-Store again and it appears working now.
On Mon, 9 Oct 2023 at 1:35 PM, Trystan @.***> wrote:

@ctschach's comment reported that a reinstall of the iOS app worked. Have any of you tried that?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

@guisea commented on GitHub (Oct 11, 2023): I had tried re-installing a time or three on a couple devices to no avail. However I have re-installed from App-Store again and it appears working now. On Mon, 9 Oct 2023 at 1:35 PM, Trystan ***@***.***> wrote: > @ctschach's comment reported that a reinstall of the iOS app worked. Have any of you tried that? > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you commented.Message ID: ***@***.***>

BreizhHardware commented

Author

Owner

@Trystan34 commented on GitHub (Oct 11, 2023):

I am hosting the NTFY server using Docker.

My server listens on port 8080 (http) not SSL but due to the one of the useful features of CloudFlare, it provides a toggle for auto SSL encryption to the domain even though the actual NTFY server is listening on HTTP.

Originally I had my base-url set to the static ip of my Rasberry Pi but I did not receive the notifications, since changing it to my domain with https (even though I do not have HTTPS enabled in the ntfy server.yml) it works now.

My docker-compose file

version: "2.3"

services:
  ntfy:
    image: binwiederhier/ntfy
    container_name: ntfy
    command:
      - serve
    environment:
      - TZ=NZDT # optional: set desired timezone
    #user: 1000:1000 # optional: replace with your own user/group or uid/gid
    volumes:
      - /var/cache/ntfy/cache.db:/var/cache/ntfy
      - /etc/ntfy:/etc/ntfy
    ports:
      - "8080:80"
    restart: always

Since the Cloud Flare Tunnel points to my static ip of the Raspberry PI including port 8080, in the iOS app, I have the server set to just domain name excluding the port number.

@Trystan34 commented on GitHub (Oct 11, 2023): I am hosting the NTFY server using Docker. My server listens on port 8080 (http) not SSL but due to the one of the useful features of CloudFlare, it provides a toggle for auto SSL encryption to the domain even though the actual NTFY server is listening on HTTP. Originally I had my base-url set to the static ip of my Rasberry Pi but I did not receive the notifications, since changing it to my domain with https (even though I do not have HTTPS enabled in the ntfy server.yml) it works now. ![image](https://github.com/binwiederhier/ntfy/assets/2108308/a3973b46-c06b-4384-88ef-c420c3a3db98) My docker-compose file ```yaml version: "2.3" services: ntfy: image: binwiederhier/ntfy container_name: ntfy command: - serve environment: - TZ=NZDT # optional: set desired timezone #user: 1000:1000 # optional: replace with your own user/group or uid/gid volumes: - /var/cache/ntfy/cache.db:/var/cache/ntfy - /etc/ntfy:/etc/ntfy ports: - "8080:80" restart: always ``` Since the Cloud Flare Tunnel points to my static ip of the Raspberry PI including port 8080, in the iOS app, I have the server set to just domain name _excluding the port number_.

BreizhHardware commented

Author

Owner

@g0d1k commented on GitHub (Oct 12, 2023):

I'm not sure if this applies to anyone else but I was using a domain I have to send notifications using the CLI, when I stopped using the domain and started using the server IP it works as it should. ie. 'curl -d "My Message" mydomain.com/mytopic' and when I send as 'curl -d "My Message" 192.168.1.1/mytopic' it works.

@g0d1k commented on GitHub (Oct 12, 2023): I'm not sure if this applies to anyone else but I was using a domain I have to send notifications using the CLI, when I stopped using the domain and started using the server IP it works as it should. ie. 'curl -d "My Message" mydomain.com/mytopic' and when I send as 'curl -d "My Message" 192.168.1.1/mytopic' it works.

BreizhHardware commented

Author

Owner

@z3k0sec commented on GitHub (Oct 24, 2023):

I'm also not getting any notifications and have to manually refresh the app to get any notification messages.
Hosting NTFY via Docker and exposing it via Cloudflare tunnel.

"base-url" is set to notify.example.com and the upstream server is the default one.

@z3k0sec commented on GitHub (Oct 24, 2023): I'm also not getting any notifications and have to manually refresh the app to get any notification messages. Hosting NTFY via Docker and exposing it via Cloudflare tunnel. "base-url" is set to notify.example.com and the upstream server is the default one.

BreizhHardware commented

Author

Owner

@binwiederhier commented on GitHub (Nov 28, 2023):

This ticket seems to be an amalgamation of various problems, but very little information. The original bug report does not provide ANY information. I will hence close this issue an direct you to these potentially helpful instructions:

The upstream-base-url must be configured to match exactly what you have configured as a default base URL in your iOS app. Otherwise messages will not arrive at all. See https://docs.ntfy.sh/config/#ios-instant-notifications
If you have different results between 5G and WiFI, it's probably because the iOS app cannot reach your local ntfy server. It must be able to reach it instantly when a new message arrives.
If you have intermittent delivery issues, you are likely being rate-limited by ntfy.sh. Please check your logs and enable debugging/tracing.
Please read the known issues to see if anything applies to your situation.

In general, troubleshooting like this is best done via Discord/Matrix.

@binwiederhier commented on GitHub (Nov 28, 2023): This ticket seems to be an amalgamation of various problems, but very little information. The original bug report does not provide ANY information. I will hence close this issue an direct you to these potentially helpful instructions: 1. The `upstream-base-url` must be configured to match *exactly* what you have configured as a default base URL in your iOS app. Otherwise messages will not arrive at all. See https://docs.ntfy.sh/config/#ios-instant-notifications 2. If you have different results between 5G and WiFI, it's probably because the iOS app cannot reach your local ntfy server. It must be able to reach it instantly when a new message arrives. 3. If you have intermittent delivery issues, you are likely being rate-limited by ntfy.sh. Please check your logs and enable [debugging/tracing](https://docs.ntfy.sh/config/#logging-debugging). 4. Please read the [known issues](https://docs.ntfy.sh/known-issues/) to see if anything applies to your situation. In general, troubleshooting like this is best done via [Discord](https://discord.gg/cT7ECsZj9w)/[Matrix](https://matrix.to/#/#ntfy-space:matrix.org).

BreizhHardware commented

Author

Owner

@jingc1413 commented on GitHub (Apr 28, 2024):

I have the same problem. Reinstalling the app and restarting the phone don't work. I have to refresh the app manually. I can see new messages.
eg:
curl -d "hello" ntfy.sh/xxxxxxx

@jingc1413 commented on GitHub (Apr 28, 2024): I have the same problem. Reinstalling the app and restarting the phone don't work. I have to refresh the app manually. I can see new messages. eg: curl -d "hello" ntfy.sh/xxxxxxx

BreizhHardware commented

Author

Owner

@alexanderdoe commented on GitHub (Apr 28, 2024):

Unfortunately I have the same problem, I have checked everything several times. There is no notification and the messages are only loaded when you reload it in the app

@alexanderdoe commented on GitHub (Apr 28, 2024): Unfortunately I have the same problem, I have checked everything several times. There is no notification and the messages are only loaded when you reload it in the app

BreizhHardware commented

Author

Owner

@aliefe04 commented on GitHub (Jul 6, 2024):

The problem still exists

@aliefe04 commented on GitHub (Jul 6, 2024): The problem still exists

BreizhHardware commented

Author

Owner

@zstreeter commented on GitHub (Jul 6, 2024):

Yeah, I have to refresh the app to see the notification. Seems like everything is setup correctly, since I can see the notification on refresh but not ideal

@zstreeter commented on GitHub (Jul 6, 2024): Yeah, I have to refresh the app to see the notification. Seems like everything is setup correctly, since I can see the notification on refresh but not ideal

BreizhHardware commented

Author

Owner

@vudam991 commented on GitHub (Jul 31, 2024):

I don't know if this is a fix for it but I finally got it to worked.
originally I have two spaces after removing the comma for the line

upstream-base-url: "https://ntfy.sh"
after I remove those two spaces, and restart ntfy it worked and even faster than Android.

upstream-base-url: "https://ntfy.sh"

@vudam991 commented on GitHub (Jul 31, 2024): I don't know if this is a fix for it but I finally got it to worked. originally I have two spaces after removing the comma for the line upstream-base-url: "https://ntfy.sh" after I remove those two spaces, and restart ntfy it worked and even faster than Android. upstream-base-url: "https://ntfy.sh" ![Screenshot 2024-07-31 at 12 17 50 AM](https://github.com/user-attachments/assets/e9925fbe-123f-4104-8f2e-95ebe6dd80d4)

BreizhHardware commented

Author

Owner

@ste7enm commented on GitHub (Sep 5, 2024):

In case, like me, you find this on Google trying to troubleshoot your self-hosted Ntfy docker container and it not generating notifications in iOS, this part ended up doing the trick for me from @binwiederhier's linked known issues resource:

Self-hosted only: No upstream-base-url set, or base-url mismatch:
To make self-hosted servers work with the iOS app, I had to do some horrible things (see iOS instant notifications for details). Be sure that in your selfhosted server:

Set upstream-base-url: "https://ntfy.sh" (not your own hostname!)

Ensure that the URL you set in base-url matches exactly what you set the Default Server in iOS to

My problem was the mismatch between what I set the base-url to in the docker compose versus what I was using in the iOS app to connect – for me, it worked when I made them identical. So, when I previously had the base-url field set to, say, https://192.168.0.1 and in the iOS app had it configured to http://192.168.0.1:1337, updating the base-url field to http://192.168.0.1:1337 in my docker container fixed the issue immediately and I began to receive notifications in iOS.

@ste7enm commented on GitHub (Sep 5, 2024): In case, like me, you find this on Google trying to troubleshoot your self-hosted Ntfy docker container and it not generating notifications in iOS, this part ended up doing the trick for me from @binwiederhier's [linked known issues](https://docs.ntfy.sh/known-issues/) resource: > Self-hosted only: No upstream-base-url set, or base-url mismatch: To make self-hosted servers work with the iOS app, I had to do some horrible things (see [iOS instant notifications](https://docs.ntfy.sh/config/#ios-instant-notifications) for details). Be sure that in your selfhosted server: > > - Set upstream-base-url: "https://ntfy.sh" (not your own hostname!) > - Ensure that the URL you set in **base-url matches exactly what you set the Default Server in iOS** to My problem was the mismatch between what I set the base-url to in the docker compose versus what I was using in the iOS app to connect – for me, it worked when I made them identical. So, when I previously had the base-url field set to, say, `https://192.168.0.1` and in the iOS app had it configured to `http://192.168.0.1:1337`, updating the base-url field to `http://192.168.0.1:1337` in my docker container fixed the issue immediately and I began to receive notifications in iOS.

BreizhHardware commented

Author

Owner

@wunter8 commented on GitHub (Sep 6, 2024):

Glad you got it working! Yes, they need to match exactly. Here are the directions I share with people on Discord

These are the things you need to do to get iOS push notifications to work:

open a browser to the web app of your ntfy instance and copy the URL (including "http://" or "https://", your domain or IP address, and any ports, and excluding any trailing slashes)
put the URL you copied in the ntfy base-url config in server.yml or NTFY_BASE_URL in env variables
put the URL you copied in the default server URL setting in the iOS ntfy app
set upstream-base-url in server.yml or NTFY_UPSTREAM_BASE_URL in env variables to "https://ntfy.sh"

@wunter8 commented on GitHub (Sep 6, 2024): Glad you got it working! Yes, they need to match exactly. Here are the directions I share with people on Discord These are the things you need to do to get iOS push notifications to work: 1. open a browser to the web app of your ntfy instance and copy the URL (including "http://" or "https://", your domain or IP address, and any ports, and excluding any trailing slashes) 2. put the URL you copied in the ntfy `base-url` config in server.yml or NTFY_BASE_URL in env variables 3. put the URL you copied in the default server URL setting in the iOS ntfy app 4. set `upstream-base-url` in server.yml or NTFY_UPSTREAM_BASE_URL in env variables to "https://ntfy.sh"

BreizhHardware commented

Author

Owner

@zabaya commented on GitHub (Dec 1, 2024):

I had the same issue setting it up via docker, i was also running pihole as a dns server. I added google as a dns server on the compose file of ntfy and it worked again.

dns:
 - 8.8.8.8
 - 8.8.4.4

@zabaya commented on GitHub (Dec 1, 2024): I had the same issue setting it up via docker, i was also running pihole as a dns server. I added google as a dns server on the compose file of ntfy and it worked again. ``` dns: - 8.8.8.8 - 8.8.4.4 ```

BreizhHardware commented

Author

Owner

@nudefireninja commented on GitHub (Apr 14, 2025):

Deleting and redownloading the app worked for me. I am not self-hosting, but I originally installed the app many months ago so maybe the post-install configuration was out of date.

@nudefireninja commented on GitHub (Apr 14, 2025): Deleting and redownloading the app worked for me. I am not self-hosting, but I originally installed the app many months ago so maybe the post-install configuration was out of date.

BreizhHardware commented

Author

Owner

@jig1056 commented on GitHub (Oct 5, 2025):

So it's Oct of 2025 and I'm still having the issue. Not sure if there is something that I've done wrong f the bug persists. I tired reinstalling the app and also adding the dns entry to my docker container but no luck

@jig1056 commented on GitHub (Oct 5, 2025): So it's Oct of 2025 and I'm still having the issue. Not sure if there is something that I've done wrong f the bug persists. I tired reinstalling the app and also adding the dns entry to my docker container but no luck

BreizhHardware commented

Author

Owner

@wunter8 commented on GitHub (Oct 5, 2025):

@jig1056 I can help troubleshoot on Discord/Matrix if you're interested.

I'd also recommend, though, using the PWA instead of the native iOS app. The PWA has more features and more reliable notifications than the native app

@wunter8 commented on GitHub (Oct 5, 2025): @jig1056 I can help troubleshoot on Discord/Matrix if you're interested. I'd also recommend, though, using the PWA instead of the native iOS app. The PWA has more features and more reliable notifications than the native app

BreizhHardware commented

Author

Owner

@jig1056 commented on GitHub (Oct 5, 2025):

@jig1056 I can help troubleshoot on Discord/Matrix if you're interested.

I'd also recommend, though, using the PWA instead of the native iOS app. The PWA has more features and more reliable notifications than the native app

Thanks.. Interesting, I will give that a try as well. But I did get iOS App to work using the suggestion from [ste7enm].
(https://github.com/ste7enm)

This worked for me, I just didn't restart my container after updating the server.yml
Set upstream-base-url: "https://ntfy.sh/" (not your own hostname!)
Ensure that the URL you set in base-url matches exactly what you set the Default Server in iOS to

@jig1056 commented on GitHub (Oct 5, 2025): > [@jig1056](https://github.com/jig1056) I can help troubleshoot on Discord/Matrix if you're interested. > > I'd also recommend, though, using the PWA instead of the native iOS app. The PWA has more features and more reliable notifications than the native app Thanks.. Interesting, I will give that a try as well. But I did get iOS App to work using the suggestion from [ste7enm]. (https://github.com/ste7enm) This worked for me, I just didn't restart my container after updating the server.yml Set upstream-base-url: "https://ntfy.sh/" (not your own hostname!) Ensure that the URL you set in base-url matches exactly what you set the Default Server in iOS to

BreizhHardware commented

Author

Owner

@wunter8 commented on GitHub (Oct 5, 2025):

Glad you got it working! Yes, upstream-base-url is crucial for instant iOS notifications

@wunter8 commented on GitHub (Oct 5, 2025): Glad you got it working! Yes, `upstream-base-url` is crucial for instant iOS notifications

BreizhHardware commented

Author

Owner

@jig1056 commented on GitHub (Oct 5, 2025):

I'm also testing the PWA and it's also working well. Nice to have options :) Thanks for the help

@jig1056 commented on GitHub (Oct 5, 2025): I'm also testing the PWA and it's also working well. Nice to have options :) Thanks for the help

BreizhHardware commented

Author

Owner

@luckman212 commented on GitHub (Oct 6, 2025):

Sorry I missed it, where do we go to read more about using the PWA instead of the iOS app please? @wunter8

edit: seems like https://docs.ntfy.sh/subscribe/pwa/ a good place to start

edit2: got it, actually was very simple. Deleted the native app, saved PWA to iPhone desktop, had to resubscribe to my tags and grant permissions—but all is working, including push notifications!

@luckman212 commented on GitHub (Oct 6, 2025): Sorry I missed it, where do we go to read more about using the PWA instead of the iOS app please? @wunter8 **edit:** seems like https://docs.ntfy.sh/subscribe/pwa/ a good place to start **edit2:** got it, actually was very simple. Deleted the native app, saved PWA to iPhone desktop, had to resubscribe to my tags and grant permissions—but all is working, including push notifications!

BreizhHardware commented