Matrix/Riot
-
@girish Getting an error on verifying:
$ curl https://example.com/.well-known/matrix/server
curl: (6) Could not resolve host: example.com (I used my own domain)I chowned the matrix folder and server file to be owned by yellowtent. I had to use sudo to get the mkdir command to work.
I set permissions of 0600 on the server file.
There is no app at example.com.
Matrix is installed at matrix.example.com.
Do I need to manually add a DNS entry for example.com? -
@will Only requirement is that it should be used by some app on Cloudron. You don't need to redirect it to matrix specifically.
example.com
can either be any app or it can redirect to any app. (At a technical level, all this means is that the Cloudron's reverse proxy is prepared & ready to answer requests for that domain). -
@will there is no way around this requirement. the matrix protocol requires the apex domain to serve up those documents. is your concern that the domain
example.com
can be used to host a site somewhere else? If so, all you have to do is to move the.well-known
setup to that server/new location. -
@will said in Matrix/Riot:
It would be cleaner to just have cloudron handle that for me. Small gripe, not a big deal at all.
Ah, Cloudron side limitation can definitely be fixed I agree that having to ssh and put files manually in a cryptic location is kinda crude. This will be fixed soonish but we just wanted to get the apps out for testing sooner rather than later.
-
-
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
asbase_url
while still having the Synapse server athttps://matrix.domain.tld
? This way I would be able keep Riot user sessions across migration. -
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.