Can't log out of Riot whilst HS is down

[lukebarnard1]

Trying to log out of my locally-built vector which is logged into a locally-running synapse, but can't open the user settings page in order to do that. Probably because the settings page loads forever trying to get something from matrix.org.

(And I want to logout so that I can log my local vector onto my own HS)

Seems to be coming from matrix-js-sdk UserSettings.js _renderCryptoInfo.

UserSettings.js:335 Error: End-to-end encryption disabled
    at MatrixClient.getStoredDevicesForUser (http://localhost:8083/bundle.js:43252:16)
    at Constructor._renderCryptoInfo (http://localhost:8083/bundle.js:80429:36)
    at Constructor.render (http://localhost:8083/bundle.js:80808:23)

[richvdh]

I'm surprised this is a thing. If you're logged into a local synapse, why is it trying to reach matrix.org? @lukebarnard1: is it still a thing?

[lukebarnard1]

I haven't been in a position where it would happen. I'm not sure why my local, non-federated synapse would be blocked on matrix.org.

[lukebarnard1]

From @dbkr:

Unfortunately, you can't open the settings page because that requires a connection to your HS, so there's no way to log out.

No consensus on whether the settings page is loading from matrix.org or just the local HS

[gnorbsl]

I encountered the same issue. It's impossible to logout or open the settings when my synapse server is down.

[xlith]

same issue

[e-dt]

same issue

[richvdh]

rereading this, I think the stuff about matrix.org is a complete red herring. The report should say "the settings page loads forever trying to get something from the current homeserver"

[smokku]

@richvdh is right. The issue is that Settings page is trying to access current HS.

This makes it impossible to logout and login to some other alive server.

P.S. To work around the issue, you need to clear Local Storage for the web client domain (either through browser privacy settings or DevTools).

[doug1]

I just got bit by this one last week. I had a synapse homeserver instance in a Linux VM for testing, and deleted it when I was done. My Windows Riot client would just sit there spinning looking for the now non-existent server, and the "logout" button/link was missing from the spinner screen. After waiting (minutes?) for it to time out, I was still not able to use the setting ("gear") icon, since it requires the homeserver to be up to show the settings window. How to clear Local Storage was not immediately obvious in the Windows desktop client. I then searched the filesystem for a plaintext configuration file where I could change the server name, but only found SQLite and LevelDB files, so no luck there. In the end, my Riot client install was not easily recoverable, and I was frustrated, so I just deleted it. Is there any why to recover from a down homeserver at all? If not, please increase this to P1 since it renders the client unusable.

[smokku]

I believe this is fixed in https://riot.im/experimental as there is a "Logout" option accessible directly from user menu.

[aaronraimist]

The logging out may be fixed (I haven’t tested that button when the server is down) but @tango_bravo14:matrix.org also brought up that you also can’t export your keys if the server is down.

The settings page should probably be available or at least a limited part of it when the server is down (or the domain has been changed or whatever).

[varh1i]

I did:

• kill the riot process
• move your ~/.config/Riot folder to some different location (just to save it as backup)