Send request to a specific VM

[greg]

Hi,

Ah. Yes, from an external network you could not use the .internal domains directly. So that option is out.

Back to the header approach then. That should work. I’ve also seen that approach mentioned e.g

Is it possibly for a client to connect to a particular instance

@hi.kanily We’ve now added a functionality where if you add fly-force-instance-id header to your request, with a value containing an instance id, we will forward the request to that instance only. This should also work with websockets and upgrades if the original request was made with the aforementioned header. This is a bit of a footgun: we will not try other instances when you provide that header. If the instance is down, the connection will probably hang for a little bit and then close.

Yet you say it’s ignored (as the same VM ID is given each request regardless). Hmm. Not sure I’m afraid. It sounds like someone at Fly will need to debug that for you.