Skip to content

[Bug]: Discord voice joins but no speech output (DecryptionFailed: UnencryptedWhenPassthroughDisabled) #25372

@jmdelpinob

Description

@jmdelpinob

Summary

Discord voice channel join succeeds, but the bot does not speak/respond in voice. Logs show voice receive decrypt failures.

Environment

  • OpenClaw version: 2026.2.23 (b817600)
  • Host: macOS (arm64)
  • Node: v25.6.1
  • ffmpeg: installed (/opt/homebrew/bin/ffmpeg)
  • Discord native commands: enabled
  • Discord voice config: enabled with TTS OpenAI/alloy

Config (relevant)

{
  "channels": {
    "discord": {
      "voice": {
        "enabled": true,
        "tts": {
          "provider": "openai",
          "openai": { "voice": "alloy" }
        }
      }
    }
  }
}

What works

  • /vc join now succeeds and bot joins/stays in the voice channel.
  • Bot has Connect + Speak permissions.
  • Gateway remains up (no immediate crash after join in latest repro).

What fails

  • Bot does not talk/respond in voice channel.
  • No audible TTS playback after user speech.

Logs

{"subsystem":"discord/voice"} discord voice: receive error: Failed to decrypt: DecryptionFailed(UnencryptedWhenPassthroughDisabled)

Also observed earlier in same environment (prior runs) that /vc join could crash with:

Cannot utilize the DAVE protocol as the @snazzah/davey package has not been installed.

After restart/new repro, this hard crash was not present, but voice still does not function due to decrypt failures.

Repro steps

  1. Configure channels.discord.voice.enabled=true with voice.tts set.
  2. Start/restart gateway.
  3. In Discord guild text channel, run /vc join.
  4. Confirm bot joins VC.
  5. Speak in VC (e.g., "can you hear me?").
  6. Observe no voice response and decryption warning in logs.

Expected behavior

Bot should receive/decrypt inbound audio and produce spoken responses in VC.

Actual behavior

Bot joins VC but cannot process inbound audio due to DecryptionFailed(UnencryptedWhenPassthroughDisabled) and remains silent.

Notes

  • Related recently-closed issues appear focused on Opus packaging/update failures (#23737, #23733, #23703).
  • This appears to be a separate runtime voice decrypt path issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions