You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using DIUN to send notifications through a self-hosted instance of ntfy, the following error is logged: "invalid character '<' looking for beginning of value"
This behavior can also be triggered by using test notifications.
Expected behaviour
When sending any kind of notification via ntfy, it should immediately be visible to all subscribers.
Actual behaviour
The aforementioned error shows up and notifications do not go through.
Steps to reproduce
Install a self-hosted ntfy instance
Make necessary adjustment to DIUN configuration to point to ntfy
Execute diun notif test from the command line
Read error message "invalid character '<' looking for beginning of value"
As mentioned in #986, I think this is related to the response parser, which expects a json, but in some cases may receive an html in the response body.
The text was updated successfully, but these errors were encountered:
Background: I am running gotify (ntfy alternative) and diun in the same server, gotify is running behind reverse proxy with a domain name so its port is not exposed.
Problem: When I set DIUN_NOTIF_GOTIFY_ENDPOINT to gotify https domain, I got the same error.
Solution: Changing DIUN_NOTIF_GOTIFY_ENDPOINT to gotify's local docker url fix the issue, I am using docker compose and both gotify and diun is in same docker networks, I just set it to http://gotify:80.
Support guidelines
I've found a bug and checked that ...
Description
This issue is related to #986.
When using DIUN to send notifications through a self-hosted instance of ntfy, the following error is logged: "invalid character '<' looking for beginning of value"
This behavior can also be triggered by using test notifications.
Expected behaviour
When sending any kind of notification via ntfy, it should immediately be visible to all subscribers.
Actual behaviour
The aforementioned error shows up and notifications do not go through.
Steps to reproduce
diun notif test
from the command lineDiun version
4.26.0
Docker info
Docker Compose config
No response
Logs
Additional info
As mentioned in #986, I think this is related to the response parser, which expects a json, but in some cases may receive an html in the response body.
The text was updated successfully, but these errors were encountered: