hermes - 💡(How to fix) Fix [Bug]: WhatsApp bridge dies immediately with code -9 under systemd [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fixed

Code Example

Report       https://paste.rs/KvR0n
  agent.log    https://paste.rs/B6un3
  gateway.log  https://paste.rs/ExN97

---

⚠️  This will upload the following to a public paste service:
System info (OS, Python version, Hermes version, provider, which API keys
    are configured — NOT the actual keys)
Recent log lines (agent.log, errors.log, gateway.log — may contain
    conversation fragments and file paths)
Full agent.log and gateway.log (up to 512 KB each — likely contains
    conversation content, tool outputs, and file paths)

Pastes auto-delete after 6 hours.

Collecting debug report...
Uploading...

Debug report uploaded:
  Report       https://paste.rs/Jjohw
  agent.log    https://paste.rs/xKwgv
  gateway.log  https://paste.rs/gbXyX

Pastes will auto-delete in 6 hours.
To delete now:  hermes debug delete <url>

Share these links with the Hermes team for support.
RAW_BUFFERClick to expand / collapse

Bug Description

Environment:

  • OS: Ubuntu 24.04
  • Hermes version: [run: hermes version]
  • Node version: 22.22.3
  • VPS: Hetzner 4GB

Symptom: Gateway starts, bridge reports "Bridge ready (status: connected)" then immediately exits with "WhatsApp bridge process exited unexpectedly (code -9)" causing gateway to fail.

Log evidence: [Whatsapp] Bridge ready (status: connected) [Whatsapp] Bridge started on port 3000 [Whatsapp] Disconnected [Whatsapp] WhatsApp bridge process exited unexpectedly (code -9) hermes-gateway.service: Main process exited, status=1/FAILURE

Suspected cause: Bridge process receives SIGKILL immediately after starting. Memory pressure possibly involved (4GB VPS, bridge uses ~120MB). Issue does not occur when running gateway interactively in foreground.

Steps to Reproduce

  1. Install Hermes with profile
  2. Configure WhatsApp via hermes whatsapp
  3. Start gateway via systemd
  4. Bridge connects then immediately dies with SIGKILL

Expected Behavior

Should successfully connect to Whatsapp bridge and allow messages to be exchanged.

Actual Behavior

Gateway starts, bridge reports "Bridge ready (status: connected)" then immediately exits with "WhatsApp bridge process exited unexpectedly (code -9)" causing gateway to fail.

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

WhatsApp

Debug Report

Report       https://paste.rs/KvR0n
  agent.log    https://paste.rs/B6un3
  gateway.log  https://paste.rs/ExN97

Operating System

Ubuntu 24.04

Python Version

Python 3.12.3

Hermes Version

Hermes Agent v0.14.0 (2026.5.16)

Additional Logs / Traceback (optional)

⚠️  This will upload the following to a public paste service:
  • System info (OS, Python version, Hermes version, provider, which API keys
    are configured — NOT the actual keys)
  • Recent log lines (agent.log, errors.log, gateway.log — may contain
    conversation fragments and file paths)
  • Full agent.log and gateway.log (up to 512 KB each — likely contains
    conversation content, tool outputs, and file paths)

Pastes auto-delete after 6 hours.

Collecting debug report...
Uploading...

Debug report uploaded:
  Report       https://paste.rs/Jjohw
  agent.log    https://paste.rs/xKwgv
  gateway.log  https://paste.rs/gbXyX

⏱  Pastes will auto-delete in 6 hours.
To delete now:  hermes debug delete <url>

Share these links with the Hermes team for support.

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING