ERR Pushover notification failed error="invalid character '<' looking for beginning of value"

[DrEsteban]

Support guidelines

• I've read the support guidelines

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem

Description

#272 is reported as Closed, but is still reproducing. I cannot reactivate the old issue so filing a new one.

Expected behaviour

Pushover notification completes with no errors.

Actual behaviour

ERR Pushover notification failed error="invalid character '<' looking for beginning of value" image=docker.io/prom/prometheus:latest

See #272 for more details.

Steps to reproduce

1. Run a Prometheus image (?)
2. Or maybe, run several (~10) images that need updating
3. Use the latest image of Diun, and configure Pushover
4. Run Diun

Diun version

crazymax/diun:latest@sha256:902ce7d5dfce72b4e1e7d8d2fef58484d3b3ac85a641304ad51e0f2c28f201fe

Docker info

Will update later if needed

Docker Compose config

name: diun

services:
  diun:
    image: crazymax/diun:latest
    command: serve
    volumes:
      - "/volume1/docker/diun:/data"
      - "/var/run/docker.sock:/var/run/docker.sock"
    environment:
      - "DIUN_WATCH_WORKERS=20"
      - "DIUN_WATCH_SCHEDULE=0 */6 * * *"
      - "DIUN_WATCH_JITTER=30s"
      - "DIUN_PROVIDERS_DOCKER=true"
      - "DIUN_PROVIDERS_DOCKER_WATCHBYDEFAULT=true"
      - "DIUN_WATCH_FIRSTCHECKNOTIF=true"
      - "DIUN_WATCH_RUNONSTARTUP=true"
      - "DIUN_NOTIF_PUSHOVER_RECIPIENT=<recipient>"
      - "DIUN_NOTIF_PUSHOVER_TOKEN=<token>"
    labels:
      - "diun.enable=true"
    restart: always

Logs

Sun, 17 Aug 2025 00:16:05 MST DBG Sending pushover notification... image=docker.io/zwavejs/zwave-js-ui:latest

Sun, 17 Aug 2025 00:16:05 MST ERR Pushover notification failed error="invalid character '<' looking for beginning of value" image=docker.io/bropat/eufy-security-ws:latest

Additional info

It seems to be thrown sometimes but not always... I kinda wonder if it's some sort of rate limiting on Pushover?? Because several other notifications went through just fine at the same time, and it isn't consistent with particular images. (For a given image it will work sometimes, but then other times it won't)

Overall I'd suggest you add much more logging here... For a debug log it's surprising to not even see the response code from the server in the logs.

[crazy-max]

Can you try with latest 4.30.0 with LOG_LEVEL=debug env set? https://crazymax.dev/diun/changelog/#4300-20250831?

[DrEsteban]

Will do as soon as I can!

Also JFYI - I finally looked at the PR and added a few suggestion comments. Sorry I was late!

Thanks for taking a look at this.