Skip to content

Commit da734d4

Browse files
authored
clarify UI behavior (#18924)
1 parent d1040a7 commit da734d4

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/content/partials/cloudflare-one/access/add-target.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,12 +20,12 @@ To create a new target:
2020
- Contain only alphanumeric characters, `-`, or `.` (no spaces allowed)
2121
- Start and end with an alphanumeric character
2222
</Details>
23-
4. In **IP addresses**, enter the IPv4 and/or IPv6 address of the target resource. If the IP address overlaps across multiple private networks, select the [virtual network](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/) where the resource is located. This IP address and virtual network pairing is now assigned to this target and cannot be reused in another target by design.
24-
:::note[IP address requirements]
25-
- The IP address must route through Cloudflare Tunnel. To verify, confirm that the target IP appears in **Networks** > **Routes**.
26-
- You must input the full IP address. The selector in the UI does not do partial matches.
23+
4. In **IP addresses**, enter the IPv4 and/or IPv6 address of the target resource. The dropdown menu will not populate until you type in the full IP address.
24+
:::note
25+
If the target IP does not appear in the dropdown, go to **Networks** > **Routes** and confirm that the IP routes through Cloudflare Tunnel.
2726
:::
28-
5. Select **Add target**.
27+
5. In the dropdown menu, select the IP address and [virtual network](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/) where the resource is located. This IP address and virtual network pairing is now assigned to this target and cannot be reused in another target by design.
28+
6. Select **Add target**.
2929
</TabItem>
3030
<TabItem label="API">
3131

0 commit comments

Comments
 (0)