LiteFS & WARNING The app is not listening on the expected address and will not be reachable

[Zane_Milakovic]

I have seen this error, and I know there is this troubleshooting article available, but I think there is a gap with the Fly CLI and LiteFS.

I just started to get this error today, after not getting it before, so not sure what changed, it was not on my side.

I did check the following -

Troubleshoot your deployment

My fly.toml shows my internal_port of 8080, which is what the console says it should be in the warning.

BUT my app actually runs at 8081, because its the proxy for LiteFS that is at 8080.

Here is the app launching on 8081.

This is the configuration I have used for over 10 months.

Is the CLI wrong, is this a issue with LiteFS, is there a new setup or best practice I should be following?

Do I not benefit from the fly proxy if I get this warning?

[mayailurus]

@Zane_Milakovic

BUT my app actually runs at 8081, because its the proxy for LiteFS that is at 8080.

Right… The warning actually means the LiteFS proxy in this case, even though it says “app”.

It should have provided a list of things that it did find listening. Did that have anything interesting?

@Zane_Milakovic

This is the configuration I have used for over 10 months.

Well, auto-suspend is surely new, , but I think I see what you mean.

Since that’s an experimental feature, it might make sense to disable it for a while, and see if that ends up helping at all…

[Zane_Milakovic]

The presentation is a little broken, so all it gives me is 2 lines, and shows part of the machine update state, and then after a few ----- continues showing machine update state. So it’s unclear if its listing all the processes it actually found.

[mayailurus]

I would try checking from the inside, then. E.g., with a Debian-based image…

$ fly ssh console
# apt-get update
# apt-get install --no-install-recommends iproute2
# ss -tnlp

You should see things like the following (among others):

LISTEN  0  0 *:8080 *:* users:(("litefs",pid=328,fd=9))     
LISTEN  0  0 *:8081 *:* users:(("website",pid=344,fd=29))  

[Zane_Milakovic]

Good Idea -

This is what I get. Only shows 0.0.0.0 for the app itself, proxy shows as *:8080. Does it care about * vs 0.0.0.0?

[Zane_Milakovic]

Also, fly ssh console failed the first few times, which was a first. Wonder if its a byproduct with machine suspend.

[mayailurus]

@Zane_Milakovic

Only shows 0.0.0.0 for the app itself, proxy shows as *:8080. Does it care about * vs 0.0.0.0?

The * should be fine for the LiteFS proxy, and the app itself would actually be ok even on localhost (since it’s the LiteFS proxy and not the Fly edge proxy that talks to that one).

From the context, you’re not actually having any trouble getting HTTP requests through from the outside—or anything like that?

(I.e., this warning message itself is the only anomaly that you’re observing?)

[Zane_Milakovic]

Yeah, requests are making it through. I assume that means the proxy is working as intended.

I am thinking this is more of a miss representation in the CLI and maybe a side effect of suspend/lifefs.