Skip to content

Commit

Permalink
docs: update verbiage on reverse port explanation
Browse files Browse the repository at this point in the history
Co-authored-by: rosstimothy <[email protected]>
  • Loading branch information
2 people authored and github-actions committed Jul 11, 2024
1 parent 9fb36dc commit ab84c23
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/pages/reference/networking.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,7 @@ In those cases, they can set up separate listeners in the config file.
| - | - | - |
| 3021 | Proxy Service | Port used by Teleport Proxy Service instances to dial agents in Proxy Peering mode. |
| 3023 | All clients | SSH port clients connect to. The Proxy Service will forward this connection to port `3022` on the destination service or use a reverse tunnel connection. |
| 3024 | Auth Service | SSH port used to create reverse SSH tunnels from behind-firewall environments into a trusted Proxy Service instance. Teleport services (SSH, DB, App,...) connecting through the Proxy will use this port to form their reverse tunnel connection.|
| 3024 | Auth Service | SSH port used to create reverse SSH tunnels from behind-firewall environments into a trusted Proxy Service instance. All Teleport services (SSH, DB, App,...) connecting through the Proxy will use this port to form their reverse tunnel connection.|
| 3080 or 443 | Proxy Service | HTTPS connection to authenticate `tsh` users into the cluster. The same connection is used to serve a Web UI. |
| 3036 | Database Service | Traffic to MySQL databases.|
| 5432 | Database Service | Traffic to Postgres databases.|
Expand Down

0 comments on commit ab84c23

Please sign in to comment.