From 82d4f5eb7d0667eff7d624f46cffe4fa5f8b5e60 Mon Sep 17 00:00:00 2001 From: Steven Martin Date: Wed, 2 Oct 2024 19:17:24 -0400 Subject: [PATCH] docs: update proxy service ports networking example --- docs/pages/reference/networking.mdx | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/docs/pages/reference/networking.mdx b/docs/pages/reference/networking.mdx index 150c240287d61..2fd07c2a9f241 100644 --- a/docs/pages/reference/networking.mdx +++ b/docs/pages/reference/networking.mdx @@ -181,11 +181,11 @@ In those cases, they can set up separate listeners in the config file. Cloud-hosted Teleport deployments allocate a different set of ports to each tenant's Proxy Service. To see which ports are available for your Teleport -tenant, run a command similar to the following, replacing `mytenant.teleport.sh` +tenant, run a command similar to the following, replacing `example.teleport.sh` with your tenant domain: ```code -$ curl https://mytenant.teleport.sh/webapi/ping | jq '.proxy' +$ curl https://example.teleport.sh/webapi/ping | jq '.proxy' ``` The output should resemble the following, including the unique ports assigned to @@ -195,20 +195,18 @@ your tenant: { "kube": { "enabled": true, - "public_addr": "mytenant.teleport.sh:11107", - "listen_addr": "0.0.0.0:3026" + "listen_addr": "0.0.0.0:3080" }, "ssh": { - "listen_addr": "[::]:3023", - "tunnel_listen_addr": "0.0.0.0:3024", - "public_addr": "mytenant.teleport.sh:443", - "ssh_public_addr": "mytenant.teleport.sh:11105", - "ssh_tunnel_public_addr": "mytenant.teleport.sh:11106" + "listen_addr": "0.0.0.0:3080", + "tunnel_listen_addr": "0.0.0.0:3080", + "web_listen_addr": "0.0.0.0:3080", + "public_addr": "example.teleport.sh:443", + "dial_timeout": 30000000000 }, "db": { - "postgres_public_addr": "mytenant.teleport.sh:11109", - "mysql_listen_addr": "0.0.0.0:3036", - "mysql_public_addr": "mytenant.teleport.sh:11108" + "postgres_listen_addr": "0.0.0.0:3080", + "mysql_listen_addr": "0.0.0.0:3080" }, "tls_routing_enabled": true }