-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
server keeps trying to handle device list update on a server that doesn't exists anymore (301: Moved Permanently) #8983
Comments
also, my homeserver has only me using it (@thomas:smartceva.com) I have no idea who @lucasmendes:orthool.com is or why the log is asking me to do a device resync on this random user. |
You likely share an encrypted room with this person. |
Looks like that user's server might be broken, https://orthool.com/.well-known/matrix/server points to matrix.orthool.com, but that https://matrix.orthool.com and all other endpoints there are returning a 301. |
How can I find out which room it is? |
@thomasesr My Synapse logs are filled with I do have a question for the community though: Is there a way to stop the log-spamming? Maybe these messages should be Notices, given how frequent they are? It's really not informative to me, I have a hard time reading my logs. |
Considering your logs: why |
Hello, my homeserver is completely nonfunctional (as in, for clients connecting) and these are the only error messages that show up in any log output (homeserver.log, stdout and stderr). Whenever my client attempts to send a message, the log fills up with errors such as this one, despite there being no members from the homeservers mentioned present in the room that the messages are sent in. |
I have recently moved my homeserver and used delegation (and 301 redirects, because some clients don't seem to get the message) to update its location, and now another homeserver which I'm using to debug is spamming these messages and can't seem to send messages to the moved homeserver properly. Hopefully it all clears up when the other server will refetch the |
This still filles up my log with MANY entries...
and this is only one user of MANY users... |
I think #16298 will mitigate this a bunch |
Description
Steps to reproduce
Failed to handle device list update for @lucasmendes:orthool.com: 301: Moved Permanently,
Version information
smartceva.com
1.24.0
portainer
docker
The text was updated successfully, but these errors were encountered: