Failed Instances when deploying

Hi,

I’m trying to deploy a SolidStart application using the node adapter. The log looks fine:

2022-12-20T15:33:57.180 app[250bxxx] fra [info] > solid-start start
2022-12-20T15:33:57.722 app[250bxxx] fra [info] solid-start start
2022-12-20T15:33:57.722 app[250bxxx] fra [info] version 0.2.7
2022-12-20T15:33:59.333 app[250bxxx] fra [info] adapter node
2022-12-20T15:33:59.365 app[250bxxx] fra [info] ➜ Page Routes:
2022-12-20T15:33:59.365 app[250bxxx] fra [info] ┌─ http://localhost:3000/*404
2022-12-20T15:33:59.365 app[250bxxx] fra [info] ├─ http://localhost:3000/
...
2022-12-20T15:33:59.365 app[250bxxx] fra [info] ➜ API Routes:
...
2022-12-20T15:33:59.587 app[250bxxx] fra [info] Listening on port 3000

Yet the web app is not accessible.

Then after ~5 minutes I have this:

--> v1 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v2 
 1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 1 total, 1 critical]

Failed Instances
failed fetching alloc c7203bac-bd09-9861-f612-174677aa0ba7: context canceled

I’m not sure why…

I’m using fly deploy by the way.

Additional log:

Failed Instances

Failure #1

Instance
ID              PROCESS VERSION REGION  DESIRED STATUS  HEALTH CHECKS           RESTARTS    CREATED   
a4cd61f0        app     4       fra     run     running 1 total, 1 critical     0           4m55s ago

So apparently I forgot to specify the port

[env]
PORT = "8080" // <-- this line

[[services]]
  http_checks = []
  internal_port = 8080

The node process was running on 3000 while the internal port was 8080. If that was the issue. Glad it is solved, sad I lost so much time wondering what was I doing wrong Ôo

The fly.toml was generated by fly launch so I’m a bit surprised it was not there by default !