@nebulon said in Questions to Matrix: There is already a thread for file uploads at https://forum.cloudron.io/topic/11032/unable-to-increase-upload-size-above-2gb-matrix/21 Thank you, then we I have to wait for an update because I use only E2E rooms

News: https://element.io/blog/2024-is-about-being-in-your-element/

Found a solution in the old bug report, only issue is that it doesn't work in e2e rooms here is the solution https://github.com/matrix-org/synapse/issues/12023#issuecomment-1044337550 That seemed to work because when uploading to an unencrypted room the upload does start, but when uploading in a e2e room it just failed (doesn't even start uploading) Does anyone have an idea on how we can make this work in e2e rooms as well? btw for anyone trying to apply it do the following 1, go to the terminal. 2, click postgress then type psql and press enter. 3, paste in the following to change media_length from integer to bigint ALTER TABLE local_media_repository ALTER COLUMN media_length TYPE bigint; you can use the following to check if the change was applied SELECT data_type FROM information_schema.columns WHERE table_name = 'local_media_repository' AND column_name = 'media_length';

@girish said in Expand Matrix app features: @Sam_uk are you looking for a specific connector? I think adding all of them is not going to be "sustainable". It's just going to break with all releases and dependencies. For me it's really only the WhatsApp bridge. It's by far the most popular chat service, requires no API access with a complex registration process or high fees and is fairly easy to use. I am basically currently running a separate server with yunohost just so I can use the bridge and would love to change that.

Just an small update, moving my cloudron from VPS to my Intel NUC went very smooth, thank you @girish and @nebulon for your great work

I understand the rationale, thanks. But the current decision have the following disadvantages, from what I see: it ignores my settings - I'm asked at which domain I would like Synapse to be installed and then I get it on my root domain, regardless my input - I've spend quite a time to figure that out you are dependant on the ever growing list of new domains What we discuss calls delegation in Synapse terminology. It feels like extra feature for me and I really can't see reason to keep in on Cloudron, at least not with current setup. Just in case - I know how to make things working for me, so I would be just fine with things as is, but I believe it's wrong from the logical perspective.

@lukas it's not very active. We mostly stick to the forum since this is publicly indexable.

@girish Oops! My mistake!

Hi, in logs I can find nothing, federation is off. I had a look at the website and add to homeserver.yaml: caches: global_factor: 2.0 per_cache_factors: get_users_who_share_room_with_user: 2.0 sync_response_cache_duration: 4m cache_autotuning: max_cache_memory_usage: 4096M target_cache_memory_usage: 1516M min_cache_ttl: 30m Then I deleted approx. 400 unused rooms, but nothing helps. I guess it is related to presence. There are 186 users, not too much. Maybe we move Matrix/Element to separate hardware. greetings dirk

In this case I meant https://en.wikipedia.org/wiki/Interactive_Connectivity_Establishment

As a side note: Cloudron's SSO completely ignores whitelabeling settings.

ok, got it fixed... Cloudron told me to: For federation to work, the delegation URI https://domain.com/.well-known/matrix/server must be configured. See the docs on how to do this. but to get it working, I had to add: matrix.domain.com:443 Topic can be marked as solved

I think we just have to start following different repo, that's the main change for now.

Have you followed https://docs.cloudron.io/apps/synapse/#post-installation ?

@humptydumpty oh very nice, thank you!

I clarified in https://docs.cloudron.io/apps/synapse/#admin that there is no admin UI

@girish got it, thanks! As for Jitsi - my showstopper issue is not yet resolved =( https://forum.cloudron.io/topic/7473/no-sound-in-jitsi/42

@girish Yep, that worked perfectly. Thanks, Girish!

@nichu42 said in Run s3_media_upload script: Open your script, then select Edit > EOL Conversion > Unix (LF). Save, upload and try again. It actually works. Thank you! Strangely enough, the script was originally created using the Cloudron file manager.

I have pushed out a new package fixing the typo...