App is being suspended even though I have auto_stop_machines set to "off" in fly.toml

Hey all! This is my first time deploying an app on Fly.io and I’m having a bit of trouble. I’m trying to deploy a discord bot and have found that after about 5 minutes of inactivity it gets suspended and goes offline, even though I have the auto_stop_machine setting in fly.toml turned off. Here is my current fly.toml:

app = 'my_bot'
primary_region = 'sea'

[[services]]
  internal_port = 8080
  protocol = "tcp"
  auto_start_machines = false
  auto_stop_machines = "off"
  min_machines_running = 1

Interestingly, it seems to be a bit different when I look at the configuration from my online dashboard. I’m not sure if it’s important, but here it is anyways.

app = "my_bot"
primary_region = "sea"

[[services]]
auto_start_machines = false
auto_stop_machines = false
internal_port = 8_080
min_machines_running = 1
protocol = "tcp"

I’ve seen a number of other posts that seem to have similar issues like this one, this one, and this one, all of which recommend setting auto_stop_machines to false which I’ve already done and it’s not fixing the problem. I also saw in the docs that it seems like "off" is the preferred setting now for some reason? I’m just generally really confused about why this is happening and would really appreciate any help that can be offered to get my bot up and running full time. Thanks!

Hey @Shock9616

It’s not autostop feature that’s stopping your machine. If you check your app’s logs (flyctl logs) you should see something like this:

Trial machine stopping. To run for longer than 5m0s, add a credit card by visiting https://fly.io/trial.

Oh yeah you’re so right. I thought the trial was a full 7-day trial. Ok thanks for your help :sweat_smile:

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