App keeps downscaling even though I've configured it not to.

Questions / Help
1

My Remix keeps downscaling with
Downscaling app xxx from 1 machines to 0 machines, stopping machine xxxx (region=sin, process group=app)

Even though I’ve configured it not to

app = "xxxx"
primary_region = "sin"
kill_signal = "SIGINT"
kill_timeout = 5
processes = [ ]

[experimental]
allowed_public_ports = [ ]
auto_rollback = true
cmd = "start.sh"
entrypoint = "sh"

[mounts]
source = "data"
destination = "/data"

[http_service]
  internal_port = 8080
  force_https = true
  auto_stop_machines = false
  auto_start_machines = true
  [http_service.concurrency]
    type = "requests"
    hard_limit = 250
    soft_limit = 200

Every time I check on the app, it has downscaled and when I visit it, it restarts.
Can someone please help me understand why this is?

2

Hi @brownbreadryedrought

Have you deployed your app after you set auto_stop_machines = false?

Looking at the records of app config on our side, it still has auto_stop_machines = true.

3

Thanks for checking this @pavel
Actually, I’m not sure if they deploy or not as my GitHub action to deploy keeps failing with this

✖ Machine xxx [app] update failed: timed out waiting for machine to reach started state: failed to wait for VM xxx in started state: Get "https://api.machines.dev/v1/apps/xxxx/machines/4d8917e9fe6678/wait?instance_id=xxxx&state=started&timeout=60": net/http: request canceled

Error: timed out waiting for machine to reach started state: failed to wait for VM xxx in started state: Get "https://api.machines.dev/v1/apps/xxx/machines/xxx/wait?instance_id=xxxx&state=started&timeout=60": net/http: request canceled

Do you have any idea how I can fix this?

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.