Discord: fetch failed on gateway connection despite discord policy preset applied (Linux/Ubuntu)

[EliFebres]

Description

Discord channel consistently fails to connect with fetch failed errors after logged in to discord succeeds. The bot authenticates with the token successfully but the follow-up REST calls to Discord's API are blocked by the OpenShell proxy despite the discord policy preset being applied and active. This is reproducible on Ubuntu Linux. A similar issue (#481) was filed for macOS — this confirms the bug is not platform-specific.

Reproduction Steps

1. Install NemoClaw on Ubuntu 22.04 via curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
2. Run nemoclaw onboard — create sandbox, select Nemotron 3 Super, apply pypi + npm presets
3. Run nemoclaw policy-add discord — confirm discord shows as active in policy-list
4. Connect to sandbox: nemoclaw connect
5. Run openclaw onboard — configure Anthropic API key, select Discord, set Open channel access, paste bot token
6. Observe in openclaw logs --follow:
   • "logged in to discord" (token auth succeeds)
   • "Failed to get gateway information from Discord: fetch failed"
   • "discord: failed to deploy native commands: fetch failed"
   • "discord: failed to fetch bot identity: TypeError: fetch failed"
   • Health monitor restarts Discord channel every 5 minutes, same result each time

Environment

OS: Ubuntu 22.04 LTS (Linux)
NemoClaw: latest (installed via nvidia.com/nemoclaw.sh, March 2026)
OpenClaw: 2026.3.11 (29dc654)
OpenShell: 0.0.12
Docker: running
GPU: none (cloud inference)
Discord policy: applied and confirmed active via policy-list

Debug Output

Logs

Checklist

• I confirmed this bug is reproducible
• I searched existing issues and this is not a duplicate

[wscurran]

✨ Thanks for submitting this issue with a detailed description, it identifies a fetch failed error on gateway connection despite Discord policy preset applied, which could be related to the Discord integration or OpenShell proxy configuration on Ubuntu.

[kjw3]

Working plan update from the Discord/native messaging investigation:

We are treating this as part of the broader native Discord regression introduced by the move from host-side bridges to OpenClaw/OpenShell-native messaging. The current implementation path in NemoClaw is: baked channel config, provider placeholder injection, and OpenShell proxy/L7 rewrite.

Execution plan now in progress:

• supersede PR fix(presets): add missing binaries to communication presets #1084 with a narrower preset fix focused on the minimal justified binary coverage
• stop relying on runtime openclaw doctor --fix for sandbox-baked channel config; improve docs and diagnostics instead
• add true native Discord gateway validation to E2E, not just REST/token-rewrite probes
• classify the remaining native path failures across NemoClaw, OpenClaw, and OpenShell

Working branch: fix/discord-native-remediation

This issue looks like one of the main native-path symptoms, so I’m treating it as part of that remediation track rather than as an isolated policy-only bug.