We’ve changed how our fly-replay feature interacts with private networks. Previously, fly-replay could route requests between any two apps in your organization, even if they were in different private networks. As of now, replays are scoped to the same private network by default.
This is paired with a new organization-wide setting for whether to allow cross-network replays. Important to note: For orgs that have used fly-replay across network boundaries recently, this setting has been enabled for you, and you will also have received an email describing the change. For everyone else, this setting is disabled and replays between different private networks will be blocked.
We’re changing this to be more restrictive, mainly to be less surprising. This new behavior is how many people expect it to work when they first encounter it, and indeed it matches the network boundary behavior of flycast. Now you can apply the same mental model to both flycast and fly-replay.
If you want to change this behavior, you can find it in your org settings in the dashboard under Routing → Cross-Network Replay. Or, from the next flyctl release, you can run fly orgs cross-network-replays <enable|disable> to configure this from the CLI.