title | nav_order | permalink |
---|---|---|
FAQ |
1 |
/faq |
Dendrite aims to provide a matrix compatible server that has low resource usage compared to Synapse. It also aims to provide more flexibility when scaling either up or down. Dendrite's code is also very easy to hack on which makes it suitable for experimenting with new matrix features such as peer-to-peer.
Mostly, although there are still bugs and missing features. If you are a confident power user and you are happy to spend some time debugging things when they go wrong, then please try out Dendrite. If you are a community, organisation or business that demands stability and uptime, then Dendrite is not for you yet - please install Synapse instead.
No, although a good portion of the Matrix specification has been implemented. Mostly missing are client features - see the readme at the root of the repository for more information.
Dendrite development is currently supported by a small team of developers and due to those limited resources, the majority of the effort is focused on getting Dendrite to be specification complete. If there are major features you're requesting (e.g. new administration endpoints), we'd like to strongly encourage you to join the community in supporting the development efforts through contributing.
No, not at present. There will be in the future when Dendrite reaches version 1.0. For now it is not possible to migrate an existing Synapse deployment to Dendrite.
No, Dendrite has a very different database schema to Synapse and the two are not interchangeable.
Yes, use the cli flag -http-bind-address
.
Check the Federation Tester. You need at least:
- A valid DNS name
- A valid TLS certificate for that DNS name
- Either DNS SRV records or well-known files
Check that your dendrite instance is running. Otherwise this is most likely due to a reverse proxy misconfiguration.
It should do, although we are aware of some minor issues:
- Element Android: registration does not work, but logging in with an existing account does
- Hydrogen: occasionally sync can fail due to gaps in the
since
parameter, but clearing the cache fixes this
Use dendrite.matrix.org which we officially support.
Yes
Yes, to enable them msc2836 would need to be added to mscs configuration in order to support Threading. Other MSCs are not currently supported.
mscs:
mscs:
- msc2836
Please note that MSCs should be considered experimental and can result in significant usability issues when enabled. If you'd like more details on how MSCs are ratified or the current status of MSCs, please see the Matrix specification documentation on the subject.
Yes, we have experimental support for push notifications. Configure them in the usual way in your Matrix client.
Possibly - Dendrite does have some application service support but it is not well tested. Please let us know by raising a GitHub issue if you try it and run into problems.
Bridges known to work (as of v0.5.1):
Remember to add the config file(s) to the app_service_api
section of the config file.
Yes, you can do this by disabling federation - set disable_federation
to true
in the global
section of the Dendrite configuration file.
This can be done by performing a room upgrade. Use the command /upgraderoom <version>
in Element to do this.
Use the admin endpoint resetpassword
Please use PostgreSQL wherever possible, especially if you are planning to run a homeserver that caters to more than a couple of users.
The list of files that need to be stored is:
- matrix-key.pem
- dendrite.yaml
- the postgres or sqlite DB
- the jetstream directory
- the media store
- the search index (although this can be regenerated)
Note that this list may change / be out of date. We don't officially maintain instructions for migrations like this.
This might be what you want: matrix-media-repo We don't officially support this or any other dedicated media storage solutions.
Run a newer docker image. We don't officially support deployments other than Docker. Most of the time you should be able to just
- stop
- replace binary
- start
Generally speaking, you should expect to see some CPU spikes, particularly if you are joining or participating in large rooms. However, constant/sustained high CPU usage is not expected - if you are experiencing that, please join #dendrite-dev:matrix.org
and let us know what you were doing when the
CPU usage shot up, or file a GitHub issue. If you can take a CPU profile then that would
be a huge help too, as that will help us to understand where the CPU time is going.
As above with CPU usage, some memory spikes are expected if Dendrite is doing particularly heavy work
at a given instant. However, if it is using more RAM than you expect for a long time, that's probably
not expected. Join #dendrite-dev:matrix.org
and let us know what you were doing when the memory usage
ballooned, or file a GitHub issue if you can. If you can take a memory profile then that
would be a huge help too, as that will help us to understand where the memory usage is happening.
No, if you already have a proper certificate from some provider, like Let's Encrypt, and use that on your reverse proxy, and the reverse proxy does TLS termination, then you’re good and can use HTTP to the dendrite process.
You may need to revisit the connection limit of your PostgreSQL server and/or make changes to the max_connections
lines in your Dendrite configuration. Be aware that each Dendrite component opens its own database connections and has its own connection limit, even in monolith mode!
There is likely an issue with your STUN/TURN configuration on the server. If you believe your configuration to be correct, please see the troubleshooting for troubleshooting recommendations.
Phone-home statistics contain your server's domain name, some configuration information about your deployment and aggregated information about active users on your deployment. They are sent to the endpoint URL configured in your Dendrite configuration file only. The following is an example of the data that is sent:
{
"cpu_average": 0,
"daily_active_users": 97,
"daily_e2ee_messages": 0,
"daily_messages": 0,
"daily_sent_e2ee_messages": 0,
"daily_sent_messages": 0,
"daily_user_type_bridged": 2,
"daily_user_type_native": 97,
"database_engine": "Postgres",
"database_server_version": "11.14 (Debian 11.14-0+deb10u1)",
"federation_disabled": false,
"go_arch": "amd64",
"go_os": "linux",
"go_version": "go1.16.13",
"homeserver": "my.domain.com",
"log_level": "trace",
"memory_rss": 93452,
"monolith": true,
"monthly_active_users": 97,
"nats_embedded": true,
"nats_in_memory": true,
"num_cpu": 8,
"num_go_routine": 203,
"r30v2_users_all": 0,
"r30v2_users_android": 0,
"r30v2_users_electron": 0,
"r30v2_users_ios": 0,
"r30v2_users_web": 0,
"timestamp": 1651741851,
"total_nonbridged_users": 97,
"total_room_count": 0,
"total_users": 99,
"uptime_seconds": 30,
"version": "0.8.2"
}