Matrix/Riot

[yusf]

@msbt said in Matrix/Riot:

I'm guessing it is because of new keys and everything, haven't tried to re-use any of the existing ones.

Might very well be, yes. I'm going to try and migrate the keys too. The migration is hard to dry run though

[msbt]

if you want to make sure this works, you could try with a test-instance, after that a clone and then the real thing good luck either way!

[yusf]

I'm transitioning my external reverse-proxy-and-well-known solution to the Cloudron solution. Is there any way I can configure Riot to have https://domain.tld as base_url while still having the Synapse server at https://matrix.domain.tld? This way I would be able keep Riot user sessions across migration.

[girish]

@yusf That should not be a problem. Riot can be installed on the main domain as well. Just make sure the .well-known is setup on the server.

[yusf]

@girish Sorry, I meant doing so while keeping Riot at a subdomain too. I guess not?

[girish]

@yusf Yeah, I think not

[jegillikin]

FWIW, I just installed all of this and tested it. Works great, instructions are clear. The yaml edits referenced by @msbt were quite helpful on the external-registration side.

Look forward to the eventual Jitsi package.

[yusf]

@girish What if I edited the Cloudron reverse proxy settings directly?

[girish]

@yusf reverse proxy configs will get overwritten during updates. I think https://cloudron.io/documentation/apps/#well-known-uris should help setup well knowns the way you want them, no?

[yusf]

@girish Well-known is in place for Synapse already, but it seems that well-known configurations aren't enough to enable entering domain.tld as homeserver in Riot sign-in when the server is at matrix.domain.tld.

What seems to be needed is the ability to forward the whole /_matrix path at domain.tld to Synapse.

In nginx terms I belive that would look something like this:

server {
  listen         443;
  server_name    domain.tld;

 location /_matrix {
    proxy_pass https://matrix.domain.tld;
 }
}

[ApplegateR]

@girish I really hope this is possible add this in Wishlist for Matrix User and room manageable so spamming prevent and keep my chat server clean

[girish]

@ApplegateR said in Matrix/Riot:

@girish I really hope this is possible add this in Wishlist for Matrix User and room manageable so spamming prevent and keep my chat server clean

What are you referring to ? Did you maybe reply in the wrong thread?

[ApplegateR]

@girish have a admin access from web. So that way I can manage user or room.

[msbt]

@ApplegateR you can just grab the synapse admin package from here and put it inside a Surfer/LAMP app, it's just static files. You can login with your admin user and manage users and channels.

[humptydumpty]

@ApplegateR I just tried what @msbt mentioned and it works great. One error I ran into was that after uploading the files to a root surfer app and trying to log in, it spit out a "session expired" error. It turned out the account I was using wasn't an admin. To make a user an admin, refer to the doc here.

Basically, in Cloudron --> app settings page --> web terminal, and enter this code.

PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} -c "UPDATE users SET admin=1 WHERE name='@user:example.com'"

The only part you need to edit is the one at the end to match your desired Matrix user:

@user:example.com

Then, you can log in and manage the Matrix server.

[ApplegateR]

@humptydumpty and @msbt thank you guy for Huge help and why this wasn't on docs if anyone really interesting to have one for matrix management

[ApplegateR]

@ApplegateR confirm it is work and thank you and I will just use surfer it better than nothing! much appericate of creator done this