@yusf said in Changes in 1.25.0:

@girish They sre apparently changing the default to allowing custom usernames. This is terrible for me but it might also be undesired behavior within the general Cloudron experience.

localpart_template: "{{ user.preferred_username }}"

The above setting activated is responsible for retaining the previous behavior, iirc.

It seems that I've cried wolf since when setting up a new test user, no prompt was given to med when signing it in to the LDAP-enabled Matrix server with Element. Good!

@girish

thank you, this was the problem!

39122723-652e-49d3-aa17-57d5572e5290-image.png

@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

@girish Sadly that was the same problem I ran into. I will reach out to the KDE guys like you mentioned, but figured I would check here first.

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.

RSS bots typically polls every 15, 30 or 60 minutes, or daily.

Default integrations are not a good experience at all currently. I can recommend maubot for RSS integration.

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

I just searched cloudron on the public matrix server, found it, joined just fine !

@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!

@girish I’ve no idea. 😊

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?

@terrygogo Element is a frontend and Synapse is the backend. Element will follow whatever authentication mechanism you setup in Synapse.

On Cloudron, when you install synapse, there are 2 ways to set it up:

Allow users from Cloudron - With this, external registration is disabled. Just add users to Cloudron and then can login to Element.

Let the app manage users - With this ,external registration is enabled by default. If you want to disable it later, you have to comment out enable_registration in the config - https://github.com/matrix-org/synapse/blob/develop/docs/sample_config.yaml#L1046

@nebulon Thanks. Will try it.