Skip to content
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 not sending test message #524

Open
Rom0067 opened this issue Sep 28, 2024 · 9 comments
Open

ntfy not sending test message #524

Rom0067 opened this issue Sep 28, 2024 · 9 comments

Comments

@Rom0067
Copy link

Rom0067 commented Sep 28, 2024

Hello,

I'm not sure if I'm missing something or if this is a bug but I am not receiving test notifications from ntfy. Im not sure if Im supposed to put something in the custom headers section. I tried an Authorization: Basic "Token" but that also did not work. Any help is appreciated.

Screenshot 2024-09-28 013120
@ellite
Copy link
Owner

ellite commented Sep 29, 2024

Hi. At what stage does it fail?
Does it fail when pressing the test button?
Does it say success but never arrives, or does it say failed when pressing the test button?
Does it work on the test but actual subscription notifications fail?

Thanks.
Regards.

@Rom0067
Copy link
Author

Rom0067 commented Sep 29, 2024

Hi thanks for getting back to me. It says success notification sent successfully but I am not getting a notification on my ntfy app or in a web browser.

@Collin7
Copy link

Collin7 commented Oct 13, 2024

Hi @Rom0067

Im not sure if this will help you but I needed to add my headers in a JSON object as follows, my test now works

{
  "Authorization": "your token here",
  "Title": "Subscription Notice",
  "Tags": "repeat"
}

Regards,

@Rom0067
Copy link
Author

Rom0067 commented Oct 14, 2024

Hi @Rom0067

Im not sure if this will help you but I needed to add my headers in a JSON object as follows, my test now works

{
  "Authorization": "your token here",
  "Title": "Subscription Notice",
  "Tags": "repeat"
}

Regards,

Thank you @Collin7 for reaching out. Could I ask where you get the token from? Is that in my ntfy config/compose file? Also what is the tags option I haven't seen that before as an option in ntfy? Sorry I'm completely lost when it comes to JSON. I usually use ntfy from the fui and occasionally cli. Thanks again!

@Collin7
Copy link

Collin7 commented Oct 14, 2024

Hi @Rom0067
No problem, hope it works for you. the Tags header is for adding an icon/emoji to your notification. You can find them all here in the docs NTFY Emojis.

As for the token, if you have access control set up that is not public and have a username and password configured for your topic access, you can generate the token inside the ntfy docker container see instructions here Access Control.

I set mine up long ago, if I recall I created an admin role user, and then created the token for that user, you will see the step by step guid in the above link.

@Rom0067
Copy link
Author

Rom0067 commented Oct 14, 2024

Hi @Rom0067 No problem, hope it works for you. the Tags header is for adding an icon/emoji to your notification. You can find them all here in the docs NTFY Emojis.

As for the token, if you have access control set up that is not public and have a username and password configured for your topic access, you can generate the token inside the ntfy docker container see instructions here Access Control.

I set mine up long ago, if I recall I created an admin role user, and then created the token for that user, you will see the step by step guid in the above link.

@Collin7 You are awesome for taking the time to help. I thought that is what you meant by auth token so docker exec'd and ran ntfy commands to find it. I did exactly what you suggested but I still am not receiving any messages...

walllosntfyerror

@Collin7
Copy link

Collin7 commented Oct 15, 2024

It's no problem @Rom0067. Try adding Bearer to your token header.
Like this
"Authorization": "Bearer tk_...",

If this still does not work make sure you can get the notification using curl command on your pc, if that does not work then you know it's not Wallos but your ntfy setup that has an issue. Just to narrow down where to look.
Hope this helps

@Rom0067
Copy link
Author

Rom0067 commented Oct 15, 2024

It's no problem @Rom0067. Try adding Bearer to your token header.
Like this
"Authorization": "Bearer tk_...",

If this still does not work make sure you can get the notification using curl command on your pc, if that does not work then you know it's not Wallos but your ntfy setup that has an issue. Just to narrow down where to look.
Hope this helps

@Collin7 IT WORKED! Thank you very much for sticking with me. Is the "Bearer" located on ntfy docs? If so I need to be better at reading directions 😄 Thanks again have a good one!

@Collin7
Copy link

Collin7 commented Oct 15, 2024

@Rom0067 awesome news. Happy to help. It is in the docs, but I know this stuff is tricky 🙂
For reference its here.
Keep well 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants