-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Failed handle request via 'PublicRoomListRestServlet' #243 #5842
Comments
Drat, I spoke too soon. After adding the SRV record, things seemed stable for a good 5 or 6 times in a row, but now it's back to before. |
M yobservation is, that when it fails, it keeps failing for some time for all servers. After some unmeasured time elapses, it starts working again until it randomly fails. |
please could you include more logs for the request in question? |
will try to if I'm able to get to the room directory again. for now, are the logs in the OP enough to investigate? |
no, I'd like to see the logs leading up to the error. |
Turns out, that my observation is caused by weird riot-web behavior: when it gets "Internal server error", it keeps showing that message even when I want to browse different server than one that returned 500. Also, it says "Internal server error", even when server returns "Unauthorized". UPDATE |
seems to be resolved on my end too. must have been a temporary misconfiguration on matrix.org's side |
possible it was fixed when we deployed #5851 |
@richvdh You are probably right. When I try to connnect to servers that are still on synapse 1.2.1, it still causes error from OP. |
Description
Synapse is returning a 500 for
_matrix/client/r0/publicRooms?server=matrix.org
about 75% of the time with this error:Steps to reproduce
matrix.org
as the server to load the directory forRiot failed to get the public room list. Internal server error
in RiotVersion information
typokign.com
If not matrix.org:
Version: v1.2.1
Install method: spantaleev/matrix-docker-ansible-deploy (issue: Failed handle request via 'PublicRoomListRestServlet' spantaleev/matrix-docker-ansible-deploy#243)
matrixdotorg/synapse:v1.2.1
Docker container on Ubuntu 18.04 LTSThe text was updated successfully, but these errors were encountered: