Advanced Search
Search Results
186 total results found
Setting Up the IRC Bridge
Matrix IRC Bridge The Matrix IRC Bridge is an IRC bridge for Matrix that will pass all IRC messages through to Matrix, and all Matrix messages through to IRC. Please also refer to the bridges' specific documentation for additional guidance. For usage of the IR...
Setting Up the SIP Bridge
Configuring SIP bridge Basic config From the Installer's Integrations page, click "Install" under "SIP Bridge" For the provided sipbridge.yml, please see the following documentation: - `postgres_create_in_cluster`: `true` to create the postgres db into the k8s...
Setting Up the XMPP Bridge
Configuring the XMPP Bridge The XMPP bridge relies on the xmpp "component" feature. It is an equivalent of matrix application services. You need to configure an XMPP Component on an XMPP Server that the bridge will use to bridge matrix and xmpp user. On the ho...
Setting up Location Sharing
Overview The ability to send a location share, whether static or live, is available without any additional configuration. However, when receiving a location share, in order to display it on a map, the client must have access to a tile server. If it does not, t...
Removing Legacy Integrations
Today, if you remove a Yaml integration's config, its components will not be removed from the cluster automatically. You will also need to manually remove the custom resources from the Kubernetes cluster. Removing Monitoring stack You need to delete first the ...
Setting up Sliding Sync
Introduction to Sliding Sync Sliding Sync is a backend component required by the Element X client beta. It provides a mechanism for the fast synchronisation of Matrix rooms. It is not recommended for production use and is only provide to enable the usage of th...
Setting Up the Skype for Business Bridge
Configuring the Skype for Business Bridge Domains and certificates The first step in preparing a Skype for Business (S4B) Bridge is to assign it a hostname that other S4B Server deployments can connect to it via SIP federation. This requires configuring DNS r...
Synapse Section: Additional Config
The Additional Config section, which allows including config not currently configurable via the UI from the Configuration Manual, is available under the 'Advanced' section of the Synapse page. We strongly advise against including any config not configurable vi...
Synapse Section: Workers
The Workers section, which allows you to configure Synape Workers, is available under the 'Advanced' section of the Synapse page. What are Synapse Workers Synapse is built on Python, an inherent limitation of which is only being able to execute one thread at a...
Kubernetes Override Sections
Found in under Advanced in any section where you configure a component of the installer, under the Kubernetes heading. Here you can override Kubernetes configuration for each component. Common Annotations In Kubernetes, annotations are key-value pairs associ...
Secrets
Find out more about the Secrets block found under each Sections' Advanced configuration options Under 'Advanced' in each section, you may find a block listing all the associated secrets configured as part...
How to run a Webserver on Standalone Deployments
This guide is does not come with support by Element. It is not part of the Element Server Suite (ESS) product. Use at your own risk. Remember you are responsible of maintaining this software stack yourself. Some config options require a web content to be serve...
ESS CRDs support in ArgoCD
ArgoCD can support getting the ESS CRDs Status as resource health using Custom Health Checks You need to configure the following under the configmap argocd-cm of argocd : data: resource.customizations: | matrix.element.io/*: health.lua: | h...
Verifying ESS releases against Cosign
Cosign ESS Verification Key ESS does not use Cosign transaction log to be able to support airgapped deployment. We are instead relying on a public key that you can ask if you need to run image verification in your cluster. The ESS Cosign public key is the foll...
Notifications, MDM & Push Gateway
The stock Android and iOS Apps will use an Element owned Push Gateway to send Notification via the Apple or Google Notifiction Services. The URL of our push gateway is https://matrix.org/_matrix/push/v1/notify The apps will on startup register with the Google ...
Automating ESS Deployment
Understand your ESS configuration files and how you can automate ESS deployment(s). The .element-enterprise-server Directory Config examples included on this page may not up-to-date and are solely provide...
Configuring Element Desktop
Element Desktop is a Matrix client for desktop platforms with Element Web at its core. You can download Element Desktop for Mac, Linux or Windows from the Element downloads page. See https://web-docs.element.dev/ for the Element Web and Desktop documentation. ...
Migrating from Self-Hosted to ESS
This document is currently work-in-progress and might not be accurate. Please speak with your Element contact if you have any questions. Preparation This section outlines what you should do ahead of the migration in order to ensure the migration goes as quickl...
Using the Admin Console
AKA the Installer GUI, a quick overview of the Configure and Admin tabs and the sections within. Opening the Admin Console First, let’s get started by logging into the admin console. To do this, make sure...
Using the Admin Tab
Users Section By default the users section will display all active user accounts present on your homeserver, listing their Matrix ID followed by their Display Name and whether the user is a Synapse Admin. Navigating Users will be displayed in a list, defaulti...