Closed jaywink closed 4 years ago
are you sure?
Same issue here. My cert for subdomain is correct and working properly, however the parent domain is pointing to a completely unrelated website which I don't have control over. The federation tester is complaining with same error: https://federationtester.matrix.org/api/report?server_name=tahvok.com
@Tahvok I see a completely different error for you: https://gist.github.com/richvdh/71913e1e8d382aaed1410978aeaeb97b.
I'm going to close this until someone can actually demonstrate the reported problem.
@jaywink's error seems perfectly normal if there's a web server/reverse proxy that has virtualhosts for both domain.tld
and matrix.domain.tld
. The web server will see it as a request to domain.tld
(SNI is always set to what certs the client expects, Host
header is generally the same as SNI). If there's no Matrix stuff on the domain.tld
virtualhost, 404 is the correct response.
Case;
domain.tld
delegates via SRV tomatrix.domain.tld
)matrix.domain.tld
has a valid SSL certificate formatrix.domain.tld
but not fordomain.tld
(as required by spec for SRV to work)The error given by the federation tester is as follows (in the JSON output):