[BUG] Duplicate Notifications

[julez2310]

Describe the bug
When gotify sends a notification to the mobile device, the notifications appears between 2 to 3 times. In the web interface, only 1 message is shown.

Expected behavior
Only one notification arrives on the smartphone.

Screenshots

Smartphone (please complete the following information):

• Device: iPhone 17
• OS: iOS 26.1
• Version of Container latest (v2.7.3)
• Version of iGotify 1.5.0.3

Additional context
When deleting the volumes "gotify_api-data the notifications will one show once for the next x push-notifications.

I have an other instance which is completly okay. The only difference is, this instance is running behind a OPNsense running NGINX as a Reverse Proxy, the problamatic one is behnid a NGINX-Proxy Manager as docker-image.
Testing to send a webhook over the internal URL also makes no difference. Multiple Services are affected, as Proxmox, Uptime Kuma, Proxmox Backup Server.

[androidseb25]

What does the logs says?

Did he send 2 messages over the assistant?

[androidseb25]

can you please test with version 1.5.1.0

[julez2310]

Hi, sorry for the late reply.
I tested with version 1.5.1.0, the messages are now a bit delayed, which is no big deal, but arrive 2 times.
In the logs from iGotify, i only see one message sent. But i see multiple errors in the igotify-container:
Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:04:47Z | 401 | 303.143µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:04:47Z | 401 | 362.282µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:04:56Z | 401 | 415.775µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:04:57Z | 401 | 527.843µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:04:57Z | 401 | 350.702µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:04:57Z | 401 | 258.523µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:04:57Z | 401 | 459.896µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:06Z | 401 | 627.146µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:07Z | 401 | 358.072µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:07Z | 401 | 252.294µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:07Z | 401 | 252.419µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:07Z | 401 | 631.342µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:16Z | 401 | 337.072µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:17Z | 401 | 290.803µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:17Z | 401 | 207.716µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:17Z | 401 | 254.073µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api 2025-12-01T17:05:17Z | 401 | 469.729µs | 172.25.0.1 | GET "/stream?token=[masked]" Error #01: you need to provide a valid access token or user credentials to access this api
The reverse-proxy should have nothing to do with this error, because i get the same behaviour, when trying to send a message from the terminal on the hosting server.

[androidseb25]

Please try 1.5.1.1 there I fixed the 401 issue that this maybe produce and the docker host panic

[julez2310]

I'm allready on 1.5.1.1. The logs from the gotify-container are the same. Sorry I've confused the logs. Above error messages are from the gotify-container.
Here are my logs from the igotify container, when sending a message from a terminal session. Maybe this helps?

WS Instance from: CQB3kTzJvOcGqt_
WFanQlHFOQOHflwA28icW3fQAolzYtU28qrDr2mt9tzKdFyHxdplz5BvKvUt904xbejr+isj6+ED98tjDQ7XD8S1B865W3jNW6Bw/+3uI/JHUV1LQ3RFCGHdnEshbmKxaT+6jU+j4vjKBlvADzzr9MCcw/Oit0zVLXsHZxoBSlpA3TYtLiwOI6XDMGrVuU1pmqOMMN9ss2cgnw2n5kc5WcIefS0HzMqqjjRhekq+8+i2AZ5RAL+13/4miJQPfnxrtU7c44fllgoYTKYXWps4IAfeH2Zb/w4AAy0D0K7tmE9c+ixsfsPpIrgOhN4QqO5ZhSDEronFEyJj4FRBxm/cbA==
SecNtfyNuGet.ResultResponse
Message converted: {"id":240,"appid":3,"message":"Terminal Test Message","title":"Test","priority":5,"date":"2025-12-01T18:12:44.244741979Z"}

WS Instance from: CQB3kTzJvOcGqt_
EmThdJJhzBmSK3Kg+04vbXZux3LseIH0xqVNdwa1XJV45bPr/ezNPP1g9tNISgoso9q20RJfh3g7IwNhA4UNFAVWi7m2qsOvP9wntByiCrvOpvcbwNOmZl1Jz857TZdbGIpQEW2wUr0bt9fmzM6n/yLlPhGKu2kjU9nBZoCbCWgUSRwS0bPmqkJwD6gn9LqpMxUO62Auy0iuFcZIDv0el6EtUS6eHSYpNH55lGFN+cSxMxvsfvjH1qn+rnruDgmPhfeV0QWB/1NbcuVyG/feHISVMvd53WqTWR2nSBjXoNyGn5q200srgwlgPaXq6NxgBor4YCQNR5+1Se6TVc/9MQ==
SecNtfyNuGet.ResultResponse

