Hey there! We've found the following might help you get unblocked faster:

• 🧵 server closed the connection unexpectedly

• 🧵 ❗️ Java Spring Boot app not responding on Railway (HTTP 502 / 499)

• 🧵 DNS lookup for egress traffic randomly failing.

If you find the answer from one of these, please let us know by solving the thread!

hey, can you paste the exact start command that shows up in the deploy logs when it successfully deploys with Nixpacks?

Starting Container

> wrestling-roleplay-bot@1.0.0 start

> node wrestling.js

Wrestling bot API running on port 8080

npm warn config production Use --omit=dev instead.

your app hardcodes port 8080; that's why it only works on nixpacks (legacy port detection) and 499s on Railpack/Dockerfile

open wrestling.js and change the .listen line to:

const port = process.env.PORT || 8080;

app.listen(port, "0.0.0.0", () => { console.logWrestling bot api running on port ${port}); });

push and redeploy , lmk if it works

const PORT = process.env.PORT || 8000;

app.listen(PORT, () => console.logWrestling bot API running on port ${PORT}));

is what it is right now

changed to this, same error on railway deployment build

fix it like this exact copy-paste:

const port = process.env.PORT || 8080;

app.listen(port, "0.0.0.0", () => {
  console.log(`Wrestling bot API running on port ${port}`);
});

let me knew the result

tysvm!!! its not erroring now on post thank u!!!

solution accepted

awesome! glad it’s working now, If you hit any other issues just lmk

thank u will do

ok so its working but half the time its giving the error rest of the time working fine

perfect, now i think the "half the time" 499 is 100% classic Hobby plan cold starts, pro plan removes sleeping completely if you prefer

good night @cyberfights