matrix-docker-ansible-deploy/docs/configuring-playbook-base-domain-serving.md

Serving the base domain

This playbook sets up services on your Matrix server (matrix.DOMAIN). To have this server officially be responsible for Matrix services for the base domain (DOMAIN), you need to set up Server Delegation. This is normally done by configuring well-known files on the base domain.

People who don't have a separate server to dedicate to the base domain have trouble arranging this.

Usually, there are 2 options:

• either get a separate server for the base domain, just for serving the files necessary for Server Delegation via a well-known file

• or, arrange for the Matrix server to serve the base domain. This involves using your own webserver or making the integrated webserver somehow serve your base domain (possible, but complicated).

To solve this problem, we've created an easy way to let you serve the base domain from the Matrix server via the integrated webserver (matrix-nginx-proxy).

Just adjust your DNS records, so that your base domain is pointed to the Matrix server's IP address and use the following configuration:

matrix_nginx_proxy_base_domain_serving_enabled: true

Doing this, the playbook will:

• obtain an SSL certificate for the base domain, just like it does for all other domains (see how we handle SSL certificates)

• serve the /.well-known/matrix/* files which are necessary for Federation Server Discovery (also see Server Delegation) and Client-Server discovery

• serve a simple homepage at https://DOMAIN with content Hello from DOMAIN (configurable via the matrix_nginx_proxy_base_domain_homepage_template variable)