Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Matrix
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Container Registry
Model registry
Operate
Environments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TeDomum
Matrix
Commits
49b58f0a
Unverified
Commit
49b58f0a
authored
6 years ago
by
Richard van der Hoff
Committed by
GitHub
6 years ago
Browse files
Options
Downloads
Patches
Plain Diff
clarify TLS instructions
parent
1c0eb8bb
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
INSTALL.md
+19
-20
19 additions, 20 deletions
INSTALL.md
with
19 additions
and
20 deletions
INSTALL.md
+
19
−
20
View file @
49b58f0a
...
...
@@ -358,26 +358,25 @@ For information on using a reverse proxy, see
[
docs/reverse_proxy.rst
](
docs/reverse_proxy.rst
)
.
To configure Synapse to expose an HTTPS port, you will need to edit
`homeserver.yaml`
.
First, under the
`listeners`
section, uncomment the configuration for the
TLS-enabled listener. (Remove the hash sign (
`#`
) and space at the start of
each line). The relevant lines are like this:
```
- port: 8448
type: http
tls: true
resources:
- names: [client, federation]
```
You will also need to uncomment the
`tls_certificate_path`
and
`tls_private_key_path`
lines under the
`TLS`
section. You can either point
these settings at an existing certificate and key, or you can enable Synapse's
built-in ACME (Let's Encrypt) support. Instructions for having Synapse
automatically provision and renew federation certificates through ACME can be
found at
[
ACME.md
](
docs/ACME.md
)
.
`homeserver.yaml`
, as follows:
*
First, under the
`listeners`
section, uncomment the configuration for the
TLS-enabled listener. (Remove the hash sign (
`#`
) at the start of
each line). The relevant lines are like this:
```
- port: 8448
type: http
tls: true
resources:
- names: [client, federation]
```
*
You will also need to uncomment the
`tls_certificate_path`
and
`tls_private_key_path`
lines under the
`TLS`
section. You can either
point these settings at an existing certificate and key, or you can
enable Synapse's built-in ACME (Let's Encrypt) support. Instructions
for having Synapse automatically provision and renew federation
certificates through ACME can be found at
[
ACME.md
](
docs/ACME.md
)
.
## Registering a user
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment