Help on etke.cc

.well-known redirects

Mon, 01 Jan 0001 00:00:00 +0000

Overview¶

Proper .well-known setup is a prerequisite for installing a Matrix server. It is required not only for Matrix clients and servers, but also for the server admin panel, in-app calls, and other features.

You can either point your apex/base domain to the Matrix server IP address, or set up a few redirects on your apex/base domain.

This page covers the second option, as it keeps usernames clean (without the matrix. prefix) while leaving your base domain available for other uses, such as hosting a website.

Here we provide you configuration examples for various web servers and platforms to help you set up the necessary redirects. If you don’t see your web server or platform listed here, please contact us for assistance!

⚠️ If redirects are not properly configured, the Matrix server and services will not work as expected, so please confirm that the redirects are correctly specified. This test tool provided by courtesy of the Matrix Foundation is also helpful to troubleshoot the common issues related to federation. Also, please note that due to technical complexity and nuances we do not support running the Matrix server behind proxied setups.

Web Servers¶

Nginx¶

# This is your HTTPS-enabled server for your-server.com.
# Replace your-server.com with your Matrix server's base/apex domain.
server {
	server_name your-server.com;

 location ^~ /.well-known/matrix/ {
 add_header Access-Control-Allow-Origin "*" always;
 return 301 https://matrix.your-server.com$request_uri;
 }

	# other configuration
}

Apache2¶

# This is your HTTPS-enabled server for your-server.com.
# Replace your-server.com with your Matrix server's base/apex domain.
<VirtualHost *:443>
	ServerName your-server.com

 # Ensure mod_headers and mod_alias (or mod_rewrite) are enabled
 <Location "/.well-known/matrix/">
 Header always set Access-Control-Allow-Origin "*"
 </Location>

 RedirectMatch 301 ^/\.well-known/matrix/(.*)$ https://matrix.your-server.com/.well-known/matrix/$1

	# other configuration
</VirtualHost>

Caddy 2¶

# This is your HTTPS-enabled frontend for your-server.com.
# Replace your-server.com with your Matrix server's base/apex domain.
your-server.com {

 @matrixWellKnown path /.well-known/matrix/*
 header @matrixWellKnown Access-Control-Allow-Origin "*"
 redir @matrixWellKnown https://matrix.your-server.com{uri} 301

	# other configuration
}

Traefik v3¶

The example below uses Docker labels format, but you can adapt it to YAML, TOML, or other formats if needed.


traefik.enable=true

# Router
traefik.http.routers.matrix-wellknown.entrypoints=web
traefik.http.routers.matrix-wellknown.rule=PathPrefix(`/.well-known/matrix/`)
traefik.http.routers.matrix-wellknown.service=noop@internal
traefik.http.routers.matrix-wellknown.middlewares=matrix-wellknown-headers,matrix-wellknown-redirect

# Middleware: CORS headers only for this router
traefik.http.middlewares.matrix-wellknown-headers.headers.accessControlAllowOriginList=*
traefik.http.middlewares.matrix-wellknown-headers.headers.accessControlAllowMethods=GET,OPTIONS
traefik.http.middlewares.matrix-wellknown-headers.headers.accessControlAllowHeaders=*
traefik.http.middlewares.matrix-wellknown-headers.headers.customResponseHeaders.Access-Control-Allow-Origin=*

# Middleware: 301 redirect preserving full URI
# REPLACE your-server.com with your Matrix server's base/apex domain.
traefik.http.middlewares.matrix-wellknown-redirect.redirectregex.regex=^https?://[^/]+(/.well-known/matrix/.*)$
traefik.http.middlewares.matrix-wellknown-redirect.redirectregex.replacement=https://matrix.your-server.com$${1}
traefik.http.middlewares.matrix-wellknown-redirect.redirectregex.permanent=true

Platforms¶

Vercel¶

See the official documentation for more details.

Add the following to vercel.json, replacing your-server.com with your Matrix server’s base/apex domain:

{
 "headers": [
 {
 "source": "/.well-known/matrix/(.*)",
 "headers": [
 {
 "key": "Access-Control-Allow-Origin",
 "value": "*"
 }
 ]
 }
 ],
 "redirects": [
 {
 "source": "/.well-known/matrix/server",
 "destination": "https://matrix.your-server.com/.well-known/matrix/server",
 "statusCode": 301
 },
 {
 "source": "/.well-known/matrix/client",
 "destination": "https://matrix.your-server.com/.well-known/matrix/client",
 "statusCode": 301
 },
 {
 "source": "/.well-known/matrix/support",
 "destination": "https://matrix.your-server.com/.well-known/matrix/support",
 "statusCode": 301
 }
 ]
}

Linux Distribution Upgrade

Mon, 01 Jan 0001 00:00:00 +0000

Need to bump your server’s host OS to a new major version? We can handle the whole upgrade for you for a one-time fee, start to finish. Or, if you’d rather do it yourself at no extra cost, here’s how.

Ubuntu¶

Please use LTS (Long Term Support) versions of Ubuntu only. We recommend using the latest LTS version available at the time of installation.

1. Take a backup¶

Hosting customers: Daily backup (snapshot) is taken automatically every day, the backups are retained for 7 days, you don’t need to do anything.

On-premises customers: Make sure to back up your server before proceeding. All cloud providers have some kind of backup functionality and make snapshots either automatically or on-demand (manually).

2. Set up a fallback port¶

During the upgrade process, the SSH process on your host may be restarted and you may lose connectivity.

The upgrade process usually opens another fallback SSH port (1022) that may be used to get back to the upgrade process. Though the port will be opened automatically, you need to update your firewalls to allow incoming connections to this port.

Also, ensure the screen utility is installed on your system, and start a screen session before proceeding:

screen -S upgrade

If you lose connectivity during the upgrade, reconnect with screen -r upgrade. See resuming a screen session for details.

Hosting customers: the 1022 port is already open on the provider-level firewall, so you only need to update the on-server firewall:

ufw allow 1022/tcp

On-premises customers:

Update your provider-level firewall rules to allow connectivity to the 1022 (TCP) port, if you have one
Update the on-server firewall to allow incoming connections to the fallback port:
```
ufw allow 1022/tcp
```

3. Update the system¶

Before performing the actual distribution upgrade, make sure your system is up-to-date:

# Update the package list
apt-get update
# Upgrade the system packages
apt-get dist-upgrade

You may reboot your server after this step, if prompted to do so.

4. Unpin Docker¶

We pin Docker to a specific version on your server to prevent accidental upgrades to a newer release that may not yet be compatible. Before performing the distribution upgrade, you must remove those pins, otherwise the upgrade process may fail to resolve package dependencies.

# Remove the apt-mark holds
apt-mark unhold docker-ce docker-ce-cli containerd.io docker-buildx-plugin
# Remove the apt-preferences block
rm -f /etc/apt/preferences.d/docker-ce-block

After the distribution upgrade is complete and you have run maintenance via Ketesa Server Actions, the pins will be re-applied automatically.

5. Upgrade to the new release¶

Finally, run the upgrade command:

do-release-upgrade

Follow the on-screen instructions. They are quite straightforward.

Note: if you are upgrading from an older LTS release (e.g., Ubuntu 20.04 while the currently supported LTS release is Ubuntu 24.04), you may need to repeat the process multiple times, as Ubuntu only supports direct upgrades between consecutive LTS releases. We recommend always upgrading to the latest LTS version available.

When doing a multi-hop upgrade, run maintenance after each intermediate release before continuing to the next one. Maintenance will re-pin Docker, so you will need to repeat step 4 (Unpin Docker) before each subsequent do-release-upgrade.

Post-upgrade steps¶

After the upgrade is complete:

Close the fallback port you opened in step 2:
```
ufw delete allow 1022/tcp
```
Run maintenance via Ketesa Server Actions. This will:
- Re-apply the Docker version pin
- Update the Docker apt repository to reference the new distro codename (without this, apt may show errors or install unexpected Docker versions)
- Ensure your server is fully reconfigured for the new OS release

If your Matrix server happens to be down after the upgrade, contact us and we will help you bring it back online.

Matrix Federation

Mon, 01 Jan 0001 00:00:00 +0000

Federation is what lets Matrix users on different servers talk to each other, and it’s core to how the whole protocol works. This page explains what it is, how it works, and why you should leave it on.

TL;DR¶

Is it secure? Yes ✅
Is it safe? Yes ✅
Will any information be leaked? No
Will any random person be able to join my rooms? No
Should I disable it? No
What happens if I disable it? ⚠️ You will not be able to access to many essential features, such as:
- Matrix RTC calls (In-App Calls for Matrix Clients)
- dedicated etke.cc support (priority support)
- the self-service bot
- community moderation policies (shared moderation efforts)
- sticker picker
- integration manager
- and many other functionalities
Can I disable it anyway? Yes, but it is not recommended.
I am scared of federation. Should I be? No

We hope this clarifies any confusion about Matrix Federation.

What is Matrix Federation?¶

Federation allows users on different Matrix servers to participate in the same room. For this to function, external servers must be able to communicate with yours to transmit messages.

Think of Matrix Federation like email: just as you can send an email from Gmail to a Yahoo account and receive a reply, Matrix Federation works in a similar way, ensuring open communication across servers.

🔒 Secure and safe by design¶

Federation lets servers talk to each other without exposing any of your information by default. It’s secure and safe by design.

Here are details about how secure room participation works:

Inviting members: A member with invite privileges can invite someone to a room. This action is logged in the room’s timeline, making it visible to all members. Once the invite is accepted or rejected, it is also recorded in the timeline.
Joining with a link:
- Room administrators must make the room public in the settings. This action is logged.
- Room administrators must assign a room alias, which is also logged.
- (Optional but recommended) Administrators can set the room’s history visibility to Anyone, enabling members to see history from before they joined. This does not apply to end-to-end encrypted rooms.
- Anyone with the room alias can join the room, and their join action will be logged.

Accessing a room requires either an invite or joining a public room. Nobody can access the room without either of them.

Also, reading messages in a room requires membership, obtained through an invite or joining a public room. It is not possible to read them without it.

Disabling federation degrades usability and functionality¶

Federation is a core and fundamental feature of the Matrix protocol, and is required by many useful and important features like in-app calls on Matrix clients, dedicated etke.cc support, self-service bot, sticker picker, integration manager, community moderation policies, and many more.

(Federation is necessary even if an in-app calls happen only among users of your own server, as the backend for it requires federation to be enabled. You can check the relevant code here, if you are interested).

🚨 Disabling federation will severely limit your server’s functionality. You have been warned!

Contact us to disable federation¶

If you would like to disable federation anyway, it is possible for us to do so for you. In this case, please contact us with the following statement, making sure that you are fully aware of expected consequences:

I am fully aware that I want to disable one of the fundamental features of the protocol, effectively limiting my access to modern advancements and reverting to a pre-internet era of isolated networks that do not offer superior information protection. I request that federation be disabled for my server, understanding that this change will leave me with a partially functional server.

Matrix Homeserver Moderation

Mon, 01 Jan 0001 00:00:00 +0000

We run managed Matrix servers, but we don’t own or control them, and that’s the whole point. We handle the technical side (installation, updates, backups, monitoring), your data stays yours, and we never touch what happens inside your homeserver.

The flip side of that freedom: moderation is your job as the owner. This guide walks through why it matters, what to watch for, which tools actually work, and where to find people who’ve been through it.

And you won’t be doing it alone. We’ve teamed up with Muninn Hall, a community of developers, moderators, and community managers who have seen it all, from lone trolls to full-scale spam waves, and they share what they know.

Why moderation is important¶

Without moderation, a server can quickly become unpleasant or even unsafe. Here are some threats you may face:

Spammers: flood your rooms with ads, crypto scams, and noise that drowns out real conversation
Phishers and scammers: DM your users to trick them out of credentials, money, or data
Abusers and trolls: harass people until your regulars get tired and leave
Illegal content: from pirated media to child abuse material, the kind that gets servers seized and police involved
Unwanted bots: fake activity, amplified garbage, relentless noise

What to moderate¶

Open registration servers¶

If your instance is public and anyone can sign up, make sure to:

Protect registration (for example, use email verification or CAPTCHAs)
Keep an eye on new accounts (they can upload harmful avatars or spam)
Check new rooms (users can create spaces with illegal or unwanted content)
Watch out for inactive accounts that may suddenly start abusing the server

Closed or invite-only servers¶

If registration is restricted, moderation is simpler, but public rooms and invited users still need oversight.
We strongly recommend running Draupnir in either case.

How to moderate¶

There are several ways to moderate your communities.

Admin dashboard¶

Your Ketesa dashboard (installed by default) lets you:

Suspend (make read-only), ban, or shadowban users. A shadowbanned user keeps posting into the void; nobody else sees a thing.
Redact messages or uploaded media
Remove problematic rooms

This is your “control center” for quick moderation.

Moderation bot¶

Matrix does not come with built-in moderation, so you will need a bot.
We recommend Draupnir. It works well for both small servers and large communities.

See our quick start guide for an easy setup with safe defaults suggested by Muninn Hall and Draupnir developers.

Knowledge¶

Tools are powerful, but knowing how to respond is equally important.
For example:

The Matrix Community Help guides are an excellent starting point.
For deeper insights, see the Muninn Hall docs.

Coordination¶

No homeserver owner can fight abuse alone. The best approach is to coordinate with others.
Muninn Hall gives you:

Active Threats list that plugs straight into Draupnir if you follow our guide
Alerts room that pings you early when a spam wave hits the network or your own server
Announcements for policy and tooling updates
Discussion rooms to ask questions and compare notes with people who’ve been there
Off-topic chat for everything else

Muninn Hall cannot be joined directly. It is a focused community for server admins and moderators, with a short screening process before joining. Once you are in, you can invite your moderation team as well.

👉 How to join Muninn Hall

Where to start¶

Running your own homeserver means running its moderation too: the cost of self-governance. Good tools make it far lighter than it looks.

Start small: lock down registration, set up Draupnir, and read the basic guides. Ketesa and Draupnir do the heavy lifting, and Muninn Hall means you’ve always got people to ask. Step by step, you’ll get the hang of it.

Payments

Mon, 01 Jan 0001 00:00:00 +0000

etke.cc uses the Ko-Fi payment and subscription management platform, which itself uses PayPal and Stripe for payment processing. At the moment, we don’t support any other subscription or payment options.

Ko-Fi works well, but a few corners of it aren’t exactly obvious. So here’s how to handle the common payment scenarios, step by step.

How to Become a Subscriber¶

To access etke.cc’s services and manage your subscription later (to update its price, to fix it if payments are failing, or to cancel it), you’ll need to set up a subscription with recurring payments on Ko-Fi. For this reason:

it is recommended that you sign up for Ko-Fi now (before paying for your etke.cc order), so that the subscription will be automatically associated with your account at Ko-Fi.

⚠️ When signing up for Ko-Fi, make sure to use the same email address as you provided when placing the order at us. If you submit another email address, our system won’t be able to automatically match it to the order, so you would need to contact us about it.
alternatively, you can create an account at Ko-Fi later, after becoming our subscriber and paying for an order without the account. However, please make sure to sign up with the same email address as you have provided for your subscription (see below).

To become an etke.cc subscriber, follow the steps below:

Sign into your Ko-Fi account, if you have one already. You can also become a subscriber without a Ko-Fi account, as mentioned above.
Visit the etke.cc membership page on Ko-Fi.
Select the By Complexity tier.
Enter the following details:
- Pay what you want: Input the total price based on the components you have ordered.
- Email address: This field only appears when ordering without a Ko-Fi account. Please make sure to use the same email address you provided when placing the order with us.
- Your name or nickname: (optional) Use any name you wish.
Press the Pay button to proceed to checkout. You may see PayPal and/or Stripe as options, depending on your region and Ko‑Fi availability.
Select your preferred payment method or add a new one and click on Agree & Continue.
If the payment is successful, you’ll be redirected to the payment confirmation page on Ko-Fi.

Congratulations! You’re all set 🎉

We’ll receive a notification from Ko-Fi and will begin preparing your Matrix server. Keep an eye on your email for updates.

If you have created a Ko-Fi account, you can also review your account’s Payments and Orders page at Ko-Fi. Additionally, you can view your payment history and download invoices from the Billing page in Ketesa.

How to Update Your Subscription Price¶

If you subsequently order new services from us or cancel some services we were providing until now, you may need to adjust the price of your subscription to align it with the new cost.

You will need your Ko-Fi account to manage your etke.cc subscription on the Ko-Fi platform. If you have not created a Ko-Fi account early on, you can create one now by going to Ko-Fi’s signup page. When signing up, make sure to use the same email address that you used for your already-existing subscription. This way, Ko-Fi will automatically attribute this subscription to your new account.

To update your subscription’s price, follow the steps below:

Log in to your Ko-Fi account
Visit your Ko-Fi account page
Locate your etke.cc subscription in the list.
Click on the three-dots dropdown menu and press the Update Pledge button
Enter the new, recalculated price into the input field and click Update
Confirm the changes by clicking Yes, update pledge
You’ll be charged using the new subscription price during the next payment period (e.g. next month), not immediately. To make up for the difference during the current payment period, make a one-time Ko-Fi donation with a custom price equal to the price difference between the new price and the old price. For example, if going from €10/mo subscription to a €25/mo subscription, make a one-time payment of €15.

Congratulations, you’ve successfully updated your subscription price! 🎉

Your Ko-Fi account page should now reflect these changes:

How to Cancel Your Subscription¶

WARNING: by canceling your subscription, you will lose access to all services provided by etke.cc:

(in case of hosting) your Matrix server will be erased, including all its data and backups, there won’t be an option to restore it later

no updates, security fixes, housekeeping, or support will be provided, etc.

no monitoring, private docker registry, self-service bot, etc.

even no exclusive admin panel features will be available

If, for any reason, you don’t wish to continue with your subscription, you can cancel it.

You will need a Ko-Fi account to manage your etke.cc subscription on the Ko-Fi platform. If you haven’t created a Ko-Fi account early on, you can create one now by going to Ko-Fi’s signup page. When signing up, make sure to use the same email address that you used for your already-existing subscription. This way, Ko-Fi will automatically attribute this subscription to your new account.

To cancel your subscription, follow the steps below:

Log in to your Ko-Fi account
Visit your Ko-Fi account page
Locate your etke.cc subscription in the list.
Click on the three-dots dropdown menu and press the Don’t Renew button.
Confirm the changes by clicking Yes, cancel it

Your canceled subscription will now appear on your Ko-Fi account page.

Note: Depending on the automatic renewal status and the number of retry attempts, the canceled subscription may not be immediately visible or may appear differently.

At this point, you are no longer an etke.cc subscriber. Nevertheless, we’ll continue providing the service you were paying for until the end period you paid for. If you wish for us to stop providing the service immediately, please contact us.

How to Fix a Failing Subscription¶

If, for any reason, your subscription fails to renew automatically, you may need to resubscribe manually.

To resubscribe, follow the steps below:

Cancel your existing subscription. See the How to Cancel Your Subscription guide
Subscribe again. See the How to Become a Subscriber guide

How to get invoices for your payments¶

If you need to obtain invoices for your payments, you can do so through the Billing page in Ketesa. This page provides access to all your payment history and allows you to download invoices for each transaction.

We deploy admin panel on https://matrix.your-server.com/admin (replace your-server.com with your actual server domain). To access the admin panel, you need to have an admin user account on your Matrix server.

How to add company details to the invoices¶

You can add your company details to the future invoices directly in your Ketesa admin panel on the Billing page.

The changes will be applied to all future invoices, but not to the past ones.

Removed Components

Mon, 01 Jan 0001 00:00:00 +0000

You were likely redirected here from a removed or deprecated page. You may wish to check our full list of bridges, bots, or extra services for the latest information.

It’s been a long time since we deprecated certain components and replaced them with better-working alternatives. Even though the old components were deprecated and considered unmaintained by us, some of our customers continued using them for a long time.

Even after marking these components unmaintained, we kept putting effort into supporting them, trying to fix the problems our customers ran into. In the end, such components still misbehaved once in a while and we couldn’t always make them fully work. If a component is unmaintained by its developers, we cannot help maintaining it ourselves because eventually it becomes incompatible with modern APIs, and there is nobody to fix the component’s code and make it compatible again.

This has prompted us to re-evaluate the current status of our deprecated components. To avoid having to invest our effort in maintaining obsoleted components, we have completely eliminated all deprecated components after a long grace period.

Removed / deprecated components¶

Here is the list of the removed or deprecated components:

ChatGPT Bot (matrix-chatgpt-bot): unmaintained by its developers since November 2023. It got superseded by Baibot.
Dimension integration manager: unmaintained by its developers since November 2022. There is no free-software alternative integration manager.
Discord bridge (mx-puppet-discord) : unmaintained by its developers since May 2022. It got superseded by Discord bridge (mautrix-discord).
Facebook bridge (mautrix-facebook): archived by its developers on March 2024. It got superseded by Facebook bridge (mautrix-meta).
Firezone - superseded by WG Easy
GroupMe Bridge (mx-puppet-groupme): unmaintained by its developers since November 2021. There is no free-software alternative GroupMe bridge.
Instagram bridge (mautrix-instagram): archived by its developers on March 2024. It got superseded by Instagram bridge (mautrix-meta).
LinkedIn bridge (beeper-linkedin): archived by its developers in March 2025. It got superseded by LinkedIn bridge (mautrix-linkedin).
Skype bridge (go-skype-bridge): Skype was shut down in May 2025.
Slack bridge (mx-puppet-slack): unmaintained by its developers since May 2022. It got superseded by Slack bridge (mautrix-slack).
Steam Bridge (mx-puppet-steam): this uses obsolete framework/base unmaintained by its developers since May 2022. There is no free-software alternative Steam bridge.
WeChat bridge (matrix-wechat): unmaintained by its developers since February 2024. There is no free-software alternative WeChat bridge.
Webhooks bridge (appservice-webhooks): unmaintained by its developers since November 2022. It got superseded by Webhooks bridge (hookshot).
Wireguard (and dnsmasq): superseded by WG Easy.

Restoring servers from backups

Mon, 01 Jan 0001 00:00:00 +0000

Servers die. A disk gives out, an update goes sideways, and suddenly the only thing between you and a very bad day is a backup. Good news: you’ve got them. Here’s how to bring one back.

Honestly, the easiest path is to contact us and let us do the restore. Pulling servers back from the brink is sort of our whole thing. But if you’d rather get your hands dirty, read on: we’ll walk you through it and flag the spots where it bites. And if you’re on one of our hosting plans, you’re already covered: daily full-server snapshots, kept for 7 days, nothing for you to set up.

BorgBackup ¶

If your server has BorgBackup installed, follow these steps to restore a backup:

Get the list of all available backups using /matrix/backup-borg/bin/borgmatic rlist.
List the files in the archive. Usually, you need specific files from the archive, and extracting a full backup may require a lot of disk space. However, if you need to extract the full archive, skip this step. To find a specific file (e.g., Twitter bridge DB dump), use the following command: /matrix/backup-borg/bin/borgmatic list --archive <ARCHIVE> --find borgmatic/postgresql_databases/matrix-postgres\:5432/ (replace <ARCHIVE> with the archive name from the first step). Example: /matrix/backup-borg/bin/borgmatic list --archive matrix-2025-04-04-021409 --find borgmatic/postgresql_databases/matrix-postgres\:5432/.
Extract the needed files from the archive using the command /matrix/backup-borg/bin/borgmatic extract --archive <ARCHIVE> --destination /restore --path <LIST OF PATHS> (replace <ARCHIVE> with the archive name from the first step and <LIST OF PATHS> with a space-separated list of paths without leading slash. If you want to extract the full archive, omit the --path parameter). Example: /matrix/backup-borg/bin/borgmatic extract --archive matrix-2025-04-04-021409 --destination /restore --path /borgmatic/postgresql_databases/matrix-postgres/matrix_mautrix_twitter.
The extracted files will be in /matrix/backup-borg/restored on the host (the --destination /restore inside the container maps to this path). Do whatever you need with them, and don’t forget to remove them when you’re done.

Local Postgres Backups¶

Enabled by default only for on-premises servers without any other backup solution. If you’d like to enable local Postgres backups on your server, please contact us.

Find a usable backup in /matrix/postgres-backup/data/last; it is usually the latest one (e.g., synapse-latest.sql.gz).
Replace placeholders and run the following script on the server:

/usr/bin/env docker run --rm --name matrix-postgres-import \
--log-driver=none --user=998:1001 --cap-drop=ALL --network=matrix \
--env-file=/matrix/postgres/env-postgres-psql \
--mount type=bind,src=./DATABASE_DUMP.sql.gz,dst=/dump.sql.gz,ro \
--entrypoint=/bin/sh docker.io/postgres:POSTGRES_VERSION-alpine \
-c "cat /synapse_dump.sql | gunzip -c | grep -vE '^(CREATE|ALTER) ROLE (matrix)(;| WITH)' | grep -vE '^CREATE DATABASE (matrix)\s' | psql -v ON_ERROR_STOP=1 -h matrix-postgres --dbname=DATABASE_NAME"

DATABASE_DUMP.sql.gz: file name on the host filesystem you want to import.
POSTGRES_VERSION: Postgres version; you can find the actual version by running cat /etc/systemd/system/matrix-postgres.service | grep -o "postgres:.*-alpine".
DATABASE_NAME: the actual database name (e.g., synapse or postmoogle). Usually, the backup filename uses the format: <database_name-timestamp>.sql.gz.

VPS to VPS migration

Mon, 01 Jan 0001 00:00:00 +0000

Need to move your Matrix server from one box to another? We can handle the whole migration for you for a one-time fee: setting up the new server, transferring the data, and making sure everything comes back up. Or, if you’d rather do it yourself at no extra cost, here’s how.

Important: This applies only to Matrix servers with custom domains. It covers migrations between cloud hosting and on-premises servers (in either direction), as well as between on-premises servers, but not migrations between two cloud-hosted servers.

Set DNS TTLs to 5 minutes for all Matrix-related DNS records.
Copy etke.cc’s SSH key from the old server to the new server.
Share the SSH login information with us, along with the sudo password (if set) and the new server’s IP address.
Generate a new SSH key on the new server using ssh-keygen -t ed25519 -N '' -C migration. Add the public key to the old server’s .ssh/authorized_keys file (preferably as root).
Stop and disable all Matrix services from auto-starting on the old server by running cd /etc/systemd/system/ && systemctl disable --now matrix-*. Verify they are stopped with systemctl | grep matrix- (a failed status is fine; what matters is that no Matrix services are actively running).
Update all Matrix-related DNS records to point to the new server.
Start a new screen session on the new server by running screen -R.
Migrate the data to the new server by running rsync -arP OLD_SERVER_USER@OLD_SERVER_IP:/matrix/ /matrix (replace OLD_SERVER_USER and OLD_SERVER_IP with the appropriate values).
Create the matrix group and user on the new server by running groupadd --system matrix && useradd --system --gid=matrix --no-create-home --home-dir=/matrix --shell=/sbin/nologin matrix.
Fix ownership of the /matrix files on the new server by running chown -hR matrix:matrix /matrix.
Inform us once the data migration is complete. We will then run a full setup process to properly configure the new server.

If you have a Matrix client with an active session, it will reconnect once services are back up. Expect a few minutes of instability while things settle.

We recommend completing steps 1 and 2 first so we can confirm connectivity to your new server.

The subsequent steps require stopping services on the old server. Matrix services will be down until the data is copied to the new server, you contact us, and we complete the full setup process. This final coordination step may take some time, especially over weekends or at night (in Europe), which can lead to extended downtime.

It’s best to perform the last steps at a time agreed with us in advance to ensure a quick turnaround. Be aware that your Matrix services will be down once you stop them, so you’ll need to contact us using one of the other methods listed on our contacts page.

Help on etke.cc

.well-known redirects

Overview¶

Web Servers¶

Nginx¶

Apache2¶

Caddy 2¶

Traefik v3¶

Platforms¶

Vercel¶

Linux Distribution Upgrade

Ubuntu¶

1. Take a backup¶

2. Set up a fallback port¶

3. Update the system¶

4. Unpin Docker¶

5. Upgrade to the new release¶

Post-upgrade steps¶

Matrix Federation

TL;DR¶

What is Matrix Federation?¶

🔒 Secure and safe by design¶

Disabling federation degrades usability and functionality¶

Contact us to disable federation¶

Matrix Homeserver Moderation

Why moderation is important¶

What to moderate¶

Open registration servers¶

Closed or invite-only servers¶

How to moderate¶

Admin dashboard¶

Moderation bot¶

Knowledge¶

Coordination¶

Where to start¶

Payments

How to Become a Subscriber¶

How to Update Your Subscription Price¶

How to Cancel Your Subscription¶

How to Fix a Failing Subscription¶

How to get invoices for your payments¶

How to add company details to the invoices¶

Removed Components

Removed / deprecated components¶

Restoring servers from backups

BorgBackup¶

Local Postgres Backups¶

VPS to VPS migration

BorgBackup ¶