Hi, I have a Node.js Express server deployed on Railway (whoop-mcp-server service). The server is running successfully and shows in the logs: * "WHOOP MCP Server running on port 3000" * "Ready for Claude iOS integration" * "Health check: GET /health" * Status shows ACTIVE and "Deployment successful" **However, when I try to access HTTP endpoints through the domain, they all return 404 "Not Found":** Test endpoint: ``` https://whoop-mcp-server-production-d584.up.railway.app/health ``` Expected response: json ```json {"status":"ok"} ``` Actual response: 404 Not Found **What I've tried:** * Waited for full deployment (2-3 minutes) * Tested in incognito/private browser * Checked environment variables (all 5 set correctly) * Server logs show no errors * Tested in multiple browsers **Details:** * Service: whoop-mcp-server * Region: us-east4 * Node version: 18.20.8 * Status: Online (green dot) The server is clearly running (confirmed by logs), but requests aren't reaching the endpoints. Could this be a domain routing or network configuration issue? Error Reference IDs from Claude: `c72d86f178fdfecc2` Thank you!

HTTP Endpoints Returning 404 Despite Server Running Successfully

fazeehun-bot

FREEOP

3 months ago

Hi,

I have a Node.js Express server deployed on Railway (whoop-mcp-server service). The server is running successfully and shows in the logs:

"WHOOP MCP Server running on port 3000"
"Ready for Claude iOS integration"
"Health check: GET /health"
Status shows ACTIVE and "Deployment successful"

However, when I try to access HTTP endpoints through the domain, they all return 404 "Not Found":

Test endpoint:

https://whoop-mcp-server-production-d584.up.railway.app/health

Expected response:

json

{"status":"ok"}

Actual response: 404 Not Found

What I've tried:

Waited for full deployment (2-3 minutes)
Tested in incognito/private browser
Checked environment variables (all 5 set correctly)
Server logs show no errors
Tested in multiple browsers

Details:

Service: whoop-mcp-server
Region: us-east4
Node version: 18.20.8
Status: Online (green dot)

The server is clearly running (confirmed by logs), but requests aren't reaching the endpoints. Could this be a domain routing or network configuration issue?

Error Reference IDs from Claude: c72d86f178fdfecc2

Thank you!

$10 Bounty

2 Replies

Status changed to Awaiting Railway Response Railway • 3 months ago

darseen

HOBBYTop 1% Contributor

3 months ago

Are you using the PORT env variable provided by Railway in your express server config (process.env.PORT)? And make sure the port you're using in your code is the same port your url is mapped to in your Service Settings > Networking.

soresu

HOBBY

3 months ago

Under the network part in the settings, enable Private Networking and redeploy.

Welcome!