2024-10-17 13:17:56 +00:00
|
|
|
# This is a sample file demonstrating how to set up reverse-proxy for element.example.com.
|
Add "Web" to Element and SchildiChat web application (#3755)
* Replace "Element" with "Element Web"
- If Element indicates the web application, then it is changed to Element Web.
- If it indicates clients branded with Element such as Element desktop, web, mobile clients, then it is changed to Element clients.
- If it is combined with location sharing functionality, it is not changed.
with other some changes, including:
- Change "app.element.io" anchor link to "https://github.com/element-hq/element-web" on README.md, following other documentation files
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Replace "SchildiChat" with "SchildiChat Web"
- If SchildiChat indicates the web application, then it is changed to SchildiChat Web.
- If it indicates clients branded with SchildiChat such as SchildiChat desktop, web, mobile clients, then it is changed to SchildiChat clients.
- If it is combined with location sharing functionality, it is not changed.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Rename configuring-playbook-client-schildichat.md to configuring-playbook-client-schildichat-web.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Rename configuring-playbook-client-element.md to configuring-playbook-client-element-web.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
---------
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Co-authored-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
2024-11-07 14:31:26 +00:00
|
|
|
# If you're not using Element Web (`matrix_client_element_enabled: false`), you won't need this.
|
2019-02-01 14:51:18 +00:00
|
|
|
|
|
|
|
<VirtualHost *:80>
|
2024-10-17 13:17:56 +00:00
|
|
|
ServerName element.example.com
|
2019-02-01 14:51:18 +00:00
|
|
|
|
2024-01-14 15:23:28 +00:00
|
|
|
# You may wish to handle the /.well-known/acme-challenge paths here somehow,
|
|
|
|
# if you're using ACME (Let's Encrypt) certificates.
|
2019-02-01 14:51:18 +00:00
|
|
|
|
2024-10-17 13:17:56 +00:00
|
|
|
Redirect permanent / https://element.example.com/
|
2019-02-01 14:51:18 +00:00
|
|
|
</VirtualHost>
|
|
|
|
|
|
|
|
<VirtualHost *:443>
|
2024-10-17 13:17:56 +00:00
|
|
|
ServerName element.example.com
|
2019-02-01 14:51:18 +00:00
|
|
|
|
|
|
|
SSLEngine On
|
|
|
|
|
|
|
|
# If you manage SSL certificates by yourself, these paths will differ.
|
2024-10-17 13:17:56 +00:00
|
|
|
SSLCertificateFile /matrix/ssl/config/live/element.example.com/fullchain.pem
|
|
|
|
SSLCertificateKeyFile /matrix/ssl/config/live/element.example.com/privkey.pem
|
2019-02-01 14:51:18 +00:00
|
|
|
|
|
|
|
SSLProxyEngine on
|
2020-01-30 10:56:20 +00:00
|
|
|
SSLProxyProtocol +TLSv1.2 +TLSv1.3
|
2019-02-01 14:51:18 +00:00
|
|
|
SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
|
|
|
|
|
|
|
|
ProxyPreserveHost On
|
|
|
|
ProxyRequests Off
|
|
|
|
ProxyVia On
|
|
|
|
|
2024-01-14 15:23:28 +00:00
|
|
|
ProxyPass / http://127.0.0.1:81/
|
|
|
|
ProxyPassReverse / http://127.0.0.1:81/
|
2019-02-01 14:51:18 +00:00
|
|
|
|
2024-10-17 13:17:56 +00:00
|
|
|
ErrorLog ${APACHE_LOG_DIR}/element.example.com-error.log
|
|
|
|
CustomLog ${APACHE_LOG_DIR}/element.example.com-access.log combined
|
2019-02-01 14:51:18 +00:00
|
|
|
</VirtualHost>
|