[GH-ISSUE #632] Signal Integration Failing #457

New issue

Closed

opened 2026-02-25 23:42:31 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 23:42:31 +03:00

Owner

Originally created by @azoller1 on GitHub (Apr 5, 2022).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/632

I am receiving the same issues after registration and testing my signal integration. The number/account should be valid.

Could not send a test notification. signal-cli call failed (-1).

All other integrations for me work ok.

Originally created by @azoller1 on GitHub (Apr 5, 2022). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/632 Related here: https://github.com/healthchecks/healthchecks/issues/564 I am receiving the same issues after registration and testing my signal integration. The number/account should be valid. Could not send a test notification. signal-cli call failed (-1). All other integrations for me work ok.

kerem closed this issue

2026-02-25 23:42:31 +03:00

kerem commented

2026-02-25 23:42:32 +03:00

Author

Owner

@cuu508 commented on GitHub (Apr 5, 2022):

Investigating, upstream issue filed: https://github.com/AsamK/signal-cli/issues/923

@cuu508 commented on GitHub (Apr 5, 2022): Investigating, upstream issue filed: https://github.com/AsamK/signal-cli/issues/923

kerem commented

2026-02-25 23:42:32 +03:00

Author

Owner

@bjo81 commented on GitHub (Apr 6, 2022):

I'm getting Could not send a test notification. signal-cli call failed (-32602). - I assume that's another issue?

@bjo81 commented on GitHub (Apr 6, 2022): I'm getting `Could not send a test notification. signal-cli call failed (-32602).` - I assume that's another issue?

kerem commented

2026-02-25 23:42:32 +03:00

Author

Owner

@cuu508 commented on GitHub (Apr 7, 2022):

@bjo81 not sure, are you getting this on a self-hosted instance?

The first thing to check would be to see if you can send a message manually with signal-cli from command line. If that fails, the command's output may have clues on what's wrong.

@cuu508 commented on GitHub (Apr 7, 2022): @bjo81 not sure, are you getting this on a self-hosted instance? The first thing to check would be to see if you can send a message manually with signal-cli from command line. If that fails, the command's output may have clues on what's wrong.

kerem commented

2026-02-25 23:42:32 +03:00

Author

Owner

@cuu508 commented on GitHub (Apr 13, 2022):

I've updated Healthchecks to handle Signal rate-limiting issues better. Instead of showing the non-specific "signal-cli call failed (-1)", Healthchecks now shows "CAPTCHA proof required". It also sends an email alert to site administrators with more details. For administrators, there is also now a submitchallenge management command for submitting CAPTCHA solution.

@cuu508 commented on GitHub (Apr 13, 2022): I've updated Healthchecks to handle Signal rate-limiting issues better. Instead of showing the non-specific "signal-cli call failed (-1)", Healthchecks now shows "CAPTCHA proof required". It also sends an email alert to site administrators with more details. For administrators, there is also now a `submitchallenge` management command for submitting CAPTCHA solution.

kerem referenced this issue

2026-02-26 00:30:15 +03:00

[PR #457] [MERGED] Add http header auth #964