Infrastructure: How to resolve AX42 missing from dashboard and naming confus...

Documentation for Sessions

📝 Infrastructure: How to resolve AX42 missing from dashboard and naming confus...

Date: 2026-03-28
Time: 12:23:06 UTC
Session: gspace1-282.5
Agent: orchestrator
Confidence: 95%
Status: ✅ Documented


📋 Decision Context

Question:

How to resolve AX42 missing from dashboard and naming confusion between sandbox.gograb.space and ax42-01.gograb.space?

Task: Fix Hetzner dual-server infrastructure: AX42 missing from dashboard, rename sandbox.gograb.space → ax42-01.gograb.space


🎯 Decision Made

Chosen:

Two fixes: (1) SELF_HOSTED_INFRA_JSON had wrong healthUrl (ax102-01 instead of AX42's URL) — dedup in getSelfHostedEntries() silently dropped the AX42 entry. (2) Rename sandbox.gograb.space → ax42-01.gograb.space across entire codebase to match ax102-01.gograb.space naming convention. Git fallback in git.service.ts correctly points to ax102-01 (where git repos live), not ax42-01.

Options Considered:

  1. Keep sandbox.gograb.space and only fix the healthUrl bug
  2. Rename to ax42-01.gograb.space across entire codebase for consistency

💭 Reasoning

The dedup logic in HetznerInfraService.getSelfHostedEntries() uses a Set keyed by healthUrl. SANDBOX_SERVER_URL (ax102-01) was registered first, then SELF_HOSTED_INFRA_JSON had the same URL for the AX42 entry → silently skipped. The naming rename (sandbox → ax42-01) prevents future confusion: both servers now follow the {hardware-class}-{sequence}.gograb.space pattern. Critical distinction: PLATFORM_GIT_SERVER_URL and git.service.ts fallback must remain ax102-01 because git repos were moved there in S260.


📁 Files Involved


🔗 Related


Auto-generated by MCP Smart Consolidation