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 subscription message - test OK #560

Open
hgelpke opened this issue Oct 9, 2024 · 6 comments
Open

ntfy not sending subscription message - test OK #560

hgelpke opened this issue Oct 9, 2024 · 6 comments

Comments

@hgelpke
Copy link

hgelpke commented Oct 9, 2024

Version v2.26.0
Running via docker container in Proxmox

Test message goes through but no ntfy notification. I have notifications setup for email and ntfy and do get the emails

firefox_8PZ6fm3NqH
firefox_IpJXmVEbzn

@Collin7
Copy link

Collin7 commented Oct 13, 2024

Hi,

I have the same issue. Test shows successful, but I dont recieve the ntfy notification.
I cant find documentation on how to specify custom headers. Is it in JSON format, or like Curl with the -H flag, or just key value pairs?

UPDATE:

I should have just read the code first, I see that headers input expects a JSON String.
@hgelpke 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"
}

@hgelpke
Copy link
Author

hgelpke commented Oct 14, 2024

Hi,

I have the same issue. Test shows successful, but I dont recieve the ntfy notification. I cant find documentation on how to specify custom headers. Is it in JSON format, or like Curl with the -H flag, or just key value pairs?

UPDATE:

I should have just read the code first, I see that headers input expects a JSON String. @hgelpke 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"
}

My test notice comes through. It's the subscriptions that don't. Was that your issue?

@Collin7
Copy link

Collin7 commented Oct 15, 2024

Hi @hgelpke
Sorry I misunderstood your question, I see what you meant, I was not getting the test message, which is now working. I only recently set Wallos up, I created some test subscriptions to see if I get the notifications. I will let you know if I get them.

@ellite
Copy link
Owner

ellite commented Oct 15, 2024

Hi. If you're admin you can trigger the "send notification" cronjob on the admin page, under the maintenance tasks. So you don't have to wait for the next cronjob to run

image

@Collin7
Copy link

Collin7 commented Oct 15, 2024

Hi @ellite
Thank you, sorry I only set this up this recently and im on holiday, have not had a chance to play with all the settings.
I have tried a test now as per screenshot above and it worked for me. Amazing job on this project by the way. 👍

@hgelpke If I test notificataion as suggested in the above comment, I get the notification for the test subscription I set up to run for tomorrow.

@koenigderorangen
Copy link

Hi,
I have the same issue. Test shows successful, but I dont recieve the ntfy notification. I cant find documentation on how to specify custom headers. Is it in JSON format, or like Curl with the -H flag, or just key value pairs?
UPDATE:
I should have just read the code first, I see that headers input expects a JSON String. @hgelpke 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"
}

My test notice comes through. It's the subscriptions that don't. Was that your issue?

For me, regular subscription reminder worked after i put "Bearer" infront of my access token, so my custom head field looks like this:
image

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

4 participants