Fly proxy logs error "timed out while connecting to instance"

Questions / Help
1

Hi,

I have a haproxy instance deployed. The container starts perfectly fine but after a short while the logs show this error:

2023-01-11T14:53:08Z proxy[d9b5872f] fra [error]timed out while connecting to instance

When I ssh into the app I can make requests to haproxy just fine.

$ fly ssh console -s
? Select instance: fra.XXX.internal
Connecting to fdaa:xxxx... complete
/ # wget 127.0.0.1
Connecting to 127.0.0.1 (127.0.0.1:80)
wget: server returned error: HTTP/1.1 403 Forbidden

403 Forbidden is an expected return value in my case :slight_smile:

The application ran perfectly for a few weeks. I redeployed the application by restart and also deleted it completely and set it up again. No luck.

There is no other error message in the logs. HAProxy starts and after 15 seconds I get the error.

2023-01-11T14:50:49Z app[d9b5872f] fra [info]Server formel1_backend/server1 is UP, reason: Layer4 check passed, check duration: 53ms. 1 active and 0 backup servers online. 0 sessions requeued, 0 total in queue.
2023-01-11T14:53:04Z proxy[d9b5872f] fra [error]timed out while connecting to instance

The application is not reachable from the outside.

What can I do?

2

I had the same issue from 2023-02-10T21:05 UTC until 2023-02-10T21:05 UTC, which is when I restarted my VM. Time will tell if it starts again.

I noticed there was a fix on a proxying issue today, but the problem appeared after that for me. :confused:

Only one app is affected, and it’s the only one I have that uses Fly-Replay, if that helps.