Skip to content

Bug: api.bugster.dev does not resolve DNS — all test runs fail with MCP timeout #3

@JonathanCh-GSS

Description

@JonathanCh-GSS

Environment

  • Bugster CLI: 0.8.12
  • OS: Windows 11
  • Install method: GitHub Releases zip (bugster-windows.zip)

Symptom

Every bugster run fails with the same exception after exactly 60 seconds, regardless of test content or whether the dashboard run is created successfully:

Exception: MCP client initialization timed out for test

All 4 generated tests fail identically. Runs do appear in the dashboard at app.bugster.dev, so authentication works — only the MCP connection step fails.

Root cause (confirmed)

api.bugster.dev does not resolve DNS publicly:

PS> Test-NetConnection api.bugster.dev -Port 443
WARNING: Name resolution of api.bugster.dev failed
PingSucceeded: False

PS> Resolve-DnsName api.bugster.dev -Server 8.8.8.8     # Google DNS — no records
PS> Resolve-DnsName api.bugster.dev -Server 1.1.1.1     # Cloudflare — no records
For comparison, app.bugster.dev resolves and TCP-connects fine on the same machine:


RemoteAddress    : 66.33.60.129
TcpTestSucceeded : True
No VPN, no proxy ($env:HTTP_PROXY, $env:HTTPS_PROXY, $env:NO_PROXY all unset).

Questions
Has the MCP / API endpoint been migrated to a different hostname?
Is there an env var or config override to point the CLI at a different API host?
Is 0.8.12 the correct version to be using, or is there a newer build that targets the updated endpoint?

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