Maybe my setup is weird or not correct? Am I missing something in the docker-compose.yml?

version: '3.8'

services:
  gotify:
    container_name: gotify
    hostname: gotify
    image: gotify/server
    restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    networks:
      - net
    ports:
      - "8680:80"
    volumes:
      - data:/app/data
    environment:
      GOTIFY_DEFAULTUSER_PASS: 'password'   # Change me!!!!!
      #TZ: Europe/Berlin
  igotify:
    container_name: igotify
    hostname: igotify
    image: ghcr.io/androidseb25/igotify-notification-assist:latest
    restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    pull_policy: always
    networks:
      - net
    ports:
      - "8681:8080"
    volumes:
      - api-data:/app/data
    #environment:
      #TZ: Europe/Berlin                 # option environment see above note
    #  GOTIFY_URLS: ''
    #  GOTIFY_CLIENT_TOKENS: ''
    #  SECNTFY_TOKENS: ''

networks:
  net:

volumes:
  data:
  api-data:

Thank you!

[androidseb25]

@julez2310 can you please send me a log with docker compose logs -f -t

Then I see a timestamp

I don't think that he do it twice

[julez2310]

Here are the logs, when sending a Test-Message from Uptime-Kuma:

igotify  | 2025-12-03T07:18:01.880419124Z Message converted: {"id":263,"appid":3,"message":"Gotify LT-Cloud Testing","title":"Uptime-Kuma","priority":8,"date":"2025-12-03T07:18:01.873249692Z"}
igotify  | 2025-12-03T07:18:01.880463916Z
igotify  | 2025-12-03T07:18:01.880696785Z WS Instance from: CQB3kTzJvOcGqt_
igotify  | 2025-12-03T07:18:01.958501163Z GZrj+9KJG62ESWdyfXCh5VJ9LCuDd876l1LIbTJUIp0mEC4sLawQOfhDMPcLvtZwqCsfwIcO9+gR0TMd6fJbztoSgqURd9FYunHsD8+kjd2zmeFjCeHm+aHTT/8DmJP/c/fgipHbyEPJ+WbEPSrBm2/KbSt4OJzkwNJep8lTCJ1GuFyqKFjdrT4sgI7fUj2BliVigpNFdQj8NWkyZop3No98sNEglOJiLFNNsJkAlyoRL6UOhUSOqsUVIB1xUGWfgT58RW+eyW43zXQHUpf87H34m/lZ5dUBoBUiuOszyBsw2tMDobIH60v0h1m7TcFnK42s86P7apJ+CRvz27/b5w==
igotify  | 2025-12-03T07:18:02.014750623Z SecNtfyNuGet.ResultResponse
gotify   | 2025-12-03T07:18:03.910633171Z 2025-12-03T07:18:03Z | 200 |     868.134µs |      172.25.0.1 | GET      "/application"
gotify   | 2025-12-03T07:18:04.775085779Z 2025-12-03T07:18:04Z | 200 |    1.527199ms |      172.25.0.1 | GET      "/application"

In this test, I got 2 notifications on my mobile device.

For my understanding: I'm hosting this on a vServer and the message/request is going through the internet, but this shouldn't be a problem, right?

[nicklutt]

i've got the same issue after the last update, after stopping and removing the container (igotify) and removing the volume. and recreating the container my notifications are working again.

[julez2310]

@nicklutt when I delete the "gotify_api-data" volume, I'm getting only one notification. But this lasts for like 3 or 4 messages, then the error occurs again.

[androidseb25]

i'm currently investigate and try to reproduce the problem.

At the moment i don't have a way to filtered out the double notifications, because the system isn't sending double msgid's

[nicklutt]

@nicklutt when I delete the "gotify_api-data" volume, I'm getting only one notification. But this lasts for like 3 or 4 messages, then the error occurs again.

Yeah, you right. It's running one day with one notification, but im experiencing the double triple notification now.

[brianyuen]

Experiencing the same thing for a while now. Multiple notifications, but when I click on one to open Gotify, it only shows one. Currently on iOS 18.7.1, Gotify 1.5.4, iGotify 1.5.1.2

[androidseb25]

hi sorry for the late response overall, i was on vacation and after that i had an influenza :/
now i'm back and working on a fix that stop the double notification issue on app side, i hope so.

I rewritten the service that receive the notification to work more efficient then the old one.
I currently tested it now. i think at the end of the week i would release an app update