Closed pedro-nonfree closed 2 years ago
This is a Synapse issue in it not issuing a soft logout, so clients SHOULD be wiping data because this is the same mechanism used for remote deauth (for when your device is stolen and thus should be wiped of keys).
I suggest adding your edge case of disk full to https://github.com/matrix-org/synapse/issues/13203 which is the issue tracking sending soft_logout: true
in the default case and only omitting it when the user explicitly asked to deauth that device.
Hydrogen's messaging is more vague which Element tries to avoid as most users don't have a connection to their homeserver admin. If Synapse fixed their behaviour to send soft_logout then you'd be presented with a screen to log in once again (without losing any keys) and that login might fail if your disk is full but it would be with a clear error.
Closing as fundamentally a security position which only Synapse can improve.
after freeing the server space problem is still not solved (I thought it was just that), in my case, the user auth is expired matrix-org/synapse#13203 ; then, that user cannot do almost anything
with server error code 401
on path /_matrix/client/r0/thirdparty/protocols
with the following response
{"errcode":"M_UNKNOWN_TOKEN","error":"Invalid access token passed.","soft_logout":false}
update: filldisk is unrelated to this, followup of our bug on: https://github.com/matrix-org/matrix-synapse-ldap3/issues/167
Steps to reproduce
Synapse server had a problem of
no space left
(check out annex 1 to see how was in logs) (EDIT:no space left
problem is unrelated to this database problem, see #167), but for me it was difficult to determine that the problem was in the server, I thought it was the client. The errors shown:after pressing OK stays syncing indefinitely, and that's confusing:
look the javascript errors at annex 2
hydrogen.element.io did better error handling, they said:
and in detail:
then I realized, oh, so this is really a homeserver error
annex 1: the synapse error
annex 2: the javascript error
posted here because is very long
Outcome
improve error handling, so when support service looks for the error, require less time what to look at
Operating system
No response
Browser information
No response
URL for webapp
No response
Application version
No response
Homeserver
No response
Will you send logs?
Yes