@girish Yay! Thank you.
I am all new to this Linux game so I wasn't aware I could just set the environment variables like that.

For everyone else, this is what you need to do:

──────────────────────────────

Set up S3 with Synapse. See my post here: https://forum.cloudron.io/post/60415

Create a database.yaml file in /app/data/configs that contains the postgres database credentials.
You can find those in the existing homeserver.yaml file.

user: xxx password: xxx database: xxx host: postgresql Create a script (e.g., s3cleanup.sh) with the following contents: #!/bin/bash cd /app/data/configs export AWS_ACCESS_KEY_ID=[your S3 compatible access key] export AWS_SECRET_ACCESS_KEY=[your s3 compatible secret access key] /app/code/env/bin/s3_media_upload update /app/data/data/media_store 1m /app/code/env/bin/s3_media_upload upload --delete --endpoint-url https://yours3storageendpoint.com /app/data/data/media_store [your s3_bucket_name] Run the s3cleanup.sh script.
It will look up media that hasn't been touched for 1m (= 1 month) or whatever you set above. It needs to be an integeger value, followed by either m = month(s), d = day(s) or y = year(s).
It will create a cache.db file that refers to the media that matches your criteria.
In the second step, it will upload all files from the cache.db to your s3 storage and delete the local copies.

The output looks like this:

Syncing files that haven't been accessed since: 2022-12-25 14:59:14.674154 Synced 603 new rows 100%|████████████████████████████████████| 603/603 [00:00<00:00, 16121.24files/s] Updated 0 as deleted 100%|████████████████████████████████████| 603/603 [03:25<00:00, 2.93files/s] Uploaded 603 media out of 603 Uploaded 3203 files Uploaded 263.6M Deleted 603 media Deleted 3203 files Deleted 263.6M

Edit: Added path /app/data/configs to script to make it work as cron job.
Edit2: Added more choices for duration suffixes in 's3_media_upload update' job.

Disclaimer: This is to the best of my knowledge and understanding. It worked for me, but I accept no liability for loss of data on your server caused by my incompetence. 😉

@girish Thank you. Then it was unfortunately what I thought. I get to discuss with Element about a possible solution.

@girish said in Matrix/Synapse Admin Interface:

@atridad I don't know if it's actually that useful. It can only manage (existing) rooms and add users from what I can tell. It's not that full fledged an admin interface as I imagined. But still, if other's consider it useful, this is trivial to package.

I am running into some issues after having used this tool to set up registration tokens where even as the admin and logged in as the admin, it will not let me delete user data. Is there an easier workaround for this? Note: Not my area of expertise but I am slowly learning and ChatGPT def helps. I am even having trouble using the Surfer CLI to access this because it won't accept my username and password despite being the superadmin.

@nichu42 great, thanks! 🙏

@murgero ah yes... this does seem to be the trick.

I just found the line in the docs that says:

Step 3. Federation Federation setup is automatic. Use the Federation Tester to verify that everything is setup properly. Note you must enter the server_name (like example.com) in the form field in the website and NOT the location of your home server (despite what the form says).

@girish Thanks, I'll give it a go

@girish said in Matrix / Element First Run - Cannot login:

@LoudLemur you have to login with Cloudron username/password.

Thanks, that solved it. I think it might help if this information is included in the "First Run" section.

How can I mark this "Solved"?

@privsec yes, I've already got matrix assigned to a group, and only they can see it, but I don't even want them to be able to see it because there isn't anything they can do with it.

This got sorted out in support . It was a configuration error - Issue was that user was part of a group that was not part of the app's access list.

@subven
@girish Nope, dont use Cloud, but thx for answering, im trying fix my problem.

@ApplegateR It is working now 🙂

@girish I can confirm It is working! 🙂 thank you for doing this!

@yusf Oh I see, alright I will try to launch Maubot side by cloudron
and see where that leads me, I really need Matrix to support webhooks

@girish Sorry for my late reply (I'm new to this forum and I didn't see that default notification settings don't send an email).

Thanks a lot for adding it to the package!
I works perfectly!

@jdaviescoates in their repo they are calling it a "showcase" and also require a specific development branch of one of their dependencies. Overall the project does not look quite "ready" to me yet.

Thank you for both of your replied.
@nebulon yes, I read the doc and configured the well-known for the domain via the Cloudron interface.
It's just, maybe I miss reads, but the Step 3 confused me.

Not 100% sure but seems like synapse does not support a built-in backup and restore as per https://github.com/matrix-org/synapse/issues/2046 . So, you have to essentially migrate databases and files manually. You will find all the necessary files in your synapse and element app backups.

@girish yeah no worries, though i was just lokking for the option to enable phone number registration, and could not for the life of me find any kind of resemblance from the sample file to the actual config file, even less where i should add the needed line inside the config, same with the tls config options

@girish I wanted to see when we might expect to see this?

@girish Thanks - I checked all these and it passed all the tests.

I've setup on a new domain and its working now so I will see if I can export the messages from the broken instance to the new.

It was a weird issue for sure.

Our tests use a bunch of APIs to validate updates in case it's interesting - https://git.cloudron.io/cloudron/synapse-app/-/blob/master/test/test.js#L57

@derin would be great if you could post your final working theme here when you have it working.

@hollosch this would have to be done in the upstream project. For element web this likely is https://github.com/vector-im/element-web/#translations

@murgero I don't think it does.

@scooke : thank you
Yes, I have another app on the domain.
I pressed 'save' to re-save and re-start it.

The domain.tld/.well-known/matrix/server returns a response.

But the tester link you gave returns an error

Connection Errors Get "https://107.155.122.83:8448/_matrix/key/v2/server": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

And complains there is no SRV record.
Seems to me that the tester is not compatible with Cloudron matrix installs which are on :443

Maybe it's a DNS propagation issue as it's been changed ... but has it really? because Cloudron installs are under a wildcard in my case.

I will try again in a while in case it is a propagation issue.

But there is one change.
Previously Element said "cannot find" your server incroyable.net, and now it says "you are not allowed to view this server's rooms list" and I could successfully join your room with a direct link.

And I can find some other random servers also.

Think I can this is now working, despite tester link errors.
Many thanks for your help !

Hi @Nexxo , have you found a solution or were able to activate the IS for Matrix?

regards

@robi That doesn't do the trick unfortunately. It results in the underlying IP of the cloudron server being exposed, which undermines the purpose of the cloudflare proxying.

So i think I still need to find a way to add in our external turn server and allow it to survive a reboot.

@senthilkumaran The CORS issue is covered here - https://forum.cloudron.io/topic/5589/cors-timeout-error-when-searching-for-public-rooms . Essentially, try giving synapse a lot of memory.