-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ntfy trigger not working with authentication on a selfhosted instance #482
Comments
First: thanks for the new feature! Now I can stop using a nodered-service to reformat a WUD-post-request so ntfy can understand it :). Unfortunately I'm also unable to get authentication working. Looking at the code, I think the issue is at the if-structures at line 78 (user/password) and 84 (bearer-token) in the ntfy.js file.
Should be
Same for the token-if: checks
Should be (using this.configuration.auth.token as per the docs, but could be wrong here)
|
Thank you both for your feedback and your analysis 👍 . Actually I didn't test that part by a lack of time (or laziness 🤔 )... |
Released in |
And it works! Thanks for the great app and the quick response! |
When trying to configure a Ntfy trigger to my selfhosted Ntfy instance using authentication, the WUD docker logs show error 403 forbidden.
I have tried with both username and password and a token with the same result. Both the username and password and the token were verified to be working outside of the WUD container.
I configured it to connect to the public ntfy.sh server and the notification worked as expected. It is only when sending to my selfhosted instance that requires authentication that it is failing.
Docker compose environment options for WUD:
WUD docker logs:
The text was updated successfully, but these errors were encountered: