@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

@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

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

Disclosure here - https://matrix.org/blog/2021/09/13/vulnerability-disclosure-key-sharing We pushed out update to Element already. Please update asap.

If you can get logs from the client on the remote end of the call, it will tell you what's not connecting / failing.

@cryexx I think you are in the wrong place. This forum is for Cloudron and related to the Synapse package on Cloudron. Maybe https://github.com/matrix-org/synapse is the right place for your question?

I fixed this in package 1.28.0-1

@infogulch ah thanks, i will remove it.

@nebulon Thanks for the tip. I will instruct my users to re-enable sync again on the Android app.

@scooke good idea, thanks