@atrilahiji @ericdrgn I started working on this yesterday and have similar questions. In my case I just opened 3478 TCP & UDP on inbound traffic (on a VPC in AWS) and two users on the Cloudron could then make video calls - on Nextcloud Talk and Kopano Meet. Monitoring the STUN/TURN logs going via the Services page, I could see a few 401s thrown before connection, but I'm not sure how to read what is happenining at this stage. Do I need to open up 5349, as well, as indicated in the post above?

Yes, they’re all separate servers. But they each need their own port into the synapse server. My suggestion is to leave some extra ports open instead of trying to assemble an app with all/most/some of the appservices. This way we can integrate appservices today rather than dreaming about 20 maintained ones sometime in the future, if ever. (Wouldn’t blame anyone for not trying to maintain 20 wildly different appservices since they’re all very fluid pieces of software)

@yusf said in Google suspended Element in Play Store: Calls and texts are literally pushed though. For the 10% of important people still using them. 90% of notifications to me are unnecessary, no matter how much I try to whack them with settings.

@girish Of course, makes sense now. Should be fairly easy for everyone moving forward.

@msbt hmm you are right and I was wrong! I'll test if it works and report back EDIT: Okay it works but only for new accounts (at first login with LDAP or local accounts). The part in my homeserver.yaml looks like this: auto_join_rooms: - '#discuss:yourdomain.com' - '#feedback:yourdomain.com' - '#help:yourdomain.com' - '#info:yourdomain.com'

@nebulon said in Question regarding setting up sydent as an identity server: . Ok, yes I haven't installed it via cloudron. Thank you for the reply!

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

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