Yes 
Omg, thank you for posting this! I was going crazy trying to figure this out! Haven’t seen the error since editing the file. 
Hi,
This is just FYI.
I updated Matrix from 1.90.2 to 1.91.2. It updated fine it seems, but got the following messages that caught my attention.
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
setuptools-rust 1.7.0 requires setuptools>=62.4, but you have setuptools 60.8.2 which is incompatible.
No solution from me here, but a warning : do not try to fix it manually via pip or you’ll face something beautiful : Failed to read info for ****** : Invalid version: '*.*.*~ynh*'
I’ve had that error message a number of times. Each time I’ve just run the following command and it seems to fix it. I’m not sure if it’s likely to cause the problem mentioned in the previous post:
pip install pip --upgrade && pip install pyopenssl --upgrade && pip install setuptools --upgrade && pip install setuptools-rust --upgrade
Hello,
I have a synapse server under Yunohost running for years already without problem.
Recently, for some month I think, the video calls from Europe to East Asia are not working well anymore. We can’t see and hear properly our Asian correspondents. The image often freeze and sound is cut too much to allow a normal conversation.
Video calls through my Synapse server were great until recently (2-4 months I guess).
Coturn server is properly working.
Our european internet connection and their asian connection is good (>300Mbit/s).
My Yunohost server is at home under a good fiber connection.
We made test with other video call system, for instance call with Signal, and call quality is very good.
I have two questions:
(1) Is there any change in the default config of Synapse or coturn (in Yunohost) made recently that may have affected the quality of our video call?
(2) How should I proceed to investigate more thoroughly?
Thanks in advance for your suggestions 
Hello,
Maybe related to Improve turn server config and securize with tls/dtls by Josue-T · Pull Request #222 · YunoHost-Apps/synapse_ynh · GitHub
Note you can disable DTLS (which could be the cause of the issue) from the config panel, cf synapse_ynh/config_panel.toml at b97297dc1d97039ba62f7762eac739c54f527897 · YunoHost-Apps/synapse_ynh · GitHub
Thanks @Josue for pointing me this information. TLS/DTLS on Audio/Video call was indeed enabled on my server.
I just disabled it and I will make some new test.
You were correct @Josue , this option to increase security of turn server with TLS/DTLS caused lags in video calls in my case.
When I remove this option, video calls are fluid as they were before.
Maybe my small server doesn’t have the capacity to handle this additional layer of security.
But to be correct, I think in my case there is no problem with Let’s Encrypt certificate as calls are correctly established. The lag cause calls to be impossible, but the connexion between correspondents happens without error.
Thanks again for your support and advice
OMG, I had been having crazy levels of problems with video calls and turning this option off made them all go away instantly.
Before, it would usually take about 4-6 time calling before we got a connection where both parties could see and hear each other. Since turning this setting off, every single call has connected correctly straight away.
Beforehand, the audio and video lagged. Now it’s near instant.
Beforehand the video would stutter, drop below 1fps and compress like crazy. Now it’s clear and smooth.
The difference is like night and day.
So, is there any problem solving I could help with to get both the security of TLS/DTLS and the call connection/quality of having it off? Happy to send logs or test patches. Oh, and yes, I’m using Let’s Encrypt certs.
After the migration to Yunohost 12 and Synapse 1.121, do you know if Sliding Sync is operational on our Synapse server?
I may have understood it is now included in latest Synapse versions (no need to add additional proxy), but I can connect to my server with Element X (client using this Sliding Sync function).
But I am not sure to fully catch the consequences on our server (I read clients are faster and calls even more reliable).
Hello 
,
I have seen the merge of Testing into Master 4 days ago.
And also the merge of Matrix v2 implementation into Testing 4 days ago.
Does the current proposed update of Synapse into Yunohost includes Matrix v2 implementation?
If yes, with these changes (sliding sync and Element call), does the “old” Android Element application still works or do we have to use only the new Element X?
For nos it’s only the testing. But I really recommend to test this testing 
Element and element X is expectation to work.
The only restrictions is for calls both are not compatible, so from an element android client you won’t be able to call a element X client. Elements web support both (if enabled from the settings) so from elements web you can call a element X or a legacy element android client.
Note also that this merge (Matrixv2) don’t Include MAS which require some big work on the core before to be merged.
Thanks @Josue for these explanations 
I have found the setting on Element web/desktop, currently at Parameter / Experimental / Audio & Video / then I can activate Element call video call
It is strange to have an evolution of the Element call system with no fallback possible to allow an old Android Element app to communicate with a new Android Element X app.
I’ll have to move all users to the new Android Element X app to benefit from these evolutions.
Hello,
I am wondering what is the proper way to disable federation on my Synapse server?
I want users registered on my server to be able to communicate with other users of my server (message and calls) but to prevent users joining rooms in other synapse servers.
you could either misconfigure the federation for it not to work properly 
Federation - Synapse
or use Configuration Manual - Synapse
Or contribute to or wait for this: Rework homeserver.yaml , config_panel and provide multiple config templates by Gredin67 · Pull Request #590 · YunoHost-Apps/synapse_ynh · GitHub
I cannot install this app (december 2025).
https://paste.yunohost.org/raw/ohusefokut
2025-12-23 09:54:38,665: WARNING - raise RuntimeError("Synapse requires PostgreSQL 14 or above.")
2025-12-23 09:54:38,665: WARNING - RuntimeError: Synapse requires PostgreSQL 14 or above.
2025-12-23 09:54:39,258: ERROR - Unable to install synapse: An error occurred inside the app installation script
I have no pending updates for my instance. I did find that same have had a similar issue with Matrix related app: https://github.com/element-hq/synapse/issues/18086
I am hesitant to try the work around given there because I do not want to break my server in the process for future yunohost updates. Is there a specific workaround I need to do on my set-up?
I suspect that your migration from YNH11 to YNH12 partially failed, because it should have migrated to postgresql version 14. Do you still have the logs of the migration ?
Hi, thanks for answering.
I don’t have the logs anymore it seems, sorry.
In the end I did move the cluster from 13 to 15 on my set-up (according to what was said here: Synapse does not start anymore - PostgreSQL version 15 is not recognized · Issue #18086 · element-hq/synapse · GitHub ).
The installation works now, except calls (but have never been able to get that to work with coturn so not to surprised there.) I had to move my setup quickly because I was using conduit until today and some critical issue was reported. Thought it might be safer to use the more established app for now.
Enjoy the holidays!
Hello dear @Josue 
,
Would you mind reminding me/us what are the appropriate port to open in our server for (1) synapse to properly work with federation, and (2) for Element call to work.
I also would like to know if coturn is still needed when using Element call. If it is not needed, do I need to remove it ?
Thanks in advance for your information and advices 