self-hosted/teleport
self-hosted/teleport
1
0
Fork 0
mirror of https://github.com/gravitational/teleport synced 2024-10-21 09:44:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

[docs] Add tunnel_public_addr (#3548)

Browse source 
We didn't mention `tunnel_public_addr` in the docs for some reason, but it's critical knowledge for anyone setting up behind a load balancer.
This commit is contained in:
Gus Luxton 2020-04-08 16:59:03 -03:00 committed by GitHub
parent 3b0db4c944
commit 48cc090e8d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/4.2/admin-guide.md
View file

@ -471,7 +471,9 @@ proxy_service:
# command line (CLI) users via password+HOTP
web_listen_addr: 0.0.0.0:3080
# The DNS name the proxy HTTPS endpoint as accessible by cluster users.
# The DNS name of the proxy HTTPS endpoint as accessible by cluster users,
# cluster clients, trusted clusters and nodes joining the cluster via
# Teleport IoT/node tunneling.
# Defaults to the proxy's hostname if not specified. If running multiple
# proxies behind a load balancer, this name must point to the load balancer
# (see public_addr section below)
@ -482,6 +484,13 @@ proxy_service:
# behind a load balancer, this name must point to the load balancer.
# Use a TCP load balancer because this port uses SSH protocol.
ssh_public_addr: proxy.example.com:3023
# The DNS name of the tunnel SSH endpoint as accessible by trusted clusters and
# nodes joining the cluster via Teleport IoT/node tunneling.
# Defaults to the proxy's hostname if not specified. If running multiple proxies
# behind a load balancer, this name must point to the load balancer.
# Use a TCP load balancer because this port uses SSH protocol.
tunnel_public_addr: proxy.example.com:3024
# TLS certificate for the HTTPS connection. Configuring these properly is
# critical for Teleport security.