-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
401 Unauthorized when getting public room list #7762
Comments
a note to whoever picks this up: I'd like us to investigate why matrix.org is reporting
|
the reason this is happening is that google's public DNS is giving us a SERVFAIL when we try to look up the SRV record:
So this is kinda the same as #6589. The problem is that I don't really know why it is returning SERVFAIL for this request. I've raised an issue about it here: https://issuetracker.google.com/issues/160447762. I'll be interested to see if we get an answer. |
ahh I think it's a DNSSEC fail:
|
Thanks for looking into it - not what I expected. Or is it just different DNS servers handling stuff differently/incorrectly?
But 1.1.1.1 gives NXDOMAIN:
If the error is DNS server dependent it kind of make sense that it federating works fine with some servers because they are likely to use different DNS. Though that doesn't explain why the federation tester is OK unless it and synapse handle SERVFAIL and NXDOMAIN differently, which would be confusing. Also it seems a bit weird to me that SRV lookups are being done in the first place considering the first line of delegate.md:
I must admit I'm a bit out of my depth with some of this DNS stuff, so apologies if I've said anything that doesn't make sense. |
I'm no dnssec expert myself, but the answer at https://issuetracker.google.com/issues/160447762 confirms that this is a dnssec problem. Essentially your server is not returning the correct records to confirm the non-existence of
Unfortunately that is the case: this is matrix-org/matrix-federation-tester#92.
Well, delegate.md simplifies the case slightly. We have to check whether you have a SRV record so that we can follow it if it exists. Normally we expect that to return a NXDOMAIN ("no such record"), in which case, we fall back to the default. But because your server returns an invalid response, we're a bit stuck. One workaround which might work for you is to use a .well-known file with an explicit port number. This will mean the SRV lookup gets skipped. Again, see delegate.md. I'd really recommend you get your DNSSEC sorted though. This is confirmed as a configuration issue on your side, so I'm going to go ahead and close this. Good luck getting it sorted though! |
Alright, thanks a lot |
Just in case someone with the same problem as me is stumbling over this issue as well: |
Description
I recently moved my Synapse install to a different VPS by installing afresh and moving the database, media directory,
homeserver.yaml
andhomeserver.signing.key
. Of possible relevance is that the old VPS was running Ubuntu 18.04 whereas the new one is on 16.04 (so I can run BigBlueButton). I also changed from Apache to Nginx, and from using an SRV record to listening directly on 8448 for federation.Everything works as expected apart from 2 things:
matrix.org
postmarketos.org
I think these 2 problems are actually the same underneath.
It's worth noting that:
matrix.org
and it workedmozilla.org
andprivacytools.io
Viewing and joining rooms on
matrix.org
calcuode.com
matrix.org
using the drop-downThe error Riot shows is:
And in Synapse's
homeserver.log
:When trying to add a new server
calcuode.com
Add a new server
postmarketos.org
)The error Riot shows (in a pop-up that sometimes doesn't pop up) is:
Synapse's
homeserver.log
:I also get the same error when trying to add
matrix.org
manually.Version information
https://packages.matrix.org/debian/
using aptIf you need any more info just let me know, thanks for taking a look.
The text was updated successfully, but these errors were encountered: