@sebgg give this a read - i had the same problem and installing the element app and then deleting it might have fixed the ssl issue that might have caused the federation to fail. https://forum.cloudron.io/topic/3974/help-making-federation-work/4?_=1610652549494 BTW, make sure to install matrix first, then element.

IIRC, the fix to this was to get federation working properly. https://docs.cloudron.io/apps/synapse/#step-3-federation

This is something you have to configure in the homeserver config file. 3pid (third party ids) in matrix can be email and MSISDN (phone numbers). From what I can tell, you have to first setup a msisdn delegate and also set disable_msisdn_registration to false i guess. I haven't found any docs on how what this msisdn delegate is though.

@girish Awesome thank you it works like a charm. Marking as solved.

@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" ?

@yusf Fixed in the latest version.

And this issue seemingly tracks non-recaptcha support.

@girish So i did actually set it to zero before and commented out the nginx file path. So that killed it. IN THE PAST But setting the upload to 0MB in the config and restarted. It actually worked. Wow! Thanks for having a functioning forum and the speedy response!

Not sure if this is related but in the logs for Surfer, which I have as a redirect for the root domain, I am getting a 404 for the matrix .well-known constantly. GET /.well-known/matrix/client 404 1.083 ms - 328 Were you ever able to look into this @girish?

@nebulon Thanks. Will try it.

Rename to Element and update pushed.

That went well, I have pushed an update.

Locking this, please see other topic.

@danigl As you probably know, the port 8448 is only for server <-> server communication. What port are you using for server <-> client communication? In Cloudron package, we use the same port for server <-> server and client <-> server communication (which is port 443).

@xavierl I have pushed a new version of synapse that allows matrix to manage it's own users. If you re-install synapse, you will see this option.

@xavierl You practically can. Just grant no Cloudron users access to it while also enabling open registration in the Matrix app internal settings.

@girish I needed it to be able to properly federate with other Matrix servers. Like I said, it was pretty weird.