Skip to content

Dashboard returns HTTP 500 when approving restricted signer #75

Description

@am5188

Summary

Approving a newly generated CLI signer from the Virtuals dashboard fails with the toast Request failed with status code 500. The CLI request stays pending.

Environment

  • @virtuals-protocol/acp-cli: 1.0.29
  • macOS
  • Mainnet
  • Fresh ACP agent created successfully through the CLI
  • Policy: restricted / Virtuals Only

Reproduction

  1. Authenticate with the split acp configure start / complete flow.
  2. Create a fresh agent.
  3. Start the documented split signer flow with acp agent add-signer --agent-id <id> --no-wait --policy restricted --json.
  4. Open the returned dashboard URL and click Approve.

Actual result

The dashboard displays Request failed with status code 500. A subsequent acp agent signer-status ... --json continues returning {"status":"pending"}.

I reproduced this with two fresh request IDs/public keys. Authentication, agent creation, policy listing, and offering creation all work. I have not tried unrestricted because that would weaken the intended security boundary.

Expected result

The restricted signer is registered and signer-status returns completed, or the dashboard displays a specific actionable error.

Report prepared with AI assistance and reviewed before submission.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions