etke.cc
etke.cc
🌓 Theme

Order Status

Loading...

FAQ

Delegation Redirects

We typically host your Matrix server on a subdomain, such as matrix.your-server.com. That normally results in full usernames that include the matrix. prefix (for example, @someone:matrix.your-server.com).

However, by default we set up the Matrix server on the subdomain such that the usernames do not include the prefix (@someone:your-server.com). This is similar to email services: your email address would be someone@your-server.com, while your email server might actually live at mail.your-server.com.

To do so, it is necessary to configure “delegation”. On Matrix protocol is there a couple of ways of setting it up, but etke.cc supports the “.well-known” file method only.

There are two options for setting up delegation:

Option 1: Apex/base domain DNS record

If your apex/base domain is not used by a service such as a website, you can simply point this domain’s DNS record to the Matrix server’s IP address by adding the @ record, in the same way as adding the matrix A/AAAA records.

With this option, we will handle the delegation redirects on your behalf.

You can always switch to the option 2 below, if you’ll host a service on the base domain.

Option 2: Delegation redirects

If you have an existing service on your base domain already, setting up the redirects from the apex/base domain should be more convenient, as it enables you to keep it for the service.

With this option, you manually need to configure all the redirects below (assuming your base domain is your-server.com):

It is also necessary to add the CORS header below to the responses for these redirects, as required by the Matrix specification: Access-Control-Allow-Origin: *

You may find examples of how to configure these redirects for various web servers and platforms in our .well-known redirects guide.

⚠️ You cannot configure HTTPS redirects using a DNS management dashboard. You need a web server running on your base domain to handle those redirects. Please do not confuse this with “URL forwarding” or “Domain redirect” offered by your DNS provider. It will not work for delegation redirects.

Ports and Firewalls

Matrix server components require various ports for operation.

For the managed hosting plan, we will take care of the ports configuration for you.

In case of on-premises setups, you may need to adjust your firewall settings to allow traffic on the ports. Here is a list of the mandatory ports for the base components of the Matrix stack:

Jitsi:

These ports are required only if you want to install Jitsi on your server:

Email bridge:

These ports are required only if you want to install Postmoogle on your server:

IRC bridge:

These ports are required only if you want to install Heisenbridge on your server:

WG Easy:

These ports are required only if you want WG Easy on your server:

Peertube:

These ports are required only if you want Peertube on your server: