Matrix.org Rooms from my Server?
-
Getting an odd message (example):
Riot failed to get the public room list. No key for <mydomainname>.net with ids in ['ed25519:a_DXwR'] (min_validity 1590775063617)
...when I try to browse rooms on matrix.org's servers from my Cloudron installation?
-
Anyone have any ideas? I guess I could try reinstalling??
-
Are you using your own matrix server or just the riot installation? One thing that happens often when listing/joining bigger matrix channels: not enough ram on your machine. bigger channels requires 2GB an more RAM to join.
-
@doodlemania2 Can you tell me your setup a bit more. Is it matrix+synapse? I will try to reproduce this locally.
Another user reported this is https://forum.cloudron.io/topic/2608/matrix-federation
-
@girish I see the same problem here!
I use the server, Riot for Linux Desktop and RiotX on my Galaxy S20.
The server has 4096 MB Ram available
-
Hey @girish - yeah, it's matrix+synapse ... trying to search rooms on matrix.org. My local rooms seem okay.
-
@doodlemania2 @toto-s Trying to reproduce it locally
-
On my install, I got a different error:
-
I cleared the browser cache and the listing started working.
But joining a room fails:
-
As @msbt said, joining smaller rooms (~1k participants) works. If I join larger rooms, the server runs out of memory and I get the CORS error in the UI.
17:05:07 - 2020-06-03 00:05:07,447 - synapse.http.matrixfederationclient - 165 - INFO - POST-109 - {PUT-O-160} [matrix.org] Completed: 200 OK 17:05:13 - /app/pkg/start.sh: line 80: 95 KilledI bumped up the app's RAM to 2GB and I can connect to all rooms.
-
@doodlemania2 @toto-s Did you change the location/domain of your matrix install by any chance? If so, I think I have a guess as to what is causing the problem. Do you have a file named
/app/data/configs/signing.key?
-
Yes, the signing.key file exists!
-
Mmm, I am out of ideas here. Out of curiosity, have you guys already tried re-installing? I can't find any related issue on matrix issue tracker either.
Can you try re-installing and try to reproduce this? If it's reproducible, can you give me access (support -> enable remote support) and send us a mail at support@cloudron with the domain name. Thanks!
-
Will do so today to see if I can make it go!
-
Yeah, reinstallation gave the same error Riot failed to get the public room list. No key for thedoodleproject.net with ids in ['ed25519:a_HtQW'] (min_validity 1591297300437)...sadness. Will email ya.
-
got the same error when I try to search in Matrix
also if I try to join public group such as: #techlore:matrix.org
https://riot.im/app/#/room/#techlore:matrix.orgthe result is:
-
@JOduMonT The M_UNKNOWN issue is related to memory limit. When you join large matrix groups like techlore, you have to bump the memory limit to atleast 2-3GB. Can you try joining a smaller group as well?
-
@doodlemania2 I replied to you from support couple of days ago, I need access to your server to debug further
-
@doodlemania2 Thanks for giving access to your server. The issue was that federation setup was incorrect:
- @doodlemania2 had setup the well-known correctly
- But there was no app installed on
domain.com. Without this, Cloudron will not respond todomain.comand thus the well-known setup won't work. - To fix: I installed a dummy app on
domain.com. I then checked in https://federationtester.matrix.org/ that the setup was correct. - I waited for couple of hours since matrix.org seems to cache the DNS a bit and it had cached the previous NXDOMAIN. After that it works.
@toto-s Can you check with federation tester?
It's working now:
-
Well that's outstanding! I guess suggest would be to add that requirement to the instructions for Matrix app?
