Request timeout at 30s, can I increase it?

[lotonadisha]

Hello,

I am using Fly for some requests that can sometimes take longer than 30s (but not more than like 60 or so).

My requests seem to always time out at 30s, is there a setting or option in fly.toml I can set to increase this? I wasn’t able to find it myself.

Thanks for your help

[andie]

Hi @lotonadisha

The timeout should only occur after the connection is idle for 60s. If your requests are timing out at 30s, could you share some more information about your app, and the application logs showing the connection errors?

Here are some other answers with info that might be helpful:

could not send HTTP request to instance: connection error: timed out

When the Fly proxy sends requests to your app, it will wait 60 seconds for a response. After that, you’ll see this error. Your app could be timing out for a number of reasons, such as slow database requests, or timeouts to other services that your app connects to. If your application isn’t logging anything about these timeouts, check to make sure the clients for your target services (Postgres, etc) are configure to log when connection errors occur.

How do I know how many connections are open?

We don’t have a limit on response times exactly. If a connection doesn’t send or receive any bytes during a 60s window, we’ll close the connection. If it continuously sends or receives some data, we will not close the connection and the response will continue. I’ve been looking at the metrics for the specific app you mentioned and it appears that the app itself is responding slowly. Do you have metrics or logs that would give you latency numbers? We expose metrics to our users, some of them l…