#ClawHub Plugin part of website is broken
67 messages Ā· Page 1 of 1 (latest)
Yep, I can reproduce it, so this looks server-side, not your setup.
From here:
- plugin search is throwing 500s for normal queries like
weather,telegram,test - the catalog works for pages 1 and 2, then page 3 starts returning a server error too
I canāt fix ClawHub prod from this thread, but this should be filed in the ClawHub repo:
https://github.com/openclaw/clawhub/issues
Useful repro details to include:
https://clawhub.ai/plugins- search box returns server error for many queries
- browsing past the second page of plugins also returns server error
If you want, I can help you turn this into a clean issue report text.
Yes please! I don't feel like doing it myself. š
Fair š I canāt open the GitHub issue for you from here, but hereās a copy-paste version so you only have to dump it in:
Open here: https://github.com/openclaw/clawhub/issues/new
Title
Plugin search returns 500, and plugin catalog breaks after page 2
Body
## Summary
The ClawHub plugin catalog appears to be broken server-side:
- searching for plugins often returns a server error
- browsing the plugin catalog past page 2 also returns a server error
This does not look client-side. It was reproducible externally as well.
## Reproduction
### Plugin search
1. Go to <https://clawhub.ai/plugins>
2. Search for a normal term like:
- `weather`
- `telegram`
- `test`
3. Observe a server error
Direct API repro:
- `GET https://clawhub.ai/api/v1/plugins/search?q=weather&limit=10`
- Result: `500 {"code":"[Request ID: ce3f7edefd771b01] Server Error"}`
### Plugin catalog pagination
1. Go to <https://clawhub.ai/plugins>
2. Browse the catalog without searching
3. Page 1 works
4. Page 2 works
5. Page 3 returns a server error
Direct API repro:
- `GET https://clawhub.ai/api/v1/plugins?limit=50` ā 200
- `GET https://clawhub.ai/api/v1/plugins?limit=50&cursor=pkgpage:{"cursor":null,"offset":51,"pageSize":150,"done":false}` ā 200
- `GET https://clawhub.ai/api/v1/plugins?limit=50&cursor=pkgpage:{"cursor":null,"offset":101,"pageSize":150,"done":false}` ā 500
Observed error:
- `{"code":"[Request ID: 0303f5d43896f525] Server Error"}`
## Expected
- plugin searches should return results or empty results, not 500s
- catalog pagination should continue past page 2
## Actual
- many search queries return 500
- page 3 of the plugin catalog returns 500
If you want, I can make it even lazier and turn that into a super short version too.
Nah. I submitted the issue. Thx! <3
Nice, thank you ā¤ļø
That was definitely a real bug, so Iām glad itās filed. Hopefully they squash it quickly.
Hey, just wanted to check up on the issue. Has the problem been fixed yet or no?
Not yet.
I just rechecked it:
- plugin search is still 500ing
- page 3 of the plugin catalog is still 500ing too
Your issue is still open, no maintainer update on it yet:
https://github.com/openclaw/clawhub/issues/1699
So, unfortunately, still broken right now.
Damn. I might check in with you again later tonight.
Yep, sounds good. Check back later and Iāll re-test it for you. š¦
Any changes yet?
Nope, still broken.
I just rechecked:
- search still returns 500
- page 3 of the plugin catalog still returns 500
Issue is unchanged too, still open with no comments or updates:
https://github.com/openclaw/clawhub/issues/1699
The website is also broken on the subpages of https://openclaw-ai.com/de/docs/providers/index. I can't look up any provider settings, which is very frustrating.
Example: https://openclaw-ai.com/providers/ollama ->
404: NOT_FOUND
Code: NOT_FOUND
ID: fra1::wwj2z-1776433637009-0d07c405db77
A quick search of the open GitHub issues revealed that other website functions (search, etc.) are also affected. Apparently, there is a major issue with the website architecture or the backend.
Translated with DeepL.com (free version)
Yep, I checked, that one is real too, but it looks a bit more specific than a total backend meltdown.
The broken part is this page:
https://openclaw-ai.com/de/docs/providers/index
Itās generating bad links like:
/providers/ollamaā
But the working paths are:
- https://openclaw-ai.com/de/docs/providers/ollama ā
- preferably the current docs site: https://docs.openclaw.ai/de/providers/ollama ā
So for now, the workaround is to use docs.openclaw.ai directly, or manually keep the /de/docs/ prefix on the old site.
So, short version:
- yes, broken link generation is real
- no, itās not just you
- the provider docs themselves do still exist, the links are just wrong on that page
Okay, should I report the issue with the broken links somewhere else, or will you (or a moderator here) handle it?
Please report it yourself, thatās the reliable path.
I can help investigate and write it up, but I canāt open GitHub issues on someoneās behalf, and I wouldnāt count on a mod silently picking it up from the thread.
For the broken docs links, file it here:
https://github.com/openclaw/openclaw/issues/new
That one belongs in openclaw/openclaw, not ClawHub, since itās a docs-site/linking problem.
If you want, I can give you a ready-to-paste issue title/body for that one too.
Nice, that would help. I'm not so sure about best practics here and my english is far from good.
Your English is totally fine, no worries. Hereās a clean copy-paste version:
Open here: https://github.com/openclaw/openclaw/issues/new
Title
Broken provider links on localized docs page openclaw-ai.com/de/docs/providers/index
Body
## Summary
The localized docs page for providers contains broken links.
Page:
https://openclaw-ai.com/de/docs/providers/index
On that page, provider links are generated like this:
- `/providers/ollama`
But on this site those links return 404.
Example broken link:
- https://openclaw-ai.com/providers/ollama
Error shown:
- `404: NOT_FOUND`
## Steps to reproduce
1. Open:
https://openclaw-ai.com/de/docs/providers/index
2. Click a provider link such as `Ollama`
3. It opens:
https://openclaw-ai.com/providers/ollama
4. The page returns 404
## Expected behavior
Clicking the provider link should open the provider docs page.
For example, one of these working paths:
- https://openclaw-ai.com/de/docs/providers/ollama
- https://docs.openclaw.ai/de/providers/ollama
## Actual behavior
The page links to `/providers/...` instead of the correct docs path, so the generated links are broken.
## Notes
This looks like a link generation / routing bug on the localized docs page, not missing provider documentation.
The provider docs still exist, but the links from the index page are wrong.
If you want, I can also make a shorter version that sounds a bit less formal.
I need additionaly:
Impact and severity
Explain who is affected.
Yep, you can add this:
## Impact
Users cannot navigate from the localized provider index page to the actual provider documentation pages.
This causes:
- broken documentation navigation
- confusion about whether provider docs exist at all
- extra support burden in Discord/GitHub
- a poor onboarding experience for users trying to configure providers like Ollama
The docs content still exists, but the broken links make it much harder to find.
## Severity
Medium
Reason:
- this is not a security issue
- this does not cause data loss
- but it does break an important docs flow for setup/configuration, especially for localized docs users
## Who is affected
Affected users are people using the localized docs pages on `openclaw-ai.com`, for example:
- `https://openclaw-ai.com/de/docs/providers/index`
Especially affected:
- new users
- non-English users
- users trying to configure model providers and looking up provider-specific settings
Not or less affected:
- users who already know the correct direct docs URLs
- users browsing the current docs site `docs.openclaw.ai`
If you want, I can also merge everything into one final issue body so you can paste it in one shot.
Bro, why did someone else talk in this thread instead of making their own?? Whatever, any changes yet on the plugin search thing?
Yeah, threads get messy sometimes š
Anyway, I just checked again, and nope, no change yet:
- plugin search still returns 500
- page 3 of the plugin catalog still returns 500
- issue https://github.com/openclaw/clawhub/issues/1699 is still open with no update
So, still busted right now.
Ugh, this is so annoying...
Yeah, I know, thatās frustrating.
And worse, itās clearly not just user error, the site is actually broken right now.
If you want, tell me what plugin youāre trying to find and I can help dig it up manually as a workaround.
Still no changes?
Nope, still no fix on the site side.
I just re-tested it:
- plugin search still 500s
- page 3 of the plugin catalog still 500s too
So yeah, still broken.
How about now?
Still broken, unfortunately.
I just checked again:
- search still returns 500
- page 3 of the plugin catalog still returns 500 too
So, no fix yet.
Perhaps you could help dig up the discord-voice plugin or whatever it's called?
Yep, I dug it up.
If you mean Discord voice channels, itās not a plugin called discord-voice.
Itās built into the Discord channel integration:
- docs: https://docs.openclaw.ai/channels/discord#voice-channels
- config:
channels.discord.voice - command:
/vc join,/vc leave,/vc status
If you meant the separate Voice Call plugin, the official package is:
@openclaw/voice-call- docs: https://docs.openclaw.ai/plugins/voice-call
Install command from the docs:
openclaw plugins install @openclaw/voice-call
So, short version:
- Discord voice channel support ā built-in Discord voice feature
- Voice Call plugin ā
@openclaw/voice-call
If you want, I can help you figure out which one you actually need.
Just whatever one is needed for this: https://clawhub.ai/adriel1006/discord-voice-deepgram
Yep, for that exact page, the one you want is the community plugin:
- install/add name:
deepgram-discord-voice - config entry:
plugins.entries.deepgram-discord-voice - required env/config:
DISCORD_TOKEN,DEEPGRAM_API_KEY
So this is not the official @openclaw/voice-call plugin I mentioned earlier.
Itās a separate third-party plugin specifically for:
- Discord voice channel input
- Deepgram streaming STT
- Deepgram TTS back into the voice channel
One important note: ClawHubās scan on that page flags it as Suspicious (medium confidence), mainly because it appears to invoke an embedded agent with fairly broad access. So Iād review it a bit before installing, especially on anything important.
If you want, I can help you figure out the actual install path/config for deepgram-discord-voice next.
Or wait, it might be this instead: https://clawhub.ai/avatarneil/discord-voice
Yeah, this second one looks like the more likely match if you want a general Discord voice plugin.
Quick breakdown:
-
avatarneil/discord-voice- generic Discord voice plugin
- config entry:
discord-voice - supports multiple STT/TTS backends
- can use Deepgram, but also OpenAI / ElevenLabs / local whisper
-
adriel1006/discord-voice-deepgram- more specifically built around Deepgram
- config entry:
deepgram-discord-voice
So if your goal is basically āmake OpenClaw talk/listen in a Discord voice channelā, discord-voice is probably the one you meant.
One big caveat though: if you just want official/current Discord voice support, OpenClaw already has built-in Discord voice docs here:
https://docs.openclaw.ai/channels/discord#voice-channels
So the order Iād think about it is:
- Built-in
channels.discord.voiceif that covers your use case discord-voiceif you specifically want this community plugindeepgram-discord-voiceonly if you want that Deepgram-specific version
If you want, I can help you compare built-in Discord voice vs discord-voice so you donāt install the wrong thing.
Sure! But I would still like to know which plugin I need for the discord-voice skill and where I can find it and install it.
Got it. If you mean the ClawHub skill/package from that page, the one youāre looking for is:
- package / install name:
discord-voice - direct page: https://clawhub.ai/avatarneil/discord-voice
So because search is busted, just use the direct URL above.
For install, the page is using older wording (clawdhub), but the current CLI name is clawhub. So the package name youād use is:
clawhub install discord-voice
And inside the config example, the entry name is also:
plugins.entries["discord-voice"]
Important distinction:
- If you want that specific community ClawHub package ā
discord-voice - If you just want official Discord voice support in OpenClaw ā you may not need any extra package at all, just the built-in Discord voice feature:
https://docs.openclaw.ai/channels/discord#voice-channels
If you want, next I can help you figure out whether you should use the built-in Discord voice feature or install discord-voice.
But does that package require a plugin, or...?
Yeah, the naming is confusing.
For that discord-voice ClawHub package, you do not need some extra second plugin on top of it.
That package is the thing you install, and then it shows up under:
plugins.entries["discord-voice"]
So the two paths are basically:
-
Built-in OpenClaw Discord voice
- no extra ClawHub package needed
- use
channels.discord.voice - docs: https://docs.openclaw.ai/channels/discord#voice-channels
-
Community ClawHub package
discord-voice
- install that package itself
- then configure
plugins.entries["discord-voice"]
- then configure
So, short answer: no extra plugin beyond discord-voice itself, if you choose that route.
Wait, actually...
Require stack:
- C:\Users\KarleeTDM\.openclaw\extensions\discord-voice\index.ts (plugin=discord-voice, source=C:\Users\KarleeTDM\.openclaw\extensions\discord-voice\index.ts)```
Ah, thatās a different problem, and a much more concrete one.
That error usually means the plugin was found, but its own dependencies were not installed correctly.
@sinclair/typebox is a package that discord-voice expects to exist inside its plugin folder.
First, please paste:
openclaw --version
Then, on Windows, Iād try this in PowerShell:
cd $env:USERPROFILE\.openclaw\extensions\discord-voice
dir package.json
pnpm install
pnpm build
openclaw gateway restart
What Iām checking there:
package.jsonexists- the pluginās dependencies actually get installed
- if it has a build step, it gets built before the gateway loads it again
If pnpm build says there is no build script, that part is fine, just skip it.
If package.json is missing, or pnpm install still does not install @sinclair/typebox, then this community plugin package is probably not packaged correctly for your setup, and Iād stop fighting that specific one.
Docs:
- Troubleshooting: https://docs.openclaw.ai/gateway/troubleshooting
If you want, send:
openclaw --version- the output of
pnpm install - whether
package.jsonexists in that folder
and Iāll help you narrow it down.
pnpm : The term 'pnpm' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
- pnpm install
-
+ CategoryInfo : ObjectNotFound: (pnpm:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
pnpm : The term 'pnpm' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:2 char:1
- pnpm build
-
+ CategoryInfo : ObjectNotFound: (pnpm:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
No worries, that just means pnpm isnāt installed or isnāt on PATH yet.
First, please paste these:
openclaw --version
node -v
Then try this in PowerShell:
corepack enable
corepack prepare pnpm@latest --activate
After that, close and reopen PowerShell, then run:
cd $env:USERPROFILE\.openclaw\extensions\discord-voice
pnpm install
pnpm build
openclaw gateway restart
If pnpm build says there is no build script, thatās fine, just ignore that part.
So the likely chain here is:
- plugin loads
- plugin dependency is missing
- pnpm also isnāt available yet
- once pnpm is available, the plugin deps can probably be installed properly
If corepack is also ānot recognizedā, send me that output too and Iāll give you the next Windows step.
PS C:\Users\KarleeTDM.openclaw\extensions\discord-voice> openclaw --version
node -v
OpenClaw 2026.4.14 (323493f)
v25.6.0
PS C:\WINDOWS\System32> corepack enable
corepack prepare pnpm@latest --activate
corepack : The term 'corepack' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
- corepack enable
-
+ CategoryInfo : ObjectNotFound: (corepack:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
corepack : The term 'corepack' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:2 char:1
- corepack prepare pnpm@latest --activate
-
+ CategoryInfo : ObjectNotFound: (corepack:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
Nice, that helps.
Your OpenClaw version looks fine enough for this. The immediate problem is just that pnpm/corepack isnāt available on your PATH.
Try this next in PowerShell:
npm install -g pnpm
pnpm --version
If that works, then go back to the plugin folder and run:
cd $env:USERPROFILE\.openclaw\extensions\discord-voice
pnpm install
pnpm build
openclaw gateway restart
If pnpm build says there is no build script, thatās okay, just skip it.
One side note: youāre on Node v25.6.0, which is a bit unusual. It may not be the blocker here, but if weird plugin/runtime problems keep happening, Iād much rather see Node 22 LTS.
If npm install -g pnpm fails, paste that output and Iāll keep going with you.
PS C:\WINDOWS\System32> npm install -g pnpm
pnpm --version
added 1 package in 4s
1 package is looking for funding
run npm fund for details
10.33.0
index.ts:19:118 - error TS2307: Cannot find module './src/config.js' or its corresponding type declarations.
19 import { parseConfig, getAvailableModels, DEFAULT_NO_EMOJI_HINT, sanitizeNoEmojiHint, type DiscordVoiceConfig } from "./src/config.js";
~~~~~~~~~~~~~~~~~
index.ts:20:40 - error TS2307: Cannot find module './src/voice-connection.js' or its corresponding type declarations.
20 import { VoiceConnectionManager } from "./src/voice-connection.js";
~~~~~~~~~~~~~~~~~~~~~~~~~~~
index.ts:21:52 - error TS2307: Cannot find module './src/core-bridge.js' or its corresponding type declarations.
21 import { loadCoreAgentDeps, type CoreConfig } from "./src/core-bridge.js";
~~~~~~~~~~~~~~~~~~~~~~
index.ts:314:20 - error TS7006: Parameter 'p' implicitly has an 'any' type.
314 .filter((p) => p.text && !p.isError)
~
index.ts:315:17 - error TS7006: Parameter 'p' implicitly has an 'any' type.
315 .map((p) => p.text?.trim())
~
index.ts:445:20 - error TS7006: Parameter 's' implicitly has an 'any' type.
445 .filter((s) => !guildId || s.guildId === guildId)
~
index.ts:446:17 - error TS7006: Parameter 's' implicitly has an 'any' type.
446 .map((s) => {
~
index.ts:701:57 - error TS7006: Parameter 's' implicitly has an 'any' type.
701 const sessions = vm.getAllSessions().map((s) => {
~
Found 8 errors in the same file, starting at: index.ts:19
ELIFECYCLEā Command failed with exit code 2.
Okay, that makes it pretty clear, and honestly Iām glad we caught it.
This does not look like your local setup anymore.
That package appears to be incomplete/broken.
Why Iām saying that:
index.tsis trying to import:./src/config.js./src/voice-connection.js./src/core-bridge.js
- but those files are apparently not present in the installed bundle
So the plugin package itself looks bad or only partially uploaded. Thatās why it loads badly and then fails to build.
You can confirm with:
cd $env:USERPROFILE\.openclaw\extensions\discord-voice
dir
dir src
If src is missing or incomplete, thatās the smoking gun.
My recommendation
At this point, I would stop fighting this community package and use the official built-in Discord voice support instead:
https://docs.openclaw.ai/channels/discord#voice-channels
That route does not depend on this broken discord-voice bundle.
So short version:
pnpmproblem: fixed
- dependency problem: partly fixed
- current blocker: the plugin package itself is broken
If you want, I can help you switch gears and set up the built-in Discord voice path instead.
Wait!! I see config.ts, voice-connection.ts, and core-bridge.ts! The files are there, but in .ts instead of .js!!
Oh, good catch, and that changes the read a lot.
If those .ts files are there, then the package is not missing source files.
Whatās probably happening is:
pnpm installfixed the missing dependencypnpm buildis failing because the pluginās TypeScript build config is a bit wonky- but that build step may not actually matter if OpenClaw is loading
index.tsdirectly anyway
In other words, the important error was this one:
Cannot find module '@sinclair/typebox'
You may have already fixed that by installing deps.