etke.cc
etke.cc
🌓 Theme

Monitoring

At etke.cc, we keep an eye on your Matrix server so you do not have to. This service is included with every server subscription.

What is monitored?¶

Here is what we keep an eye on:

Ports¶

We make sure the expected ports are reachable based on the services you have enabled. For a basic Matrix server without add-ons, we monitor:

  • 22/tcp — SSH port
  • 80/tcp, 443/tcp, 443/udp — HTTP and HTTPS. UDP is required for HTTP/3.
  • 8448/tcp and 8448/udp — Matrix federation port (if federation is enabled). UDP is required for HTTP/3.
  • 3478/tcp+udp, 5349/tcp+udp — TURN ports (VoIP calls)
  • 49152-49573/udp — TURN ports (VoIP calls)

If you have additional components, for example the Postmoogle email bridge, we also monitor extra ports: 25/tcp and 587/tcp (SMTP).

A complete list of required ports per component is available in the Ports and Firewalls FAQ section.

DNS records¶

We make sure the DNS records your server relies on are present and correct. For a basic Matrix server without add-ons, we monitor:

  • @ base/apex domain record — should exist and point to your server’s IP address (only if you serve the base domain from the Matrix server itself)
  • matrix subdomain record — should exist and point to your server’s IP address

If you have additional components, for example linkding, we also monitor extra DNS records such as the linkding subdomain. As with the records above, it should exist and point to your server’s IP address (via CNAME or A record).

HTTP endpoints¶

We check that the HTTP endpoints for the services you have enabled are reachable. For a basic Matrix server without add-ons, we monitor:

  • https://your-server.com/.well-known/matrix/server — Matrix server discovery endpoint (Matrix Federation API, if federation is enabled)
  • https://your-server.com/.well-known/matrix/client — Matrix server discovery endpoint (Matrix Client-Server API)
  • https://your-server.com/.well-known/matrix/support — Matrix server contacts endpoint (MSC1929, part of Matrix protocol v1.10)
  • https://matrix.your-server.com:8448/_matrix/federation/v1/version — Matrix Federation version endpoint (Matrix Federation API, if federation is enabled)
  • https://matrix.your-server.com/_matrix/client/versions — Matrix client version endpoint (Matrix Client-Server API)
  • https://element.your-server.com — Element web client (enabled by default on all servers)

If you have additional components, for example Funkwhale, we also monitor extra endpoints such as https://funkwhale.your-server.com/api/v1/instance/nodeinfo/2.0 — the Funkwhale NodeInfo endpoint.

VPS metrics¶

We track basic metrics on your Matrix server host:

  • CPU — CPU usage; we recommend keeping it below 80% for optimal performance
  • RAM — RAM usage; we recommend keeping it below 80% for optimal performance
  • Disk — disk usage; we recommend keeping it below 80% for optimal performance. If you have a /matrix mountpoint configured, we monitor that instead of the root / mountpoint
  • Units — failed systemd units; we monitor the state of the Docker containers to ensure all services are running as expected

If any metric exceeds the recommended values, we let you know.

How long is the monitoring data stored?¶

We keep the last 7 days of monitoring data on our side.

How to access the monitoring data?¶

You can access the monitoring report by opening the Server Status page in Synapse Admin, by using the Scheduler ping command, or via automatic monitoring alerts.

How the report is looks like?¶

All services are up and running¶

This example shows that all services are up and running, and there are no issues with the server.

There are issues with the server¶

This example shows issues that require your attention, namely:

  • High disk utilization
  • Timeout on the 25/tcp and 587/tcp ports
  • Invalid content in the delegation endpoint (/.well-known/matrix/server)
  • Invalid DNS records for the social.etke.cc subdomain

How do I get the monitoring report?¶

On-demand¶

You can get the monitoring report by opening the Server Status page in Synapse Admin, or by using the Scheduler ping command.

Automatic¶

We send monitoring alerts to your Matrix account and email address. The report is generated daily between 3 a.m. and 5 a.m. UTC (fixed schedule).

To avoid spamming you with repeated alerts, we send the report once per week if nothing changes. If the same issue persists for a week, you will receive the alert again; if a new issue appears, you will receive a new alert on the same day.

What to do if the monitoring report shows issues?¶

Different issues call for different actions. Below are the most common issues and the recommended steps to resolve them.

DNS records failures¶

If the monitoring report shows DNS record failures, please review your DNS configuration:

  • All Matrix-related subdomains should point to your server’s IP address
  • If you serve the base/apex domain from the Matrix server itself, it should also point to your server’s IP address
  • If you use any DNS proxy (like Cloudflare Proxy), it should be disabled for all Matrix-related records

If that does not help, please contact us and we will help you resolve the issue.

High CPU usage¶

If CPU usage is consistently above 80%, consider upgrading your server or removing additional components.

The minimum recommended configuration for a basic Matrix server without any add-ons is 2 vCPUs:

  • If your server has fewer than 2 vCPUs, upgrade as soon as possible
  • If your server has 2 vCPUs and additional components enabled, consider removing them
  • If your server has 2 vCPUs and no additional components, high CPU can be caused by a user joining a large federated room (1000+ members). You can identify and remove such rooms using Synapse Admin

On-premises servers: resize your server to a more powerful one via your VPS provider dashboard.

Hosting by etke.cc: please contact us to discuss upgrade options.

High RAM usage¶

If RAM usage is consistently above 80%, consider upgrading your server or removing additional components.

The minimum recommended configuration for a basic Matrix server without any add-ons is 2 GB of RAM:

  • If your server has less than 2 GB of RAM, upgrade as soon as possible
  • If your server has 2 GB of RAM and additional components enabled, consider removing them
  • If your server has 2 GB of RAM and no additional components, high RAM can be caused by a user joining a large federated room (1000+ members). You can identify and remove such rooms using Synapse Admin

On-premises servers: resize your server via your VPS provider dashboard.

Hosting by etke.cc: please contact us to discuss upgrade options.

High Disk usage¶

Note: If you have a /matrix mountpoint configured, we monitor that instead of the root / mountpoint.

If disk usage is consistently above 80%, consider upgrading your server or removing old media using Synapse Admin.

The minimum recommended configuration for a basic Matrix server without any add-ons is 40 GB of disk space:

  • If your server has less than 40 GB of disk space, upgrade as soon as possible
  • If your server has 40 GB of disk space, consider removing old media using Synapse Admin
  • If your server has 40 GB of disk space and you do not want to remove old media, consider upgrading your server

On-premises servers: resize your server’s disk via your VPS provider dashboard.

Hosting by etke.cc: please contact us to discuss upgrade options.

Units failures¶

If the report shows Units failed, something is wrong with specific components. This can be a consequence of other issues, such as:

If the report does not contain other issues, please contact us and we will help you resolve it. Otherwise, address the other issues first and run the check again.

Metrics failures¶

If the report shows Metrics failed, something is wrong with your VPS or DNS. This is usually the result of other issues. Possible reasons include:

On-premises servers: ensure all mandatory ports are open and reachable from the internet, DNS records are configured properly, and CPU/RAM/Disk utilization is below 80%. If that does not help, please contact us and we will help you resolve the issue.

Hosting by etke.cc: ensure DNS records are configured properly. If that does not help, please contact us and we will help you resolve the issue.

/.well-known/matrix/server failures¶

If the /.well-known/matrix/server endpoint is unavailable (404, invalid content, or any other error), ensure delegation is configured correctly.

  • If your base/apex domain is served outside the Matrix server (for example, you have a website on that domain), refer to the delegation redirects configuration FAQ section.
  • If your base/apex domain is served by the Matrix server itself, please contact us and we will help you resolve it.

/.well-known/matrix/client failures¶

If the /.well-known/matrix/client endpoint is unavailable (404, invalid content, or any other error), ensure delegation is configured correctly.

  • If your base/apex domain is served outside the Matrix server (for example, you have a website on that domain), refer to the delegation redirects configuration FAQ section.
  • If your base/apex domain is served by the Matrix server itself, please contact us and we will help you resolve it.

Note: If the issue is missing CORS headers, refer to the delegation redirects configuration FAQ section. This happens because the client discovery endpoint is served from the base/apex domain; since that domain is hosted outside the Matrix server, you must add the CORS headers yourself.

/.well-known/matrix/support failures¶

If the /.well-known/matrix/support endpoint is unavailable (404, invalid content, or any other error), ensure delegation is configured correctly.

  • If your base/apex domain is served outside the Matrix server (for example, you have a website on that domain), refer to the delegation redirects configuration FAQ section.
  • If your base/apex domain is served by the Matrix server itself, please contact us and we will help you resolve it.

/_matrix/federation/v1/version failures¶

If the /_matrix/federation/v1/version endpoint is unavailable (404, invalid content, or any other error), something is wrong with your Matrix server. This is usually a symptom rather than a root cause, so check for other issues first (typically high CPU, RAM, or disk usage).

If your server has the Matrix Federation API disabled and you still see this error, please contact us and we will help you resolve it.

/_matrix/client/versions failures¶

If the /_matrix/client/versions endpoint is unavailable (404, invalid content, or any other error), something is wrong with your Matrix server. This is usually a symptom rather than a root cause, so check for other issues first (typically high CPU, RAM, or disk usage).

Any other HTTP endpoints failures¶

Please double-check:

  • DNS records are configured properly, pointing to the Matrix server’s IP, and any DNS proxy (like Cloudflare Proxy) is disabled for Matrix-related subdomains
  • Ports are open and reachable from the internet (on-premises servers only)
  • CPU, RAM, and disk usage are below 80%

If that does not help, please contact us and we will help you resolve the issue.

Ports failures¶

Port failures mean an expected port is unreachable. The most common reasons are:

  • misconfigured firewall (on-premises servers)
  • high CPU, RAM, or disk usage

On-premises servers: ensure all mandatory ports are open and reachable from the internet. If that does not help, please contact us and we will help you resolve the issue.

Hosting by etke.cc: please contact us and we will help you resolve the issue.

Don't have a Matrix server yet?

We specialize in setup, hosting and maintenance of Matrix and various Matrix & non-Matrix add-ons.
Hosting is on affordable VPS servers provided by us (via Hetzner Cloud) in the EU, US and Asia, or on your own infrastructure anywhere in the world.

Let's build your Matrix haven together!

Order Now