502 bad gateway

[danieljvdm]

I follow the instructions and install the template on Railway and the public address just gives:

There are no meaningful deploy logs to point towards what might be happening

[danieljvdm]

Fixed by changing port to 8080. Might wanna update docs with that

[cktang88]

same

[surya7938]

+1, able to resolve by updating port number to 8080 under Networking -> Public Networking settings

[vignesh07]

Added better diagnostics for 502 / “Application failed to respond” cases in #74 (merged).

Next steps:

• Visit /setup → Debug Console (to see if gateway is starting)
• Visit /setup/api/debug and paste the JSON here — it now includes config path resolution + the last gateway start error.

[vignesh07]

Most 502s on Railway for this template are due to Public Networking routing to the wrong target port.

Checklist:

• Set the service domain target port to 8080 (Railway defaults to 3000 sometimes)
• Check /healthz and /setup/api/debug for gateway start errors

Closing as needs-info; reopen with the debug output if this persists after fixing the target port.

[vignesh07]

Closing as needs-info / likely Railway target port config. Reopen with /healthz + /setup/api/debug if still failing.