Runex

Troubleshooting

Port configuration

If a deployment shows as started but https://<slug>.runex.cloud does not respond, the process may be listening on the wrong port or only on localhost inside the container.

Checklist

  1. Bind your HTTP server to 0.0.0.0 (all interfaces), not only 127.0.0.1.
  2. Listen on the port your Runex runtime expects (check the dashboard or current runtime docs for the convention — often provided via PORT).
  3. For Docker, EXPOSE the same port your process uses and ensure the CMD/ENTRYPOINT starts the server.
  4. Re-read start logs for “address already in use” or immediate exits — see deployment failed.

Related