Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/basebalance-cloud-x402-rpc-mcp-gateway/issues.md or /mcp/basebalance-cloud-x402-rpc-mcp-gateway/issues.json, or Pod over MCP.

Reported issues for basebalance.cloud — x402 RPC & MCP gateway

Pod holds 14 of 14 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to basebalance.cloud — x402 RPC & MCP gateway.

Most discussed

CRITICAL BUG: Charged for VM creation, but sandbox is missing/inaccessible (refund or restore requested)

Critical issue encountered:

I hit a billing/provisioning mismatch and need help.

Account / wallet:

Issue summary:

Evidence:

Read the thread · 2026-02-20 · open · external user · 9 comments

SIWE provisioning fails: POST /v1/auth/verify returns 500 Database error (fresh wallet)

Summary

Provisioning a Conway API key for a new automaton fails consistently. POST /v1/auth/verify returns 500 {"error":"Database error"} on every attempt over several hours (2026-07-17, ~13:40–14:36 UTC).

Steps to reproduce

  1. Fresh EVM wallet generated by the automaton runtime (v0.2.1, macOS, Node v24.14.0)
  2. POST https://api.conway.tech/v1/auth/nonce → 200, returns nonce (works fine)
  3. Build SIWE message exactly as in src/identity/provision.ts (domain conway.tech, uri…

Read the thread · 2026-07-17 · open · external user · 3 comments

SIWE provisioning fails with 500 Database error

SIWE provisioning fails with 500 Database error

Commit: 871c53e (v0.2.1) Chain: Base (8453)

Reproduction

Error

Provision failed: SIWE verification failed: 500 {"error":"Database error"}

Wallet

Automaton: "0x82aae527923dC22607472Dbf7De89f392304bF17"

Creator: "0xD8a4BA197b2e424656d23B638723683b9eDDeF14"

This reproduces consistently on a fresh Ubuntu 24.04 VPS.

Read the thread · 2026-08-27 · open · external user · 2 comments

Provision fails with SIWE verification: "Invalid or expired nonce" (401) on Windows v0.2.1

Environment

Problem

I cannot provision a new Automaton agent.

Running:

node dist/index.js --provision

always returns:

Provision failed: SIWE verification failed: 401 {"error":"Invalid or expired nonce"}

What I've verified

Read the thread · 2026-07-27 · open · external user · 2 comments

SIWE provisioning fails with HTTP 500 Database error

Conway Terminal SIWE provisioning fails with HTTP 500 Database error.

Environment:

Diagnostics:

Request ID: 68a1aade-41cc-49b8-bd17-a6b2a0a0737b

The API key has not been created. No funds have been deposited or spent.…

Read the thread · 2026-08-20 · closed · external user · 1 comment

SIWE provisioning fails with "Invalid or expired nonce" (401) — reproducible on latest main

Running node dist/index.js --provision (and the same step inside the first-run setup wizard) consistently fails with:

{"level":"error","module":"main","message":"Provision failed: SIWE verification failed: 401 {"error":"Invalid or expired nonce"}"}

Steps to reproduce

  1. git clone https://github.com/Conway-Research/automaton.git
  2. npm install && npm run build
  3. node dist/index.js --run (or node dist/index.js --provision directly)
  4. Reaches step [2/6] "Provisioning Conway API key…

Read the thread · 2026-08-05 · open · external user · 1 comment

SIWE provisioning fails with "Invalid or expired nonce" despite fast round-trip and correct clock

Describe the bug --provision (and auto-provision during setup wizard) consistently fails with a 401 "Invalid or expired nonce" error from /v1/auth/verify, even though the nonce-fetch-to-verify round trip completes in under 500ms.

Environment

  1. Run node dist/index.js --setup (or hit auto-provision during first-run wizard)
  2. Select EVM chain, generate wallet 3.…

Read the thread · 2026-07-28 · open · external user · 1 comment

SIWE provisioning fails with 500 Database error on /v1/auth/verify

I can reproduce this on the current main branch (d8f8168).

Environment:

Reproduction:

  1. POST https://api.conway.tech/v1/auth/nonce returns 200 with a fresh nonce.

  2. I immediately construct and sign a SIWE message using:

    • domain: conway.tech
    • chain ID: 8453 (Base)
    • URI: https://api.conway.tech/v1/auth/verify
    • the exact nonce returned by the API

  3. I…

Read the thread · 2026-08-29 · open · external user · 0 comments

Most recent

Provisioning fails — SIWE endpoint not issuing nonce (401 Invalid or expired nonce)

Description Provisioning consistently fails with a SIWE 401 error. The backend appears to be not issuing a nonce at all, even when running with --debug.

This is not a client‑side issue — Windows time is synchronized, caches cleared, reinstall done, and no SIWE registry key exists. Debug mode returns no SIWE payload, indicating the backend rejects the session before nonce generation.

Error Code Provision failed: SIWE verification failed: 401 {"error":"Invalid or expired nonce"} Environment…

Read the thread · 2026-08-26 · open · external user · 0 comments

SIWE provisioning fails: /v1/auth/verify returns 500 Database error / 401 Invalid or expired nonce

--provision fails for all wallets: /v1/auth/verify returns 500 Database error (new address) or 401 Invalid or expired nonce (existing address).

Signature verification itself passes — a deliberately bad signature produces a different, earlier error (400 Verification failed), so the SIWE message and signing in src/identity/provision.ts are behaving correctly. The failure is downstream of signature checking.

Reproduction

Run automaton --provision with an EVM wallet.…

Read the thread · 2026-08-22 · open · external user · 0 comments

Windows: HOME env var defaults to /root causing invalid paths; SIWE provisioning fails with "Invalid or expired nonce" on --provision

Environment

Bug 1: HOME environment variable defaults incorrectly on Windows

src/identity/wallet.ts resolves the automaton directory as:

const AUTOMATON_DIR = path.join(process.env.HOME || "/root", ".automaton");

On Windows, HOME is typically unset (Windows uses USERPROFILE instead), so this falls back to /root, which resolves to an invalid path like…

Read the thread · 2026-07-27 · open · external user · 0 comments

Same issue here — USDC on wallet, $0 credits, billing UI broken

Same issue here — USDC on wallet, $0 credits, billing UI broken

Setup:

Problem:

Read the thread · 2026-02-19 · open · external user · 0 comments

Port exposure returns 404 despite successful API response

Bug Report

Summary

sandbox_expose_port API returns a successful response with a public URL, but the URL returns 404. The reverse proxy does not appear to route traffic to the sandbox.

Steps to Reproduce

  1. Create a sandbox (Large tier, us-east)
  2. Start a server listening on port 8888 (confirmed with ss -tlnp, binding to *:8888)
  3. Expose the port via API:
POST /v1/sandboxes/:id/ports
{ "port": 8888 }
  1. API returns success:
{
  "port": 8888,
  "visibility":…

[Read the thread](https://github.com/Conway-Research/automaton/issues/90) · 2026-02-19 · open · external user · 0 comments

### Sandbox created but immediately inaccessible — requesting  refund

## Description

Created a Medium sandbox via MCP (`sandbox_create`), which returned a successful response with ID `128c218be42d8882baacab0d26e6d4ce`. However:

- `sandbox_exec` immediately returns `403: Sandbox not found or access denied`
- `sandbox_get` returns the same 403
- `sandbox_list` returns an empty array
- `sandbox_terminal_session` returns the same 403
- Terminal URL returns "Authentication required" and there's no way to obtain a session
- $8 was deducted from credits (balance went…

[Read the thread](https://github.com/Conway-Research/automaton/issues/53) · 2026-02-18 · closed · external user · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/Conway-Research/automaton.git/issues).