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

CLI: Auth fails due to redirect from clawhub.ai to www.clawhub.ai #48

New Issue
Open
opened 2026-02-15 17:15:21 -05:00 by yindo · 2 comments
yindo commented 2026-02-15 17:15:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @udiedrichsen on GitHub (Feb 2, 2026).

Bug Description

The clawdhub CLI fails to authenticate when using clawhub.ai as the registry URL because of a redirect to www.clawhub.ai that loses the Authorization header.

Steps to Reproduce

  1. Create an API token on clawhub.ai
  2. Run clawdhub login --token <token>
  3. Run clawdhub whoami

Result: ✖ Unauthorized

Root Cause

# This fails (307 redirect loses auth header):
curl -H "Authorization: Bearer <token>" https://clawhub.ai/api/v1/whoami
# Returns: Redirecting... → 401 Unauthorized

# This works:
curl -H "Authorization: Bearer <token>" https://www.clawhub.ai/api/v1/whoami
# Returns: {"user":{"handle":"..."}}

The redirect from clawhub.ai to www.clawhub.ai strips the Authorization header.

Workaround

Use --registry https://www.clawhub.ai flag:

clawdhub whoami --registry "https://www.clawhub.ai"
clawdhub publish . --registry "https://www.clawhub.ai"

Or update ~/.config/clawdhub/config.json:

{
  "registry": "https://www.clawhub.ai",
  "token": "..."
}

Suggested Fix

Either:

  1. Change default registry URL in CLI to https://www.clawhub.ai
  2. Or remove the redirect on the server side
  3. Or ensure the redirect preserves headers

Environment

  • clawdhub CLI: v0.3.0
  • Node.js: v24.12.0
  • OS: Ubuntu (ARM64)
Originally created by @udiedrichsen on GitHub (Feb 2, 2026). ## Bug Description The `clawdhub` CLI fails to authenticate when using `clawhub.ai` as the registry URL because of a redirect to `www.clawhub.ai` that loses the Authorization header. ## Steps to Reproduce 1. Create an API token on clawhub.ai 2. Run `clawdhub login --token <token>` 3. Run `clawdhub whoami` **Result:** `✖ Unauthorized` ## Root Cause ```bash # This fails (307 redirect loses auth header): curl -H "Authorization: Bearer <token>" https://clawhub.ai/api/v1/whoami # Returns: Redirecting... → 401 Unauthorized # This works: curl -H "Authorization: Bearer <token>" https://www.clawhub.ai/api/v1/whoami # Returns: {"user":{"handle":"..."}} ``` The redirect from `clawhub.ai` to `www.clawhub.ai` strips the Authorization header. ## Workaround Use `--registry https://www.clawhub.ai` flag: ```bash clawdhub whoami --registry "https://www.clawhub.ai" clawdhub publish . --registry "https://www.clawhub.ai" ``` Or update `~/.config/clawdhub/config.json`: ```json { "registry": "https://www.clawhub.ai", "token": "..." } ``` ## Suggested Fix Either: 1. Change default registry URL in CLI to `https://www.clawhub.ai` 2. Or remove the redirect on the server side 3. Or ensure the redirect preserves headers ## Environment - clawdhub CLI: v0.3.0 - Node.js: v24.12.0 - OS: Ubuntu (ARM64)
yindo commented 2026-02-15 17:15:22 -05:00
Author
Owner
Copy Link
Copy Source

@xolom commented on GitHub (Feb 2, 2026):

+1

@xolom commented on GitHub (Feb 2, 2026): +1
yindo commented 2026-02-15 17:15:22 -05:00
Author
Owner
Copy Link
Copy Source

@BrennerSpear commented on GitHub (Feb 3, 2026):

Workaround until the fix is merged:

CLAWHUB_REGISTRY=https://www.clawhub.ai clawhub login --token <your-token>

Or set the env var permanently:

export CLAWHUB_REGISTRY=https://www.clawhub.ai

This bypasses the redirect from clawhub.ai → www.clawhub.ai that strips the auth header.

@BrennerSpear commented on GitHub (Feb 3, 2026): **Workaround until the fix is merged:** ```bash CLAWHUB_REGISTRY=https://www.clawhub.ai clawhub login --token <your-token> ``` Or set the env var permanently: ```bash export CLAWHUB_REGISTRY=https://www.clawhub.ai ``` This bypasses the redirect from `clawhub.ai` → `www.clawhub.ai` that strips the auth header.
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#48
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?