Solved Matrix.org Rooms from my Server?
-
@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?
-
Yeah, I think this can be avoided by having some .well-known UI in cloudron. Currently, it seems a bit complicated to explain (this is actually in our docs, but I guess it's not easy to follow)
-
@girish I sent you an email with my domain!
-
@girish said in Matrix.org Rooms from my Server?:
@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?
I gave 3GB to Riot and 3GB to Matrix and logout and login but I still have this error.
-
@JOduMonT Are you able to join other groups?
-
@toto-s Sent you a mail from support but the federation is not setup for your domain. Can you review the post installation again at https://cloudron.io/documentation/apps/synapse/#post-installation ? Let me know if something is not clear and I can clarify or fixup the docs. The main things is that the below command should work as a first step. For you domain, it doesn't work because there is nothing installed there.
~$ curl https://domain.com/.well-known/matrix/server curl: (6) Could not resolve host: domain.com -
@girish sadly no I still have this error when I try to explore group
Riot failed to get the public room list. No key for mydomain.tld with ids in ['ed25519:a_tHTB'] (min_validity 1592294601615)and when I try to join I still have the same error too
so I don't think it is related to the memory
BTW: I forgot to mention, Cloudron is behind a firewall in a DMZ zone but my provider seams enjoying blocking port,
which port matrix/riot need ? -
the default federation port is 8448, but on cloudron it is different, you can try 8008 and check if that's working
-
@JOduMonT said in Matrix.org Rooms from my Server?:
Riot failed to get the public room list. No key for mydomain.tld with ids in ['ed25519:a_tHTB'] (min_validity 1592294601615)
This is most likely to do with federation not setup properly. Can you send me a mail to support@cloudron.io with your domain name and I can tell you what is going wrong.
-
@msbt said in Matrix.org Rooms from my Server?:
the default federation port is 8448, but on cloudron it is different, you can try 8008 and check if that's working
We switched the federation port to 443. (So it's both the client port and the federation port)
-
ah thanks @girish, was wondering why none of the others were exposed, that explains it
-
@girish said in Matrix.org Rooms from my Server?:
This is most likely to do with federation not setup properly. Can you send me a mail to support@cloudron.io with your domain name and I can tell you what is going wrong.
thank for you help and your explanation
so basically I have this issue because the .well-known dir is not present, but also because my root domain (https://mydomain.tld) don't point to my cloudflare server
-
thank again @girish
In my project Gatsby I created the file static/.well-known/matrix/server
as mentioned in the doc
and now I could Explore rooms on matrix.org even if riot have only 256mb of RAM and matrix 512mb -
I followed the post-install instructions, managed to list rooms,but can't join them :
this is my federation tester results : https://federationtester.matrix.org/#rmendes.net
Not sure what else I can do
This is what I see when trying to join a public room :
I have no idea what changed but I joined Cloudron room from searching it on the matrix server public rooms, also managed to join another linux room, but If i try to join the main matrix room on the matrix server I get this repeatedly :
If I try again, it keeps looping in this state :
I'm not sure it's related but on the Element log I can see this error, it's the only error that keeps repeating : Oct 08 16:01:27 [2020-10-08T14:01:27.135Z] "GET /config.chat.rmendes.net.json?cachebuster=1602165687021" Error (404): "Not found"
As if instead of looking for the config file where it is, it is pointing to a non existing place where there is obviously no config file ?
-
I'm confused even more now, I can join some rooms but not others, and I don't see any logical reason that some room on the same server (official matrix) can be joined and others not...
You don't see it on this screenshot but server connection seems to be unstable, sometimes I can display the chat of a joined remote room, sometimes I can display the user list but not the chat, in between I see a red message saying server connection has been lost..
it seems the lost connection is the remote one, nothing to do between cloudron matrix/element apps... -
I have spent a few hours trying to prove that there is a correlation between trying to join rooms and this error : Oct 08 17:53:46 [2020-10-08T15:53:46.844Z] "GET /config.chat.rmendes.net.json?cachebuster=1602172426790" Error (404): "Not found"
this config file is at the root of the Element app container, why is it run as if it was a subdomain location ?And I'm pretty sure with the timestamps that these errors are related to trying to join rooms.
The question is, why are some rooms join-able and not others ?
if you append this : #/room/#freenode_#indieweb:matrix.org to your Element app URL
you should not be able to join this room and you should see the error above in your error log.the only log item I'm seeing on matrix app side that raise question is :
Oct 08 15:22:37 /app/pkg/start.sh: line 82: 101 Killed gosu cloudron:cloudron python3 -m synapse.app.homeserver --config-path /app/data/configs/homeserver.yaml
-
You need quite a lot of RAM to join the main matrix channel, since there are a few 1000 users inside. I think that requires at least 2GB. Could that be it?
-
@msbt I have upped the memory to 2GB and since, this error : Oct 08 15:22:37 /app/pkg/start.sh: line 82: 101 Killed gosu cloudron:cloudron python3 -m synapse.app.homeserver --config-path /app/data/configs/homeserver.yaml
is completely gone.
But I'm still stuck at the same : even joining little rooms does not work, or works "randomly" ?
