#I updated to 2025.05.07 from 2025.04.16, changed some settings, now can't reach OC from Discord

1 messages · Page 1 of 1 (latest)

uncut heart
#

After the update I was testing openclaw through the build in chat/command interface. That was a mistake, because I did not verify that discord was still working.
I later added the following changes to my openclaw.json:

  1. I added a "ownerAllowFrom": [ "discord:12.........79" ] (obfuscated for privacy reasons) and set messages.groupChat.visibleReplies = message_tool via doctor.
  2. I enabled commitments (enabled = true; maxPerDay = 3)
  3. I changed controlUi.allowInsecureAuth from true to false

Now my bot is not reachable via Discord. He is shown as disabled.

stable roseBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

silver kayak
#

if you're able to access the control UI and reach your agent that way. Ask it to troubleshoot and fix

uncut heart
#

I've got it done by exporting an obfuscated config file and the logs to claude.ai.
took some time and explaining what is

simple blazeBOT
#

Nice, glad you got it unstuck 🎉

Tiny privacy note: exporting config + logs to claude.ai is fine only if you’re really sure tokens, user IDs, webhook URLs, and auth headers are redacted. For future debugging, openclaw status --all is the safer pasteable report because it’s read-only and redacts tokens by design: https://docs.openclaw.ai/help/faq

If you have a minute, please drop the short version of what the actual fix/root cause was here. That makes this thread useful for the next person. And if a message in this thread solved it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow indexes it.