From d4f81508a1751475d8dc65700c880eb918526034 Mon Sep 17 00:00:00 2001 From: Miguel Jimenez Date: Thu, 12 Nov 2026 16:33:54 -0500 Subject: [PATCH 1/8] Document WireGuard tokens and limiting them to networks --- flyctl/integrating.mdx | 2 ++ networking/custom-private-networks.mdx | 2 ++ security/tokens.mdx | 26 +++++++++++++++++++++++++- 3 files changed, 29 insertions(+), 1 deletion(-) diff --git a/flyctl/integrating.mdx b/flyctl/integrating.mdx index f1aeae2a11..95a6b33c9f 100644 --- a/flyctl/integrating.mdx +++ b/flyctl/integrating.mdx @@ -64,6 +64,8 @@ fly tokens create readonly -o my-org -x 720h Scoped to the entire org (like `fly tokens create org`) but can't create, deploy, or modify anything. Good for monitoring scripts, status dashboards, or any workflow that only consumes data from the Fly API. +**WireGuard token** For managing an organization's WireGuard peers. You can limit it to specific private networks with `--network`. See [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). + ### Token management List active tokens: diff --git a/networking/custom-private-networks.mdx b/networking/custom-private-networks.mdx index 767b0dc13c..6d814e6804 100644 --- a/networking/custom-private-networks.mdx +++ b/networking/custom-private-networks.mdx @@ -89,6 +89,8 @@ As an administrator with a multi-tenant setup, you might need to troubleshoot cu - `fly ssh sftp` commands to work with files on an app Machine. See the [`fly ssh sftp` docs](/flyctl/cmd/fly_ssh_sftp). - `fly proxy [remote_host] --app ` to create a WireGuard tunnel to an app Machine. See the [`fly proxy` docs](/flyctl/cmd/fly_proxy). +You can limit a WireGuard token to one or more custom 6PNs. The token can then create and remove WireGuard peers only on those networks. See [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). + ## Check which network an app or Machine is on You can retrieve the network name for all apps in your organization and you can also verify that apps or Machines are on different networks by examining their private IPv6 addresses. diff --git a/security/tokens.mdx b/security/tokens.mdx index 1aa8a10a19..77530e1134 100644 --- a/security/tokens.mdx +++ b/security/tokens.mdx @@ -22,7 +22,7 @@ You can create a standard app-scoped deploy token, a token to SSH into an app's Use an org-scoped token for access to manage all the apps within a single organization. An org-scoped token is the middle ground between the auth token and the more restricted app-scoped token, and is useful when you want to automate a single org. -You can create a standard org-scoped token or a read-only org-scoped token. +You can create a standard org-scoped token, a read-only org-scoped token, or a token to manage an org's WireGuard peers. ## Create and manage tokens @@ -116,6 +116,30 @@ Create a read-only token based on an existing token: fly tokens create readonly --name <"my token name"> --expiry --from-existing -t ``` +#### Create an org-scoped WireGuard token + +A WireGuard token can manage WireGuard peers for a single org. By default, the token works on every private network in the org. + +Create a WireGuard token: + +``` +fly tokens create wireguard -o +``` + +To limit the token to specific networks, use the `--network` option with the [network name](/networking/custom-private-networks#network-names-and-ids): + +- The token can create and remove WireGuard peers only on the networks you name. A request on any other network is refused. +- To allow several networks, repeat the option or separate the names with commas: `--network staging --network prod` or `--network staging,prod`. +- `default` names the org's default network. +- The limit covers WireGuard peers only. It doesn't limit apps, Machines, or IP addresses to a network. +- The token can still read the org's data. + +This example creates a WireGuard token for the `my-org` org that's limited to the `staging` network: + +``` +fly tokens create wireguard -o my-org --network staging +``` + ### List or view tokens List all the tokens for current app, or use the `--app` option to specify an app: From 49a05584e2f1014fee23d5d3cee717c4aec3e519 Mon Sep 17 00:00:00 2001 From: Miguel Jimenez Date: Thu, 12 Nov 2026 22:13:20 -0500 Subject: [PATCH 2/8] Correct what a WireGuard token can access --- networking/custom-private-networks.mdx | 8 +++++++- security/tokens.mdx | 9 ++++++--- 2 files changed, 13 insertions(+), 4 deletions(-) diff --git a/networking/custom-private-networks.mdx b/networking/custom-private-networks.mdx index 6d814e6804..2b6358796a 100644 --- a/networking/custom-private-networks.mdx +++ b/networking/custom-private-networks.mdx @@ -89,7 +89,13 @@ As an administrator with a multi-tenant setup, you might need to troubleshoot cu - `fly ssh sftp` commands to work with files on an app Machine. See the [`fly ssh sftp` docs](/flyctl/cmd/fly_ssh_sftp). - `fly proxy [remote_host] --app ` to create a WireGuard tunnel to an app Machine. See the [`fly proxy` docs](/flyctl/cmd/fly_proxy). -You can limit a WireGuard token to one or more custom 6PNs. The token can then create and remove WireGuard peers only on those networks. See [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). +## Limit a WireGuard token to custom 6PNs + +A WireGuard token manages WireGuard peers for an organization and nothing else. You can limit the token to one or more custom 6PNs. The token can then create and remove WireGuard peers only on those networks. + +A WireGuard token can't run commands that name an app, like `fly ssh console --app` or `fly proxy --app`. + +See [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). ## Check which network an app or Machine is on diff --git a/security/tokens.mdx b/security/tokens.mdx index 77530e1134..d544092f24 100644 --- a/security/tokens.mdx +++ b/security/tokens.mdx @@ -118,7 +118,11 @@ fly tokens create readonly --name <"my token name"> --expiry --from-e #### Create an org-scoped WireGuard token -A WireGuard token can manage WireGuard peers for a single org. By default, the token works on every private network in the org. +A WireGuard token manages WireGuard peers for a single org and nothing else: + +- The token can create and remove WireGuard peers. By default, it works on every private network in the org. +- The token can do org-level reads. +- The token can't act on apps or Machines, reads included. Any command that names an app is refused, for example `fly ssh console --app`, `fly proxy --app`, `fly status -a`, or `fly machines list -a`. Create a WireGuard token: @@ -131,8 +135,7 @@ To limit the token to specific networks, use the `--network` option with the [ne - The token can create and remove WireGuard peers only on the networks you name. A request on any other network is refused. - To allow several networks, repeat the option or separate the names with commas: `--network staging --network prod` or `--network staging,prod`. - `default` names the org's default network. -- The limit covers WireGuard peers only. It doesn't limit apps, Machines, or IP addresses to a network. -- The token can still read the org's data. +- The option doesn't limit reads. Org-level reads still work. This example creates a WireGuard token for the `my-org` org that's limited to the `staging` network: From 2b74b2f71eec924d21ead81414b2ef46df97dfe6 Mon Sep 17 00:00:00 2001 From: Miguel Jimenez Date: Thu, 12 Nov 2026 22:13:31 -0500 Subject: [PATCH 3/8] Add expiry, the reference link and network name notes for WireGuard tokens --- flyctl/integrating.mdx | 8 +++++++- security/tokens.mdx | 17 +++++++++++------ 2 files changed, 18 insertions(+), 7 deletions(-) diff --git a/flyctl/integrating.mdx b/flyctl/integrating.mdx index 95a6b33c9f..6477581ff2 100644 --- a/flyctl/integrating.mdx +++ b/flyctl/integrating.mdx @@ -64,7 +64,13 @@ fly tokens create readonly -o my-org -x 720h Scoped to the entire org (like `fly tokens create org`) but can't create, deploy, or modify anything. Good for monitoring scripts, status dashboards, or any workflow that only consumes data from the Fly API. -**WireGuard token** For managing an organization's WireGuard peers. You can limit it to specific private networks with `--network`. See [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). +**WireGuard token** For managing an organization's WireGuard peers: + +```bash +fly tokens create wireguard -o my-org --network staging -x 720h +``` + +The token can only create and remove WireGuard peers, and `--network` limits it to the networks you name. It can't run commands that name an app. See [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). ### Token management diff --git a/security/tokens.mdx b/security/tokens.mdx index d544092f24..b58329cdda 100644 --- a/security/tokens.mdx +++ b/security/tokens.mdx @@ -1,6 +1,6 @@ --- title: Access tokens -description: "Create Fly.io access tokens scoped to one app or org, including SSH, machine-exec and read-only tokens, then set expiry, list and revoke them with fly tokens." +description: "Create Fly.io access tokens scoped to one app or org, including SSH, machine-exec, read-only and WireGuard tokens, then set expiry, list and revoke them." source_url: https://fly.io/docs/security/tokens/ --- @@ -124,25 +124,30 @@ A WireGuard token manages WireGuard peers for a single org and nothing else: - The token can do org-level reads. - The token can't act on apps or Machines, reads included. Any command that names an app is refused, for example `fly ssh console --app`, `fly proxy --app`, `fly status -a`, or `fly machines list -a`. -Create a WireGuard token: +If you don't specify a name with the `--name` option, then the default name is `WireGuard token`. + +Create a WireGuard token with a custom name and expiry: ``` -fly tokens create wireguard -o +fly tokens create wireguard -o --name <"my token name"> --expiry ``` To limit the token to specific networks, use the `--network` option with the [network name](/networking/custom-private-networks#network-names-and-ids): - The token can create and remove WireGuard peers only on the networks you name. A request on any other network is refused. - To allow several networks, repeat the option or separate the names with commas: `--network staging --network prod` or `--network staging,prod`. -- `default` names the org's default network. +- `default` always means the org's default network. You can't use `--network` to name a custom network that's called `default`. +- Network names aren't checked when you create the token. If you mistype the name, you get a token that works on no network. - The option doesn't limit reads. Org-level reads still work. -This example creates a WireGuard token for the `my-org` org that's limited to the `staging` network: +This example creates a WireGuard token for the `my-org` org that's limited to the `staging` network and valid for 24 hours: ``` -fly tokens create wireguard -o my-org --network staging +fly tokens create wireguard -o my-org --network staging --expiry 24h ``` +For all options, refer to the [`fly tokens create wireguard` command docs](/flyctl/cmd/fly_tokens_create_wireguard). + ### List or view tokens List all the tokens for current app, or use the `--app` option to specify an app: From e3f9fd80dee117ea88076921777522fb6a856d14 Mon Sep 17 00:00:00 2001 From: Miguel Jimenez Date: Thu, 12 Nov 2026 22:34:26 -0500 Subject: [PATCH 4/8] Keep the WireGuard token text in one place and say why to limit it --- flyctl/integrating.mdx | 2 +- networking/custom-private-networks.mdx | 10 ++-------- security/tokens.mdx | 24 ++++++++++++++++-------- 3 files changed, 19 insertions(+), 17 deletions(-) diff --git a/flyctl/integrating.mdx b/flyctl/integrating.mdx index 6477581ff2..a31d41cfce 100644 --- a/flyctl/integrating.mdx +++ b/flyctl/integrating.mdx @@ -70,7 +70,7 @@ Scoped to the entire org (like `fly tokens create org`) but can't create, deploy fly tokens create wireguard -o my-org --network staging -x 720h ``` -The token can only create and remove WireGuard peers, and `--network` limits it to the networks you name. It can't run commands that name an app. See [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). +The `--network` flag keeps the token to the networks it needs. For what the token can and can't do, see [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). ### Token management diff --git a/networking/custom-private-networks.mdx b/networking/custom-private-networks.mdx index 2b6358796a..9a4c4895bd 100644 --- a/networking/custom-private-networks.mdx +++ b/networking/custom-private-networks.mdx @@ -24,6 +24,8 @@ If you destroy all the apps on a custom 6PN, the network technically still exist It's a best practice to use a formula for naming custom 6PNs, especially if you're going to have a lot of them or if you need to add more than one app to each custom 6PN. For example, `customerID-network` or `appName-someID-network`. Network names can have letters, numbers, and dashes, but must start with a letter. +You can limit a WireGuard token to specific networks by name. See [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). + ## Create a custom private network @@ -89,14 +91,6 @@ As an administrator with a multi-tenant setup, you might need to troubleshoot cu - `fly ssh sftp` commands to work with files on an app Machine. See the [`fly ssh sftp` docs](/flyctl/cmd/fly_ssh_sftp). - `fly proxy [remote_host] --app ` to create a WireGuard tunnel to an app Machine. See the [`fly proxy` docs](/flyctl/cmd/fly_proxy). -## Limit a WireGuard token to custom 6PNs - -A WireGuard token manages WireGuard peers for an organization and nothing else. You can limit the token to one or more custom 6PNs. The token can then create and remove WireGuard peers only on those networks. - -A WireGuard token can't run commands that name an app, like `fly ssh console --app` or `fly proxy --app`. - -See [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). - ## Check which network an app or Machine is on You can retrieve the network name for all apps in your organization and you can also verify that apps or Machines are on different networks by examining their private IPv6 addresses. diff --git a/security/tokens.mdx b/security/tokens.mdx index b58329cdda..eba4ed4862 100644 --- a/security/tokens.mdx +++ b/security/tokens.mdx @@ -22,7 +22,7 @@ You can create a standard app-scoped deploy token, a token to SSH into an app's Use an org-scoped token for access to manage all the apps within a single organization. An org-scoped token is the middle ground between the auth token and the more restricted app-scoped token, and is useful when you want to automate a single org. -You can create a standard org-scoped token, a read-only org-scoped token, or a token to manage an org's WireGuard peers. +You can create a standard org-scoped token or a read-only org-scoped token. You can also create an org-scoped WireGuard token, which manages an org's WireGuard peers and can't act on apps. ## Create and manage tokens @@ -82,7 +82,7 @@ fly tokens create machine-exec --command "" ### Create org-scoped tokens -Org-scoped tokens are limited to managing a single org and its resources, including apps. +Org-scoped tokens are limited to a single org. A standard org-scoped token can manage the org and its resources, including apps. If you don't specify a name with the `--name` option, then the default name is `Org deploy token`. @@ -118,10 +118,10 @@ fly tokens create readonly --name <"my token name"> --expiry --from-e #### Create an org-scoped WireGuard token -A WireGuard token manages WireGuard peers for a single org and nothing else: +A WireGuard token is for managing the WireGuard peers of a single org: - The token can create and remove WireGuard peers. By default, it works on every private network in the org. -- The token can do org-level reads. +- The token can do org-level reads, like listing the org's WireGuard peers. - The token can't act on apps or Machines, reads included. Any command that names an app is refused, for example `fly ssh console --app`, `fly proxy --app`, `fly status -a`, or `fly machines list -a`. If you don't specify a name with the `--name` option, then the default name is `WireGuard token`. @@ -132,13 +132,13 @@ Create a WireGuard token with a custom name and expiry: fly tokens create wireguard -o --name <"my token name"> --expiry ``` -To limit the token to specific networks, use the `--network` option with the [network name](/networking/custom-private-networks#network-names-and-ids): +A WireGuard peer joins a private network and can reach every private service on that network. A token that can create peers on any network gives access to all of them. Use the `--network` option with the [network name](/networking/custom-private-networks#network-names-and-ids) to keep a token to the networks it needs: -- The token can create and remove WireGuard peers only on the networks you name. A request on any other network is refused. +- The token can create and remove WireGuard peers only on the networks you name. A request that names any other network is refused, reads included. +- Reads that name no network, like listing the org's WireGuard peers, aren't affected. - To allow several networks, repeat the option or separate the names with commas: `--network staging --network prod` or `--network staging,prod`. - `default` always means the org's default network. You can't use `--network` to name a custom network that's called `default`. -- Network names aren't checked when you create the token. If you mistype the name, you get a token that works on no network. -- The option doesn't limit reads. Org-level reads still work. +- Network names aren't checked when you create the token. With `--network staging,prdo`, the token works on `staging` but not on `prod`, and you get no error. This example creates a WireGuard token for the `my-org` org that's limited to the `staging` network and valid for 24 hours: @@ -146,6 +146,14 @@ This example creates a WireGuard token for the `my-org` org that's limited to th fly tokens create wireguard -o my-org --network staging --expiry 24h ``` +With a network-limited token, [`fly wireguard create`](/flyctl/cmd/fly_wireguard_create) must name an allowed network: + +``` +fly wireguard create my-org ord my-peer --network staging +``` + +Without `--network`, `fly wireguard create` targets the default network. The request is refused unless the token allows `default`. + For all options, refer to the [`fly tokens create wireguard` command docs](/flyctl/cmd/fly_tokens_create_wireguard). ### List or view tokens From 628ffc78038650a4ab30a58f7f2fd744b4282c9d Mon Sep 17 00:00:00 2001 From: Miguel Jimenez Date: Thu, 12 Nov 2026 22:58:54 -0500 Subject: [PATCH 5/8] Say how to create a peer on the default network with a WireGuard token --- security/tokens.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/security/tokens.mdx b/security/tokens.mdx index eba4ed4862..39b4979aba 100644 --- a/security/tokens.mdx +++ b/security/tokens.mdx @@ -137,7 +137,7 @@ A WireGuard peer joins a private network and can reach every private service on - The token can create and remove WireGuard peers only on the networks you name. A request that names any other network is refused, reads included. - Reads that name no network, like listing the org's WireGuard peers, aren't affected. - To allow several networks, repeat the option or separate the names with commas: `--network staging --network prod` or `--network staging,prod`. -- `default` always means the org's default network. You can't use `--network` to name a custom network that's called `default`. +- `default` means the org's default network. You can't use `--network` to name a custom network that's called `default`. - Network names aren't checked when you create the token. With `--network staging,prdo`, the token works on `staging` but not on `prod`, and you get no error. This example creates a WireGuard token for the `my-org` org that's limited to the `staging` network and valid for 24 hours: @@ -152,7 +152,7 @@ With a network-limited token, [`fly wireguard create`](/flyctl/cmd/fly_wireguard fly wireguard create my-org ord my-peer --network staging ``` -Without `--network`, `fly wireguard create` targets the default network. The request is refused unless the token allows `default`. +To create a peer on the default network, leave out `--network`. The request is refused unless the token allows `default`. On `fly wireguard create`, `--network default` names a custom network called `default`, not the default network. For all options, refer to the [`fly tokens create wireguard` command docs](/flyctl/cmd/fly_tokens_create_wireguard). From 5b529be16257ea9c216502af9d378bc11467d182 Mon Sep 17 00:00:00 2001 From: Miguel Jimenez Date: Thu, 12 Nov 2026 23:56:01 -0500 Subject: [PATCH 6/8] Say the default network where a WireGuard token allows it --- security/tokens.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/security/tokens.mdx b/security/tokens.mdx index 39b4979aba..6a7cd753ad 100644 --- a/security/tokens.mdx +++ b/security/tokens.mdx @@ -120,7 +120,7 @@ fly tokens create readonly --name <"my token name"> --expiry --from-e A WireGuard token is for managing the WireGuard peers of a single org: -- The token can create and remove WireGuard peers. By default, it works on every private network in the org. +- The token can create and remove WireGuard peers. Without `--network`, it works on every private network in the org. - The token can do org-level reads, like listing the org's WireGuard peers. - The token can't act on apps or Machines, reads included. Any command that names an app is refused, for example `fly ssh console --app`, `fly proxy --app`, `fly status -a`, or `fly machines list -a`. @@ -137,7 +137,7 @@ A WireGuard peer joins a private network and can reach every private service on - The token can create and remove WireGuard peers only on the networks you name. A request that names any other network is refused, reads included. - Reads that name no network, like listing the org's WireGuard peers, aren't affected. - To allow several networks, repeat the option or separate the names with commas: `--network staging --network prod` or `--network staging,prod`. -- `default` means the org's default network. You can't use `--network` to name a custom network that's called `default`. +- To allow the org's default network, use `--network default`. You can't use `--network` to name a custom network that's called `default`. - Network names aren't checked when you create the token. With `--network staging,prdo`, the token works on `staging` but not on `prod`, and you get no error. This example creates a WireGuard token for the `my-org` org that's limited to the `staging` network and valid for 24 hours: @@ -152,7 +152,7 @@ With a network-limited token, [`fly wireguard create`](/flyctl/cmd/fly_wireguard fly wireguard create my-org ord my-peer --network staging ``` -To create a peer on the default network, leave out `--network`. The request is refused unless the token allows `default`. On `fly wireguard create`, `--network default` names a custom network called `default`, not the default network. +To create a peer on the default network, leave out `--network`. The request is refused unless the token allows the default network. On `fly wireguard create`, `--network default` names a custom network called `default`, not the default network. For all options, refer to the [`fly tokens create wireguard` command docs](/flyctl/cmd/fly_tokens_create_wireguard). From 476996726d182eaf63ac9d5f8bd116ebcbc32f87 Mon Sep 17 00:00:00 2001 From: Miguel Jimenez Date: Fri, 13 Nov 2026 12:36:06 -0500 Subject: [PATCH 7/8] Say limit, and list what --network default means on each command --- flyctl/integrating.mdx | 2 +- security/tokens.mdx | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/flyctl/integrating.mdx b/flyctl/integrating.mdx index a31d41cfce..cea068e806 100644 --- a/flyctl/integrating.mdx +++ b/flyctl/integrating.mdx @@ -70,7 +70,7 @@ Scoped to the entire org (like `fly tokens create org`) but can't create, deploy fly tokens create wireguard -o my-org --network staging -x 720h ``` -The `--network` flag keeps the token to the networks it needs. For what the token can and can't do, see [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). +The `--network` flag limits the token to the networks it needs. For what the token can and can't do, see [Create an org-scoped WireGuard token](/security/tokens#create-an-org-scoped-wireguard-token). ### Token management diff --git a/security/tokens.mdx b/security/tokens.mdx index 6a7cd753ad..4e0a71d02f 100644 --- a/security/tokens.mdx +++ b/security/tokens.mdx @@ -132,7 +132,7 @@ Create a WireGuard token with a custom name and expiry: fly tokens create wireguard -o --name <"my token name"> --expiry ``` -A WireGuard peer joins a private network and can reach every private service on that network. A token that can create peers on any network gives access to all of them. Use the `--network` option with the [network name](/networking/custom-private-networks#network-names-and-ids) to keep a token to the networks it needs: +A WireGuard peer joins a private network and can reach every private service on that network. A token that can create peers on any network gives access to all of them. Use the `--network` option with the [network name](/networking/custom-private-networks#network-names-and-ids) to limit a token to the networks it needs: - The token can create and remove WireGuard peers only on the networks you name. A request that names any other network is refused, reads included. - Reads that name no network, like listing the org's WireGuard peers, aren't affected. @@ -152,7 +152,9 @@ With a network-limited token, [`fly wireguard create`](/flyctl/cmd/fly_wireguard fly wireguard create my-org ord my-peer --network staging ``` -To create a peer on the default network, leave out `--network`. The request is refused unless the token allows the default network. On `fly wireguard create`, `--network default` names a custom network called `default`, not the default network. +- Token allows the default network: `fly tokens create wireguard --network default` +- Peer on the default network: `fly wireguard create ` (no `--network`) +- `fly wireguard create --network default` means a custom network named `default`. For all options, refer to the [`fly tokens create wireguard` command docs](/flyctl/cmd/fly_tokens_create_wireguard). From 6cda41998f3e2b76b7a6d65d75c25ba486d20999 Mon Sep 17 00:00:00 2001 From: Miguel Jimenez Date: Fri, 13 Nov 2026 12:59:27 -0500 Subject: [PATCH 8/8] Say a default-network peer is refused unless the token allows it --- security/tokens.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/security/tokens.mdx b/security/tokens.mdx index 4e0a71d02f..3186488c9e 100644 --- a/security/tokens.mdx +++ b/security/tokens.mdx @@ -152,8 +152,10 @@ With a network-limited token, [`fly wireguard create`](/flyctl/cmd/fly_wireguard fly wireguard create my-org ord my-peer --network staging ``` +For the default network, `--network` works differently on the two commands: + - Token allows the default network: `fly tokens create wireguard --network default` -- Peer on the default network: `fly wireguard create ` (no `--network`) +- Peer on the default network: `fly wireguard create ` (no `--network`). This is refused unless the token allows the default network. - `fly wireguard create --network default` means a custom network named `default`. For all options, refer to the [`fly tokens create wireguard` command docs](/flyctl/cmd/fly_tokens_create_wireguard).