Open Elara6331 opened 1 year ago
The issue seems to have fixed itself when matrix.org's signature and valid_until_ts
were refreshed. The homeserver is now receiving transactions from matrix.org again. I think it would be a good idea to figure out what caused this, but I don't know how to go about that since I can no longer reproduce the issue.
What is your value for global.cache.max_age
?
Wondering if this is maybe due a caching issue in combination with Dendrite being unable to fetch the keys from matrix.org
What is your value for
global.cache.max_age
? Wondering if this is maybe due a caching issue in combination with Dendrite being unable to fetch the keys from matrix.org
That's set to 1h
Well, there goes my theory.
okay as mentioned in #3278 https://github.com/matrix-org/gomatrixserverlib/commit/5dd581bf6b8f6eb962ea825b4e6bb763378e6cc4 seems to fix this. im told this should roll out soon, and i can attest that patching it in fixed the issue for me
Background information
go version
: N/A (go
doesn't exist in docker container)Description
Bad signature from \"matrix.org\" with ID \"ed25519:a_RXGa\"
. This is not happening with another dendrite homeserver I run, which is using the same version of dendrite.2023-09-14T18:16:17.796693324Z
. Nothing before that log event indicates any issues. I was notified about it by a user who couldn't see messages from matrix.org at2023-09-15T18:01:44Z
.Steps to reproduce
Current Log Snippet (debug enabled)
Log Snippet from the first occurrence (debug disabled)