-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
M_UNKNOWN for a room that exists #24200
Comments
Soon afterwards I received |
When I refresh the page I get the same error, but when I switch to the room with Ctrl-K, it appears. |
Same problem on app.element.io |
Getting this in console:
|
So I'm being rate-limited. |
Same (RVS failed to get room id for alias: ... I'm not sure what is RVS |
I saw an issue that was causing lots of requests, but I can't find it. If this is an example of that issue, I remember that it was actually fixed, but any users hit by it need to wait for the queue of requests to drain and then it will start working again. If/when I find the issue number I'll double-check this and then mark this as a duplicate if that seems right. Meanwhile, matrix.org might be struggling a bit, maybe because of this problem. |
It seems to be healthier for me now. @argentatus-larus ? |
sorry, this was a partial outage on matrix.org, between 10:30 and 11:10 or so, UTC. |
Same, all good, thank you! |
you may be thinking of #24167? I don't think that's related here. |
At least for me, it didn't trigger a rate limiting on m.org. Do the rate limit checks depend on the endpoints? |
Yes I was, thank you. |
OK, so this was down to a partial outage on matrix.org, closing. |
Steps to reproduce
Outcome
What did you expect?
To return to the room I was looking at.
What happened instead?
I received this message:
Operating system
Ubuntu 22.04
Browser information
Firefox 108.0.2
URL for webapp
https://develop.element.io
Application version
Element version: 5b730f4-react-b1c32995c679-js-e2ce379b56b9 Olm version: 3.2.12
Homeserver
matrix.org
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: