Proxy connection issues

3

This one is for the Fly engs to answer.

I have a suggestion if you want to narrow this problem as being down to Fly’s proxy:

There must be a FLY_PUBLIC_IP env var set for each VM. You can connect to this IP over allowed_public_ports bypassing Fly’s proxies. To do so:

  1. Add an experimental.allowed_public_ports=[<app-internal-port] to your fly.toml: Any way to attach a public IPv4 address to a specific machine? - #4 by ignoramous
  2. Exec ab against that IP:port.
ab -n 10 -c 10 -H "Host: <FILL-IF-REQUIRED>" "http://$FLY_PUBLIC_IP:$INTERNAL_PORT"

To hasten up, consider writing to their support if you are okay subscribing to their Launch plans (£29/mo) or Scale plans (£200/mo): Announcing: Plans for email support and compliance requirements (usage included).