# Matrix synapse doesn't work after last update

**URL:** <https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097>\
**Category:** Hardware Owners Support\
**Created:** [May 21, 2022, 2:45pm UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097 "2022-05-21T14:45:36Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnny](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/j/ecb155/32.png) [@johnny](https://discuss.freedombox.org/u/johnny)\
**Post date:** [May 21, 2022, 2:45pm UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097/1 "2022-05-21T14:45:36Z")

</div>

- FreedomBox is plugged into a router at home
- Bought in march 2021
- Running Debian GNU/Linux 11 (bullseye) and FreedomBox version 22.11

## Diagnostic Results

### App: Matrix Synapse

| Test | Result |
| --- | --- |
| Package matrix-synapse is the latest version (1.57.1-1~bpo11+1) | passed |
| Package matrix-synapse-ldap3 is the latest version (0.1.4+git20201015+a3c7a9f-1) | passed |
| Port matrix-synapse-plinth (8448/tcp) available for internal networks | passed |
| Port matrix-synapse-plinth (8448/tcp) available for external networks | passed |
| Access URL [https://127.0.0.1/\_matrix/client/versions](https://127.0.0.1/_matrix/client/versions) on tcp4 | failed |
| Access URL https://[::1]/\_matrix/client/versions on tcp6 | failed |
| Access URL [https://192.168.0.11/\_matrix/client/versions](https://192.168.0.11/_matrix/client/versions) on tcp4 | failed |
| Access URL https://[2a01:288:11f:f300:a:4ff:fe83:360]/\_matrix/client/versions on tcp6 | failed |
| Access URL https://[fe80:🅰4ff:fe83:360%eth0]/\_matrix/client/versions on tcp6 | failed |
| Access URL [https://10.84.0.1/\_matrix/client/versions](https://10.84.0.1/_matrix/client/versions) on tcp4 | failed |
| Access URL https://[fe80::15a8:a991:b5:c672%wg0]/\_matrix/client/versions on tcp6 | failed |
| Access URL [https://localhost/\_matrix/client/versions](https://localhost/_matrix/client/versions) on tcp4 | failed |
| Access URL [https://localhost/\_matrix/client/versions](https://localhost/_matrix/client/versions) on tcp6 | failed |
| Access URL [https://freedombox/\_matrix/client/versions](https://freedombox/_matrix/client/versions) on tcp4 | failed |
| Service matrix-synapse is running | failed |
| Listening on tcp4 port 8008 | failed |
| Listening on tcp4 port 8448 | failed |

---

<div class="post-metadata">

**Author:** ![neil](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/n/839c29/32.png) [@neil](https://discuss.freedombox.org/u/neil)\
**Post date:** [May 23, 2022, 3:09pm UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097/2 "2022-05-23T15:09:12Z")

</div>

I did a fresh install and it looks like Coturn was removed, maybe that’s causing your errors?

I can get chat messages working with Element, but voice calls do not connect, again probably due to missing Coturn.

Does anyone know if Coturn will bevadded in again, or can it be manually installed?

---

<div class="post-metadata">

**Author:** ![johnny](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/j/ecb155/32.png) [@johnny](https://discuss.freedombox.org/u/johnny)\
**Post date:** [May 23, 2022, 5:45pm UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097/3 "2022-05-23T17:45:55Z")

</div>

No, Coturn is not the problem in my case. I have it installed and it’s working. Also, matrix can run without coturn.

---

<div class="post-metadata">

**Author:** ![johnny](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/j/ecb155/32.png) [@johnny](https://discuss.freedombox.org/u/johnny)\
**Post date:** [May 25, 2022, 8:18pm UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097/4 "2022-05-25T20:18:01Z")

</div>

Matrix was the only application I use, and now because of another shitty update is the only application that doesn’t work. I have no idea what is wrong this time, but I can’t turn it on in any way. The problem with sure is not from me because I have not changed anything since it worked. My patience with Freedombox has long been exhausted to continue to deal with it, let alone reinstall it again. I don’t hope for adequate support anymore. Thinking about how long I lost to solve problems … This is not freedom at all. I will wait a little longer, then I take my freedom and the box goes to the bin.

---

<div class="post-metadata">

**Author:** ![neil](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/n/839c29/32.png) [@neil](https://discuss.freedombox.org/u/neil)\
**Post date:** [May 26, 2022, 8:54am UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097/5 "2022-05-26T08:54:23Z")

</div>

I agree with your sentiments. I’ve spent many, many hours tinkering with freedombox for it to be all for nothing when an update blows the system to pieces.

Are there no tests before they are released?

I appreciate freedombox is free, but there seems to be very little engagement from freedombox towards the users who are using and testing their product.

---

<div class="post-metadata">

**Author:** ![nbenedek](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/nbenedek/32/1220_2.png) [@nbenedek](https://discuss.freedombox.org/u/nbenedek)\
**Post date:** [May 26, 2022, 9:03pm UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097/6 "2022-05-26T21:03:46Z")

</div>

Sorry to hear your frustration with Matrix. Can you provide us with the logs of your server? You can do that by opening **Cockpit** and in **Logs** menu searching for “matrix”.

Alternatively, you can also share with us the most recent content of /var/log/matrix-synapse/homeserver.log, removing any data that might be sensitive.

It would also be very useful to run `sudo systemctl status matrix-synapse` in the terminal of your FreedomBox and show us the output.

---

<div class="post-metadata">

**Author:** ![jvalleroy](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/jvalleroy/32/331_2.png) [@jvalleroy](https://discuss.freedombox.org/u/jvalleroy)\
**Post date:** [May 27, 2022, 1:34pm UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097/7 "2022-05-27T13:34:43Z")

</div>

> [@neil](#):
>
> I agree with your sentiments. I’ve spent many, many hours tinkering with freedombox for it to be all for nothing when an update blows the system to pieces.
> 
> Are there no tests before they are released?

The FreedomBox team only maintains and releases the `freedombox` package. We don’t control the many other packages from Debian that make up the system.

The only recent change related to Matrix Synapse is that in FreedomBox 22.11, we changed the apt configuration so that new dependencies for `matrix-synapse` will be installed from bullseye-backports. This is required for the latest `matrix-synapse` package to be installable on bullseye.

Normally, packages in Debian stable are very “stable”, meaning that there are very few updates except for security fixes. However, the `matrix-synapse` package is only in stable backports, not in stable. This is because it needs to be updated often to keep up with the rest of the Matrix network, and they cannot provide long-term support to older versions just yet.

---

<div class="post-metadata">

**Author:** ![johnny](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/j/ecb155/32.png) [@johnny](https://discuss.freedombox.org/u/johnny)\
**Post date:** [June 1, 2022, 9:07am UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097/10 "2022-06-01T09:07:05Z")

</div>

It is no longer necessary. I reinstalled it once again (I lost the count already). This practice reminds me of Windows XP you need to force restart it and reinstall it regularly. I hope this time it lasts longer than the previous one. I wonder if I should ban the updates.

---

<div class="post-metadata">

**Author:** ![johnny](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/j/ecb155/32.png) [@johnny](https://discuss.freedombox.org/u/johnny)\
**Post date:** [June 27, 2022, 9:09am UTC](https://discuss.freedombox.org/t/matrix-synapse-doesnt-work-after-last-update/2097/14 "2022-06-27T09:09:57Z")

</div>

Matrix stopped working again after the update to 22.14  
This fix resolved the problem:

[![Sunil Mohan Adapa](https://discuss.freedombox.org/uploads/default/original/1X/846d8cbdf086a4638df4e48a7ee26605f4253746.png) ](https://salsa.debian.org/sunilmohan)

[Sunil Mohan Adapa](https://salsa.debian.org/sunilmohan) [@sunilmohan](https://salsa.debian.org/sunilmohan) · [3 days ago](https://salsa.debian.org/freedombox-team/freedombox/-/issues/2220#note_314332)

```auto
<sunilmohan> emorrp1: So, this is an upstream issue?
<emorrp1> yes and no, yes upstream has merged a code change in develop that will incidentally fix it, but no it's a packaging upload that caused the problem to start occurring yesterday
<emorrp1> https://github.com/matrix-org/synapse/commit/f30bcbd84a651de59777b2a749850f6ca56ce3f0
<emorrp1> Copying details from other channel:
<emorrp1> Error: Synapse 1.57.1 needs matrix-common~=1.1.0, but got matrix-common==1.2.1
<emorrp1> Fix: `sudo sed -i '/common/s/~=/>=/' /usr/lib/python3/dist-packages/matrix_synapse-1.57.1.dist-info/METADATA`

```
