For some reason my push Notification are not working properly even with my ntfy server. I will miss calls from people because it doesn’t seem like my clients are running in the background on my pixel. I have the battery access set to unrestricted. I do not know why the clients don’t run in the background to notify me.

It seems they only really notify me if I keep the client open.

I am using a google pixel 8 running grapheneos. The clients I have tried are: schildichat and element.

I have also tried it on my fiance’s google pixel 8 running grapheneos and the same issue appears.

I am running both my ntfy server and matrix server on docker on a ubuntu 20.04 machine with casaos. I use cloudflare tunnels to forward my services.

When troubleshooting notifications it passes all the tests on both element and schildichat. however on element x and schildi next I get an error failed to check gateway and push back loop. (which both element x and schildi next functioning 100% for me yet. See other posts)

Any help is appreciated!

Edit: it seems to be a problem with ntfy. Checking the container logs I found this:

INFO Connection closed with HTTP 500 (ntfy error 50003) (error=internal server error: base-url must be be configured for this feature, error_code=50003, http_method=GET, http_path=/_matrix/push/v1/notify, http_status=500, tag=http, visitor_auth_limiter_limit=0.016666666666666666, visitor_auth_limiter_tokens=30, visitor_id=ip:example, visitor_ip=example, visitor_messages=43, visitor_messages_limit=17280, visitor_messages_remaining=17237, visitor_request_limiter_limit=0.2, visitor_request_limiter_tokens=60, visitor_seen=2025-02-06T09:19:26.984Z)

Edit 2: i seemed to have fixed that error by reinstalling ntfy and creating a config file with the base url. However I am still not recieving push notifications. Element still crashes/closes and stops running in the background. I have no idea how to fix this. I have seen mentions of ‘ip_range_whitelist’ variables not being set properly. However all the documentation that relates to that variable is only for synapse. I do not know if that same variable is applicable to dendrite. I cannot see it listed in the config file.

  • Strit
    link
    fedilink
    English
    118 hours ago

    INFO Connection closed with HTTP 500 (ntfy error 50003) (error=internal server error: base-url must be be configured for this feature

    Yeah, sounds like you need to configure the base-url of ntfy.

    • @[email protected]OP
      link
      fedilink
      English
      1
      edit-2
      4 hours ago

      Is this within a config file for ntfy? When I access it through local host it tells me it needs to be accessed through https. Which I setup through cloudflare tunnels and the error went away.

      There was no config file generated for my docker container for ntfy.

      Edit: I have fixed this error but notifications still do not work.

  • @ricdeh
    link
    English
    118 hours ago

    Are you certain that Element does not run in the background? It always does for me, both on my Samsung with OneUI and on another Samsung with LineageOS. Perhaps not really helpful, but my observation is that Element’s background “listening for notifications” is quite reliable. Might this be due to some settings in your OS?

    • Strit
      link
      fedilink
      English
      118 hours ago

      ELement from google play always use the google push notiofication system, which is always running. But element from say f-droid, does not have access to that, so it needs another push daemon to work, like ntfy.