# Rails launch improvements (dockerfile-rails@1.6.7 w/ flyctl@0.2.22)

**URL:** <https://community.fly.io/t/rails-launch-improvements-dockerfile-rails-1-6-7-w-flyctl-0-2-22/18830>\
**Category:** Fresh Produce\
**Created:** [March 19, 2024, 1:34am UTC](https://community.fly.io/t/rails-launch-improvements-dockerfile-rails-1-6-7-w-flyctl-0-2-22/18830 "2024-03-19T01:34:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![miharekar](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/miharekar/32/14766_2.png) [@miharekar](https://community.fly.io/u/miharekar)\
**Post date:** [September 27, 2024, 9:09am UTC](https://community.fly.io/t/rails-launch-improvements-dockerfile-rails-1-6-7-w-flyctl-0-2-22/18830/2 "2024-09-27T09:09:39Z")

</div>

I can’t get thruster to work. I updated the ports in fly.toml to 80, but then I get this:

```auto
2024-09-27T09:05:07Z app[4d89626bee5128] fra [info] INFO Preparing to run: `/rails/bin/docker-entrypoint ./bin/thrust ./bin/rails server` as 1000
2024-09-27T09:05:07Z app[4d89626bee5128] fra [info] INFO [fly api proxy] listening at /.fly/api
2024-09-27T09:05:07Z app[4d89626bee5128] fra [info]2024/09/27 09:05:07 INFO SSH listening listen_address=[fdaa:0:c61d:a7b:cbb7:64a0:b6ee:2]:22 dns_server=[fdaa::3]:53
2024-09-27T09:05:07Z runner[4d89626bee5128] fra [info]Machine created and started in 3.633s
2024-09-27T09:05:08Z app[4d89626bee5128] fra [info]{"time":"2024-09-27T09:05:08.635895771Z","level":"DEBUG","msg":"No custom 502 page found","path":"./public/502.html"}
2024-09-27T09:05:08Z app[4d89626bee5128] fra [info]{"time":"2024-09-27T09:05:08.636404222Z","level":"INFO","msg":"Server started","http":":80"}
2024-09-27T09:05:08Z health[4d89626bee5128] fra [error]Health check on port 80 has failed. Your app is not responding properly.
2024-09-27T09:05:11Z app[4d89626bee5128] fra [info]=> Booting Puma
2024-09-27T09:05:11Z app[4d89626bee5128] fra [info]=> Rails 8.0.0.beta1 application starting in production
2024-09-27T09:05:11Z app[4d89626bee5128] fra [info]=> Run `bin/rails server --help` for more startup options
2024-09-27T09:05:15Z app[4d89626bee5128] fra [info]Puma starting in single mode...
2024-09-27T09:05:15Z app[4d89626bee5128] fra [info]* Puma version: 6.4.3 (ruby 3.3.5-p100) ("The Eagle of Durango")
2024-09-27T09:05:15Z app[4d89626bee5128] fra [info]* Min threads: 3
2024-09-27T09:05:15Z app[4d89626bee5128] fra [info]* Max threads: 3
2024-09-27T09:05:15Z app[4d89626bee5128] fra [info]* Environment: production
2024-09-27T09:05:15Z app[4d89626bee5128] fra [info]* PID: 333
2024-09-27T09:05:15Z app[4d89626bee5128] fra [info]* Listening on http://0.0.0.0:3000
2024-09-27T09:05:15Z app[4d89626bee5128] fra [info]Use Ctrl-C to stop
error.message="instance refused connection. is your app listening on 0.0.0.0:80? make sure it is not only listening on 127.0.0.1 (hint: look at your startup logs, servers often print the address they are listening on)" 2024-09-27T09:05:24Z proxy[4d89626bee5128] fra [error]request.method="GET" request.id="01J8SBMM89XMN07HPF7R08A5QH-iad"
2024-09-27T09:05:54Z proxy[4d89626bee5128] fra [error][PC01] instance refused connection. is your app listening on 0.0.0.0:80? make sure it is not only listening on 127.0.0.1 (hint: look at your startup logs, servers often print the address they are listening on)

```

Should they remain on 3000? Will thruster even be involved then? 🤔

---

_[View the full topic](https://community.fly.io/t/rails-launch-improvements-dockerfile-rails-1-6-7-w-flyctl-0-2-22/18830)._