Suddenly Matrix federation doesn't work anymore :(

[girish]

@luckow said in Suddenly Matrix federation doesn't work anymore :

BTW: same for the cloudron.io domain.

$ curl -L https://cloudron.io/.well-known/matrix/server
{ "m.server": "matrix.cloudron.io:443" }

-L follows redirects.

[girish]

@luckow *.example.com does not cover example.com in DNS. It only covers the subdomains . Also, you need to have an app installed on example.com or alternately add it as a redirect of an existing app.

[luckow]

@girish Ok. got it. From my side it was a misunderstanding. It's not a topic about "*.example.org is not enough" and to make federation work it needs to have an exclusive matrix-homeserver.example.org (btw: that makes no sense in my poor expertise about dns stuff). It the hint, that it needs a dns entry for example.org to get federation working. But: yes I have such DNS record.

[luckow]

I found the problem for my problem.

example.org is handled by the surfer app. I've switched to www.example.org this week and redirected example.org to www.example.org. That was the moment matrix federation stops working. Switching back to example.org solves the problem.

Maybe there is a bug in the surfer app @nebulon ?
Goal is to have www.example.org because of https://www.yes-www.org/why-use-www/

[luckow]

@girish should we add the -L option to the docs? https://docs.cloudron.io/apps/synapse/#step-23-verify-setup

[girish]

@luckow Looks like there is a bug when the bare domain is a redirect. Investigating.

[girish]

@luckow I have fixed this in https://git.cloudron.io/cloudron/box/-/commit/2f58092af2344a257a05ab31f773ebbfb558eb4f

It's a small change if you want to fix it yourself. The file is /home/yellowtent/box/src/nginxconfig.ejs. Just have to add those two lines in the commit above. Then go to Location -> Save to regenerate the nginx config. No need to restart box code.

[luckow]

@girish top!

Got 1 connection report.
Homeserver version: Synapse 1.27.0

[A Former User]

Sorry to revive this but I had a question regarding this. It seems like Element can no longer connect when I do this. Also, I noticed the same sort of setup is here for Mastodon: https://docs.cloudron.io/domains/#matrix-server-location

So is it then possible to have the same base domain for both? I want to have matrix.domain.com and social.domain.com. Just a little confused.

@girish

[nebulon]

@atrilahiji so the apps can be installed on any domain really but for the user/channel handles to work in federation, the base domain (in your example domain.com) needs to provide information where to find the backend servers. That information is stored in a well known location.

We've just added those cases in the domain configuration directly, to avoid users having to edit text files in specific URL paths, which can be error prone.