mirror of
https://github.com/gravitational/teleport.git
synced 2026-11-04 19:05:37 +08:00
Paul Gottschling
c423c08fd3
* Refresh the Enterprise Getting Started guide Fixes #14249 Edit the Enterprise Getting Started guide based on manual testing to make the guide up to date and easier to follow. - Update the architectural description in the introduction - Structure the guide, following out Linux Server guide for open source installations, to include Application Access - Add DNS instructions rather than using the `--insecure` flag - Add copy-pastable installation instructions - Flesh out the license file instructions and add a screenshot of the customer portal - Simplify the instructions for adding a local user - Remove the docker-compose instructions, since we want the user to finish setting up a minimal Teleport cluster by the end of the guide, and these instructions begin a new step-by-step sequence. We also have a separate docker-compose guide that users can follow for a local demo - Add a "Next steps" section and move relevant content there * Respond to PR feedback
34 lines
1.1 KiB
Plaintext
34 lines
1.1 KiB
Plaintext
Let's Encrypt verifies that you control the domain name of your Teleport cluster
|
|
by communicating with the HTTPS server listening on port 443 of your Teleport
|
|
Proxy Service.
|
|
|
|
You can configure the Teleport Proxy Service to complete the Let's Encrypt
|
|
verification process when it starts up.
|
|
|
|
On the host where you will start the Teleport Auth Service and Proxy Service,
|
|
run the following commands, where `tele.example.com` is the domain name of your
|
|
Teleport cluster and `user@example.com` is an email address used for
|
|
notifications (you can use any domain):
|
|
|
|
```code
|
|
$ DOMAIN=tele.example.com
|
|
$ EMAIL=user@example.com
|
|
$ teleport configure --acme --acme-email=${EMAIL?} --cluster-name=${DOMAIN?} | \
|
|
sudo tee /etc/teleport.yaml > /dev/null
|
|
```
|
|
|
|
The `--acme`, `--acme-email`, and `--cluster-name` flags will add the following
|
|
settings to your Teleport configuration file:
|
|
|
|
```yaml
|
|
proxy_service:
|
|
enabled: "yes"
|
|
web_listen_addr: :443
|
|
public_addr: tele.example.com:443
|
|
acme:
|
|
enabled: "yes"
|
|
email: user@example.com
|
|
```
|
|
|
|
Port 443 on your Teleport Proxy Service host must allow traffic from all sources.
|