Wrong Port, Right Service

The deployment looks healthy, but production traffic lands on an admin-only process. The service map was changed during a port cleanup.

Initial failing signalClient resolves the admin port for public trafficExpected behavior: Public traffic resolves to port 3000. · actual behavior: Public traffic resolves to the admin port, 3001.

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Compare the process reached by health checks with the process receiving user traffic.
Trace service names through configuration and runtime port resolution.
Restore consistent routing without exposing the admin process.

Focus Mode

Start

src/service-map.js

Likely area

src/service-map.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicNetwork & Connectivity

DifficultyEasy

Est. time14 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace