Skip to content

Webhook service stuck #744

@eugenyuk

Description

@eugenyuk

Hi guys,

I use webhook 2.8.0 on my Ubuntu 24.04.3 server. Every half hour a request is sent to Webhook and the latter runs the signal-cli shell command.
Yesterday it stuck for unclear reason. At 01:00 there was the last successfully handled request. The next one (at 01:30) and several consequent requests were not handled at once but queued and handled at 06:49 (the time when I logged in to server to check what happened).
The webhook script is run as: webhook -ip localhost -hooks webhook/hooks.json -verbose in side my screen session.
This is the log:

[webhook] 2025/12/18 01:00:01 [90c4bd] incoming HTTP GET request from 127.0.0.1:58916
[webhook] 2025/12/18 01:00:01 [90c4bd] phone got matched
[webhook] 2025/12/18 01:00:01 [90c4bd] error parsing body payload due to unsupported content type header:
[webhook] 2025/12/18 01:00:01 [90c4bd] phone hook triggered successfully
[webhook] 2025/12/18 01:00:01 [90c4bd] error extracting command arguments: couldn't retrieve argument for {Source:url Name:group EnvName: Base64Decode:false}
[webhook] 2025/12/18 01:00:01 [90c4bd] error extracting command arguments: couldn't retrieve argument for {Source:url Name:msg EnvName: Base64Decode:false}
[webhook] 2025/12/18 01:00:01 [90c4bd] executing /home/ubuntu/send-122-to-signal/send-status-to-signal.sh (/home/ubuntu/send-122-to-signal/send-status-to-signal.sh) with arguments ["/home/ubuntu/send-122-to-signal/send-status-to-signal.sh" "+1234567890" "" ""] and environment [] using  as cwd
[webhook] 2025/12/18 01:00:21 [90c4bd] command output: + PHONE_NUMBER=+1234567890
+ SIGNAL_GROUP=
+ MESSAGE=
+ signal-cli -u +1234567890 send -m MESSAGE -g GROUP
WARN  AccountHelper - Messages have been last received 21 days ago. The Signal protocol expects that incoming messages are regularly received.
Failed to send (some) messages:
GROUP: Untrusted Identity for "872ig873-7hs5-8760-3k97-2398dgch387321"
GROUP: Untrusted Identity for "+0987654321"
1766019606359

[webhook] 2025/12/18 01:00:21 [90c4bd] finished handling phone
[webhook] 2025/12/18 01:00:21 [90c4bd] 200 | 541 B | 20.438823784s | localhost:9000 | GET /hooks/phone?number=%2b1234567890
^[[webhook] 2025/12/18 01:30:03 [08204b] incoming HTTP GET request from 127.0.0.1:54410
[webhook] 2025/12/18 06:49:40 [08204b] phone got matched
[webhook] 2025/12/18 06:49:40 [08204b] error parsing body payload due to unsupported content type header:
[webhook] 2025/12/18 06:49:40 [08204b] phone hook triggered successfully
[webhook] 2025/12/18 02:00:02 [154faa] incoming HTTP GET request from 127.0.0.1:55146
[webhook] 2025/12/18 06:49:40 [154faa] phone got matched
[webhook] 2025/12/18 06:49:40 [154faa] error parsing body payload due to unsupported content type header:
[webhook] 2025/12/18 06:49:40 [154faa] phone hook triggered successfully
[webhook] 2025/12/18 06:49:40 [08204b] error extracting command arguments: couldn't retrieve argument for {Source:url Name:group EnvName: Base64Decode:false}
[webhook] 2025/12/18 06:49:40 [08204b] error extracting command arguments: couldn't retrieve argument for {Source:url Name:msg EnvName: Base64Decode:false}
[webhook] 2025/12/18 06:49:40 [08204b] executing /home/ubuntu/send-122-to-signal/send-status-to-signal.sh (/home/ubuntu/send-122-to-signal/send-status-to-signal.sh) with arguments ["/home/ubuntu/send-122-to-signal/send-status-to-signal.sh" "+1234567890" "" ""] and environment [] using  as cwd
[webhook] 2025/12/18 06:49:40 [154faa] error extracting command arguments: couldn't retrieve argument for {Source:url Name:group EnvName: Base64Decode:false}
[webhook] 2025/12/18 06:49:40 [154faa] error extracting command arguments: couldn't retrieve argument for {Source:url Name:msg EnvName: Base64Decode:false}
[webhook] 2025/12/18 06:49:40 [154faa] executing /home/ubuntu/send-122-to-signal/send-status-to-signal.sh (/home/ubuntu/send-122-to-signal/send-status-to-signal.sh) with arguments ["/home/ubuntu/send-122-to-signal/send-status-to-signal.sh" "+1234567890" "" ""] and environment [] using  as cwd
[webhook] 2025/12/18 03:00:01 [754e73] incoming HTTP GET request from 127.0.0.1:57492
[webhook] 2025/12/18 06:49:40 [754e73] phone got matched
[webhook] 2025/12/18 06:49:40 [754e73] error parsing body payload due to unsupported content type header:
[webhook] 2025/12/18 06:49:40 [754e73] phone hook triggered successfully
[webhook] 2025/12/18 06:49:40 [754e73] error extracting command arguments: couldn't retrieve argument for {Source:url Name:group EnvName: Base64Decode:false}
[webhook] 2025/12/18 06:49:40 [754e73] error extracting command arguments: couldn't retrieve argument for {Source:url Name:msg EnvName: Base64Decode:false}
[webhook] 2025/12/18 06:49:40 [754e73] executing /home/ubuntu/send-122-to-signal/send-status-to-signal.sh (/home/ubuntu/send-122-to-signal/send-status-to-signal.sh) with arguments ["/home/ubuntu/send-122-to-signal/send-status-to-signal.sh" "+1234567890" "" ""] and environment [] using  as cwd

I've noticed the strange ^ character in the log when the service stuck at 01:30:03 and second ^ when it back to work at 06:49:56.
The whole log I attach. Could you please help me to understand the reason of the issue?
Thank you.

webhook.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions