openclaw/clawhub
1
0
Fork 0
mirror of https://github.com/openclaw/clawhub.git synced 2026-07-21 19:25:25 -04:00
Code Issues 183 Packages Projects Releases 1 Wiki Activity

[Bug]: CORS error and 404 on Skill Upload (auth.clawdhub.com domain mismatch) #74

New Issue
Closed
opened 2026-02-15 17:15:31 -05:00 by yindo · 5 comments
yindo commented 2026-02-15 17:15:31 -05:00
Owner
Copy Link
Copy Source

Originally created by @Grenghis-Khan on GitHub (Feb 5, 2026).

Summary

When publishing a skill on clawhub.ai/upload and clicking "Publish Skill" an error message shows below the button ""Server Error Called by client"" and a "Server Error", if I rename the skill the process fails with CORS errors and 404s. The console logs indicate a request is being made to auth.clawdhub.com (note the extra 'd'), which seemingly lacks the correct CORS headers for the clawhub.ai origin, preventing the skill from being verified or found after publish.

Steps to reproduce

  1. Go to https://clawhub.ai/upload.
  2. Upload a valid SKILL.md file.
  3. Click the "Publish Skill" button.
  4. (If "Server Error" occurs) Rename the skill and try again.

Expected behavior

The skill should publish successfully, be saved to the database, and be retrievable via the API without cross-origin blocking.

Actual behavior

The UI may show "Server Error called by client" or appear to publish but result in a "no skill found" state. The browser console shows that requests to the auth backend are blocked by CORS policy, and the resource is not found (404).

Environment

  • Interface: clawhub.ai web uploader
  • Browser: Chrome 144
  • OS: Windows

Logs or screenshots

# first publish
 [CONVEX A(skills:publishVersion)] [Request ID: 88xxxxxxxxx5cc] Server Error

# rename and publish
Access to fetch at 'https://auth.clawdhub.com/api/v1/skills/skillname' from origin 'https://clawhub.ai' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

GET https://auth.clawdhub.com/api/v1/skills/skillname net::ERR_FAILED 404 (Not Found)
Originally created by @Grenghis-Khan on GitHub (Feb 5, 2026). ## Summary When publishing a skill on clawhub.ai/upload and clicking "Publish Skill" an error message shows below the button ""Server Error Called by client"" and a "Server Error", if I rename the skill the process fails with CORS errors and 404s. The console logs indicate a request is being made to `auth.clawdhub.com` (note the extra 'd'), which seemingly lacks the correct CORS headers for the `clawhub.ai` origin, preventing the skill from being verified or found after publish. ## Steps to reproduce 1. Go to https://clawhub.ai/upload. 2. Upload a valid SKILL.md file. 3. Click the "Publish Skill" button. 4. (If "Server Error" occurs) Rename the skill and try again. ## Expected behavior The skill should publish successfully, be saved to the database, and be retrievable via the API without cross-origin blocking. ## Actual behavior The UI may show "Server Error called by client" or appear to publish but result in a "no skill found" state. The browser console shows that requests to the auth backend are blocked by CORS policy, and the resource is not found (404). ## Environment - Interface: clawhub.ai web uploader - Browser: Chrome 144 - OS: Windows ## Logs or screenshots ``` # first publish [CONVEX A(skills:publishVersion)] [Request ID: 88xxxxxxxxx5cc] Server Error # rename and publish Access to fetch at 'https://auth.clawdhub.com/api/v1/skills/skillname' from origin 'https://clawhub.ai' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. GET https://auth.clawdhub.com/api/v1/skills/skillname net::ERR_FAILED 404 (Not Found) ```
yindo closed this issue 2026-02-15 17:15:31 -05:00
yindo commented 2026-02-15 17:15:31 -05:00
Author
Owner
Copy Link
Copy Source

@Shaivpidadi commented on GitHub (Feb 5, 2026):

I’m also seeing the same failure. The issue is reproducible not only on Upload (/upload) but also on GitHub Import (/import) the skill appears to publish (or errors), and then verification / retrieval fails with “no skill found”

@Shaivpidadi commented on GitHub (Feb 5, 2026): I’m also seeing the same failure. The issue is reproducible not only on Upload (/upload) but also on GitHub Import (/import) the skill appears to publish (or errors), and then verification / retrieval fails with “no skill found”
yindo commented 2026-02-15 17:15:31 -05:00
Author
Owner
Copy Link
Copy Source

@Grenghis-Khan commented on GitHub (Feb 5, 2026):

I’m also seeing the same failure. The issue is reproducible not only on Upload (/upload) but also on GitHub Import (/import) the skill appears to publish (or errors), and then verification / retrieval fails with “no skill found”

same with the clawhub CLI tool. I published and got a ✔ OK. Published response but when I tried to install the skill

npx clawhub@latest install myskill
✖ Skill not found
Error: Skill not found

The issue is that cmdInstall makes an anonymous request, but new skills are often in a "pending scan" state (or private), which makes them invisible to anonymous users. The fix is to ensure clawhub install uses the authenticated user's token. Which it currently is not. Probably the same issue with the GitHub Import.

I might open another PR to try and address these as well

@Grenghis-Khan commented on GitHub (Feb 5, 2026): > I’m also seeing the same failure. The issue is reproducible not only on Upload (/upload) but also on GitHub Import (/import) the skill appears to publish (or errors), and then verification / retrieval fails with “no skill found” same with the clawhub CLI tool. I published and got a `✔ OK. Published` response but when I tried to install the skill ``` npx clawhub@latest install myskill ✖ Skill not found Error: Skill not found ``` The issue is that `cmdInstall` makes an anonymous request, but new skills are often in a "pending scan" state (or private), which makes them invisible to anonymous users. The fix is to ensure `clawhub install` uses the authenticated user's token. Which it currently is not. Probably the same issue with the GitHub Import. I might open another PR to try and address these as well
yindo commented 2026-02-15 17:15:32 -05:00
Author
Owner
Copy Link
Copy Source

@brookswood commented on GitHub (Feb 5, 2026):

I am experiencing the same issues

@brookswood commented on GitHub (Feb 5, 2026): I am experiencing the same issues
yindo commented 2026-02-15 17:15:32 -05:00
Author
Owner
Copy Link
Copy Source

@Grenghis-Khan commented on GitHub (Feb 5, 2026):

I updated the PR to address the CLI/github issues

@Grenghis-Khan commented on GitHub (Feb 5, 2026): I updated the PR to address the CLI/github issues
yindo commented 2026-02-15 17:15:32 -05:00
Author
Owner
Copy Link
Copy Source

@Bluecraft-AI commented on GitHub (Feb 5, 2026):

This is likely the root cause of #131 - my skill with 175 downloads vanished after update with the same "Server Error Called by client" message. Thanks for tracking this down.

@Bluecraft-AI commented on GitHub (Feb 5, 2026): This is likely the root cause of #131 - my skill with 175 downloads vanished after update with the same "Server Error Called by client" message. Thanks for tracking this down.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/clawhub#74
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?