-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Unable to join some rooms on matrix.org #13853
Comments
Thanks for reporting, a few questions: are you able to join any other rooms on matrix.org? What happens when the join fails-do you see an error message in the client, etc? |
Hello, The client is the Element flatpack on Fedora 36. The GUI error is.
I can join most rooms, but not others. For example, both #matrix:matrix.org, and #python:matrix.org are not working. But #fediverse:pixie.town and #FreeBSD:matrix.org work fine.There's no errors in the Nginx logs, or timeouts that I can see. Other than the posted error log here, I don't see anything wrong in the homeserver.log. |
Interesting-I don't see the |
Hello, Yes, is there a place to send the full log other than a public ticket? Here's at least the snippets that reference send_join. Note, I don't have the previous showed IPV6 error anywere in this log, so my guess that was the issue seems wrong.
|
You can DM me the full logs at @shayshay:matrix.org. |
This stacktrace is weird:
It suggests that somehow we're constructing a However, I suspect the reason you can't join |
Here's the DNS records as seen from my matrix instance. I'm not sure about any SRV records. The system is FreeBSD, not NetBSD, though I don't know if that makes a difference. In regards to #1211, my issue is not that it's slow, but that's it's impossible. It's not just the main matrix room this happens to. Are there any settings to increase the timeouts to allow the rooms to load? |
The timeout looks to be 60 seconds on the joiner's side: synapse/synapse/http/matrixfederationclient.py Lines 844 to 845 in a1b62af
Not currently configurable, but it's read from here:
You could try bumping this 60 to a larger number---but it's really a bodge around that fact that remote room joins are currently very expensive. |
Bumping self.default_timeout to 600 lets me join all the rooms. The client still throws an error and timeouts, but the room show up at a later time regardless. |
Thanks, I think that confirms that #1211 is the underlying cause. The in-progress faster remote room joins project should help here in the coming months. (https://github.com/matrix-org/synapse/milestone/8, https://github.com/matrix-org/synapse/milestone/10) |
Description
This error happens on an IPv4 only system. There is no IPV6 available, not even localhost. I believe this error is triggered when trying to join or communicate with rooms that are on servers with both IPv4 and IPv6.
The issue was discovered while trying to figure out why I can't join #matrix:matrix.org. The log below happened right as attempting to join #matrix:matrix.org failed, but I can't gurantee they are related.
Steps to reproduce
Simply run Synapse on a system without IPV6. Here's an example of my homeserver.yaml file.
listeners:
tls: false
type: http
x_forwarded: true
bind_addresses: ['172.16.10.84']
resources:
compress: false
Homeserver
(Private server)
Synapse Version
{"server_version":"1.67.0","python_version":"3.10.7"}
Installation Method
pip (from PyPI)
Platform
The operating system is FreeBSD 13.1. Synapse is run in a custom chroot and listens on a localhost bound IP. Synapse is proxied by Nginx.
Relevant log output
Anything else that would be useful to know?
I'm happy to do any testing, patching, or other work to help.
The text was updated successfully, but these errors were encountered: