Can you confirm that your PORT variable is set to the same port your app is listening on?

sure here we go

to be honest. I never had this set. and it always worked without this env var. but this morning out of the blue the deployment didnt work anymore.

then I ran a diagnosis and it told me to set the PORT env. did it. but still am not able to successfully run the health check

here my current Dockerfile:

ENV PORT=8080

COPY --from=installer /app .

EXPOSE 8080

CMD ["node", "--import", "./apps/scraper/dist/instrument.js", "apps/scraper/dist/app.js", "--mode", "daemon"]

and here my application:

  app.listen(port, "::", () => {

    logger.info("Server listening", { port });

    logger.info("Health check ready", {

      url: `http://localhost:${port}/health`,

    });

    logger.info("Bull Board UI ready", {

      url: `http://localhost:${port}/admin/queues`,

    });

  });

I do not have public routing enabled on this application/service.

weird this happened out of the blue. I disabled the health check and everything seems to work properly. here the logs:

{

  "message": "Server listening",

  "severity": "info",

  "attributes": {

    "label": "scraper",

    "level": "info",

    "metadata": {

      "port": 8080

    }

  },

  "timestamp": "2026-05-25T14:21:45.456790796Z"

}

its not solved. I just disabled the health check for a brief moment to see if the application even runs

ENV PORT=8080

COPY --from=installer /app .

EXPOSE 8080

CMD ["node", "--import", "./apps/scraper/dist/instrument.js", "apps/scraper/dist/app.js", "--mode", "daemon"]

figured the service did take too long to reply. had to increase the timeout