Переглянути джерело

Update configuring-playbook-own-webserver.md

Adding a bit on how to bind the synapse ports if the webserver isn't in the same docker network, or on a different machine.
pull/1904/head
ThellraAK 4 роки тому
committed by GitHub
джерело
коміт
523a7b4a6e
Не вдалося знайти GPG ключ що відповідає даному підпису Ідентифікатор GPG ключа: 4AEE18F83AFDEB23
1 змінених файлів з 8 додано та 0 видалено
  1. +8
    -0
      docs/configuring-playbook-own-webserver.md

+ 8
- 0
docs/configuring-playbook-own-webserver.md Переглянути файл

@@ -57,6 +57,14 @@ matrix_nginx_proxy_ssl_protocols: "TLSv1.2"

If you are experiencing issues, try updating to a newer version of Nginx. As a data point in May 2021 a user reported that Nginx 1.14.2 was not working for them. They were getting errors about socket leaks. Updating to Nginx 1.19 fixed their issue.

If you are not going to be running your webserver on the same docker network, or the same machine as matrix, these variables can be set to bind synapse to an exposed port. [Keep in mind that there are some security concerns if you simply proxy everything to it](https://github.com/matrix-org/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints)
'''yaml
# Takes an "<ip>:<port>" or "<port>" value (e.g. "127.0.0.1:8048" or "192.168.1.3:80"), or empty string to not expose.
matrix_synapse_container_client_api_host_bind_port: ''
matrix_synapse_container_federation_api_plain_host_bind_port: ''
'''



### Using your own external Apache webserver



Завантаження…
Відмінити
Зберегти