fix(cipher-api): PORT env mismatch causes permanent unhealthy (415 failing streak) - #2357
Conversation
cipher-api was unhealthy (415 failing streak) because the ByteRover upstream Dockerfile hardcodes PORT=3000, but the PMOVES compose sets PMOVES_PORT=8105 (which the upstream code ignores). The CMD reads $PORT, so the app listened on :3000 inside the container while the healthcheck probed :8105 and the port mapping bound host 8105 to container 8105. Adding PORT=8105 as a compose env override aligns the app's listen port with the healthcheck, port mapping, and all downstream service references (CIPHER_URL, CIPHER_MCP_URL, CIPHER_MEMORY_URL all use :8105). 💘 Generated with Crush Assisted-by: Crush:glm-5.2
|
Warning Review limit reached
Next review available in: 17 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Docker Hardening ValidationHardening Validation ReportValidated: Mon Aug 3 15:15:13 UTC 2026Services CheckedPMOVES.AI Docker Hardening Validation[INFO] Checking: pmoves/docker-compose.hardened.yml [INFO] Validating: hi-rag-gateway-v2 [INFO] Validating: extract-worker [INFO] Validating: langextract [INFO] Validating: presign [INFO] Validating: render-webhook [INFO] Validating: retrieval-eval [INFO] Validating: pdf-ingest [INFO] Validating: jellyfin-bridge [INFO] Validating: invidious-companion-proxy [INFO] Validating: ffmpeg-whisper [INFO] Validating: media-video [INFO] Validating: media-audio [INFO] Validating: hi-rag-gateway-v2-gpu [INFO] Validating: hi-rag-gateway-gpu [INFO] Validating: deepresearch [INFO] Validating: supaserch [INFO] Validating: publisher-discord [INFO] Validating: mesh-agent [INFO] Validating: nats-echo-req [INFO] Validating: nats-echo-res [INFO] Validating: comfy-watcher [INFO] Validating: grayjay-plugin-host [INFO] Validating: agent-zero [INFO] Validating: p7-room-orchestrator [INFO] Validating: archon [INFO] Validating: channel-monitor [INFO] Validating: pmoves-yt [INFO] Validating: notebook-sync [INFO] Validating: supabase_service_role_key [INFO] Validating: supabase_jwt_secret [INFO] Validating: p7_control_token ====================================== |
Regenerated via make compose-split. cipher-api PORT=8105 fix (#2357) confirmed present in both source and generated agents overlay — survives secrets-funnel (funnel only touches env files, not compose). 💘 Generated with Crush Assisted-by: Crush:glm-5.2
Summary
cipher-api has been unhealthy for 3+ hours with a 415-streak healthcheck failure. Root cause: the ByteRover upstream Dockerfile hardcodes
PORT=3000, but PMOVES compose sets onlyPMOVES_PORT=8105— which the upstream code ignores. The CMD (node ... --port $PORT) reads$PORT, so the app listens on:3000inside the container while::8105(always connection refused)8105→ container8105(nothing there):8105Fix: Add
PORT=8105as a compose env override in bothdocker-compose.ymlanddocker-compose.agents.yml. This aligns the app's listen port with the healthcheck, port mapping, and all downstream service references.This is z890-Claude's #1 blocker — "the memory stack is one service short, cipher-api is unhealthy so the write path isn't provable end-to-end."
1-line fix per file, backwards-compatible, no secrets.
💘 Generated with Crush