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!

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

@andreasdueren @girish confirmed a couple days ago that this was coming in 7.4. It was originally scheduled for 7.3, but didn't make it. I hope it does as it's pretty critical for anyone wanting to use a turnserver in academic or corporate contexts.

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

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

@girish yeah, similarly there are other non ActivityPub federated apps too like Diaspora etc.

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.