matrix explore room issues

[nebulon]

are there any errors on the app side when it responds with 502 status code there?

[girish]

I have noticed that sometimes you have to give a lot more memory to synapse app to make the Explore work.

[ApplegateR]

@girish then why I don't get any alert memory or graph is very low show nothing reach up

[girish]

@ApplegateR yeah, I think the synapse server (it's based on python) just fails when it is low on memory but doesn't actually crash. We get a notification/callback from docker only when something runs out of memory and crashes.

[ApplegateR]

@girish okay i puah it up tp 8GB same result...

[ApplegateR]

This post is deleted!

[ApplegateR]

@ApplegateR I gave up... would you possible help me thru remote support see if we could get my matrix and element get work?

[nebulon]

@ApplegateR yes, please enable it and send us a mail to support@cloudron.io ideally with login credentials for the user you are experiencing this if this is not Cloudron user management.

[girish]

@ApplegateR The issue here was that the port number was not explicitly specified in Matrix Server Location. It has to be set explicitly as matrix.domain.com:443. This is because 443 is not the default matrix server port.

Unless that is set up, federation won't work. Unless federation works, it cannot explore rooms of another server.

I fixed up the port number as suggested above and now I can explore rooms.

[ApplegateR]

@girish let party!!! Thank you so much!

[ApplegateR]

@ApplegateR It is working now