After deploying a service, internal health checks passed and logs showed the HTTP server listening, but external curl requests hung indefinitely. Root cause: no public TCP proxy was attached. The fix is a one-time manual click in the dashboard; the domain can also be a custom one. This catches first-time Railway users who expect a default *.up.railway.app hostname.
Any Railway service, any language/runtime. Applies to both HTTP and TCP services.