Unable to sign into account after logging out

bpoteryko commented 5 months ago

Describe the bug

Mis-clicked the 'sign out' option and now Memos will not allow me to sign in again. When I attempt to sign in by navigating to http://<my-server>:5230/auth the page shows me the sign in page for an instant, then changes to a screen with the logo in the centre, and no controls aside from language and dark/light mode at the bottom.

The log file in the Docker container produces the following whenever I visit the sign-on page, it appears the issue is my user is not found.

memos  | 2024/06/13 02:33:10 INFO OK method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile
memos  | 2024/06/13 02:33:10 INFO client error method=/memos.api.v1.AuthService/GetAuthStatus error="rpc error: code = Unauthenticated desc = user not found"
memos  | 2024/06/13 02:33:10 INFO OK method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting
memos  | 2024/06/13 02:33:10 INFO OK method=/memos.api.v1.IdentityProviderService/ListIdentityProviders

I tried several other browsers and the issue remains, however the Android app MoeMemos is unaffected, I am still able to log in and create memos just fine on my phone.

Steps to reproduce

Click the sign out button on the left and allow the page to sign out.
Click the sign in button on the left hand side.
Memos should now produce a sign in screen for a fraction of a second, then show just the logo.

The version of Memos you're using

v0.22.2

I attempted to downgrade, changing to v0.21.0 allows me to sign in again, but the client is unable to read any existing memos nor allow me to create new ones, and when upgrading back to latest, the original issue begins again.

Screenshots or additional context

This is what the blank screen looks like: image of blank screen

DRazumovskiy commented 4 months ago

Same issue here. Upgraded from 0.22.0 to 0.22.2 and cannot login anymore. That's what I have in logs:

2024/06/18 15:26:47 INFO OK method=/memos.api.v1.AuthService/SignIn 2024/06/18 15:26:47 INFO OK method=/memos.api.v1.AuthService/GetAuthStatus 2024/06/18 15:26:47 INFO OK method=/memos.api.v1.UserService/GetUserSetting 2024/06/18 15:26:48 ERROR server error method=/memos.api.v1.AuthService/GetAuthStatus error="failed to get user: interrupted (9)" 2024/06/18 15:26:48 INFO OK method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile 2024/06/18 15:26:48 ERROR server error method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting error="failed to get user: interrupted (9)" 2024/06/18 15:26:48 INFO OK method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting 2024/06/18 15:26:48 ERROR server error method=/memos.api.v1.AuthService/GetAuthStatus error="failed to get user: interrupted (9)" 2024/06/18 15:26:48 INFO OK method=/memos.api.v1.WorkspaceService/GetWorkspaceProfile 2024/06/18 15:26:48 ERROR server error method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting error="failed to get user: interrupted (9)" 2024/06/18 15:26:48 INFO OK method=/memos.api.v1.WorkspaceSettingService/GetWorkspaceSetting 2024/06/18 15:26:48 INFO OK method=/memos.api.v1.MemoService/ListMemos 2024/06/18 15:26:48 INFO OK method=/memos.api.v1.MemoService/ListMemoTags 2024/06/18 15:26:49 INFO OK method=/memos.api.v1.IdentityProviderService/ListIdentityProviders

DRazumovskiy commented 4 months ago

After downgrading to 0.22.0 I've lost all items from Timeline. Now it's empty

lovwyr commented 4 months ago

Same Issue here, its fixable by restarting the Container but its very annoying. Side Remark: this only happens on an new Instance (0.22.2) for me. My upgraded old Instance are not facing it.

bpoteryko commented 4 months ago

To provide an update, I have managed to log in using the Vivaldi browser, but Firefox-based ones still provide the issue I initially described.

bpoteryko commented 3 months ago

Issue fixed with updating to the most recent version.

usememos / memos