-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I cannot send encrypted messages to matrix.org, but I can receive them?!? #17085
Comments
One more thing, the clients receive this message after a while:
|
Some other homeservers are also experiencing the same issue. I've seen people complain about it in other public rooms. |
Problem still exist ... can anyone help? |
Logs like this one from your snippet sound useful; if you have any recent ones please share: Try to include all the log lines from the log message (I don't know if you are filtering it out), it'd be really useful to see the full URL requested from Matrix.org Probably your server can't federate directly with Matrix.org but can with other servers; then other servers are relaying the encrypted message to Matrix.org but since you never federate directly, you can't send the required to-device messages for Matrix.org users to decrypt the messages. Does this sound plausible — are there users from other servers in the same rooms? |
The problem has only existed since the beginning of April. Before that, I was able to write to matrix.org people without any problems. Since April it no longer works, regardless of whether it is in encrypted groups or 1-to-1 chats. Unfortunately I don't have any more logs, when I grep matrix.org only these few lines come up. |
With a busy log like that, usually the best approach is to first make a search based on what you're interested in, then grep for the request identifier, to get all the log lines for the related request. See https://element-hq.github.io/synapse/latest/usage/administration/request_log.html In the example from your first post |
I find a lot of these errors now in the log. What else can I do? What could be the reason?
|
I think we need more of the surrounding log lines. But if anything an error in Can you dig up some log lines that fail when you are sending to matrix.org?
something like |
Unfortunately, I can't find anything in the log. But when I restart Synapse, I get the missing messages in my matrix.org account, but it says “encrypted” instead of a text.
|
Description
On my home server, I can send and receive encrypted messages to and from different servers without any problems.
But I cannot send messages to matrix.org, receiving them works fine.
There is also no write notification when sending.
I also switched the Docker Synapse Worker setup back to Monolith for testing, but this did not bring any improvement.
I cannot find anything in the logs that directly indicates an encryption problem.
Is there anything else I can do to provide usable logs?
Steps to reproduce
I have no idea, from my other home server I can send and receive encrypted messages to matrix.org without any problems.
Homeserver
nope.chat
Synapse Version
1.104.0
Installation Method
Docker (matrixdotorg/synapse)
Database
PostgreSQL 14
Workers
Multiple workers
Platform
Debian 12.5
Docker Engine - Community Version: 26.0.1
Docker Compose version v2.26.1
Configuration
No response
Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: