Hi… This would be the internal_port, in fly.toml.
You can get a little more context in the following two recent forum threads:
- https://community.fly.io/t/setting-up-litefs-with-the-proxy-and-docker/20927
- https://community.fly.io/t/litefs-warning-the-app-is-not-listening-on-the-expected-address-and-will-not-be-reachable/21311
(Note that the second is not precisely your own situation, but the overall debugging steps, etc., are related.)
LiteFS is a niche database with still a few rough edges, particularly with regard to fly launch auto-configuration.
Basically, you have to roll up your sleeves a fair amount initially…