Remix - Failed Due to Unhealthy Allocations.

Questions / Help
1

I’m making a remix app, and it was working fine, but for some reason it started giving this error when I tried to deploy:

Screen Shot 2022-04-10 at 1.56.24 PM
Screen Shot 2022-04-10 at 1.56.24 PM1920×1200 138 KB

fly.toml:

# fly.toml file generated for setela on 2022-04-10T12:05:56-03:00

app = "setela"

kill_signal = "SIGINT"
kill_timeout = 5
processes = []

[env]

[experimental]
  allowed_public_ports = []
  auto_rollback = true

[[services]]
  http_checks = []
  internal_port = 8080
  processes = ["app"]
  protocol = "tcp"
  script_checks = []

  [services.concurrency]
    hard_limit = 25
    soft_limit = 20
    type = "connections"

  [[services.ports]]
    force_https = true
    handlers = ["http"]
    port = 80

  [[services.ports]]
    handlers = ["tls", "http"]
    port = 443

  [[services.tcp_checks]]
    grace_period = "30s"
    interval = "15s"
    restart_limit = 0
    timeout = "2s"
2

When you say it was working fine … do you mean locally? Or … on Fly? Only that log output seems to end with it saying that Fly can’t find a version to revert back to. Which I’d assume it should be able to do if the prior version was working and deployed successfully. Strange.

One thing I did notice was your fly.toml doesn’t mention a PORT in the [env] block. Perhaps that is no longer needed, but when I compare it to e.g this one:

… that does specify 8080. So it’s possible the app is listening on another one (whatever it defaults to). If it’s not been told otherwise (via that env PORT).

Assuming that’s not it, have you followed the steps the Remix stack suggests? For example (this may not be applicable) their “blues” stack mentions setting secret values like SESSION_SECRET. Which I assume it relies on to work. So you’d need to set whatever values your stack needs.

It sounds like they have a choice of Indie and Blues. So one of these should help:

3

It was working fine on fly and locally.
I’ll try your solution