iOS not pushing notifications. Ntfy needs to be refreshed to view them. about ntfy HOT 12 CLOSED

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.

from ntfy.

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.

from ntfy.

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.

from ntfy.

Count me in as another user facing the same issue.

from ntfy.

@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.

from ntfy.

same

from ntfy.

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

from ntfy.

from ntfy.

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.

from ntfy.

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.

from ntfy.

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.

from ntfy.

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.
4. Please read the known issues to see if anything applies to your situation.

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

from ntfy.