"Your session has expired" immediately after attempting to log in

csolisr commented 3 years ago

Describe the bug

When attempting to log into BitWarden (whether through the Firefox plugin or the website), the session closes immediately after logging in, with a message stating "Your session has expired". Checking the journalctl logs I find the following error:

bitwarden_rs[761] Error: Unauthorized Error: Invalid claim
bitwarden_rs[761] Warning: Responding with 401 Unauthorized catcher.

Context

Hardware: Raspberry Pi 4, at home
YunoHost version: 4.1.7.2
I have access to my server: Through SSH and physically
Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
Using package version: 1.16.3~ynh2

Steps to reproduce

Install and configure BitWarden as usual
Open the web browser. Alternatively, open the browser extension, enter the settings cog, point towards your server
Enter your user name and password, then log in

Expected behavior

The application should log in, giving access to my stored passwords.

Logs

 journalctl -u bitwarden                                                                                                                                                   │···························
-- Logs begin at Thu 2021-02-25 14:24:25 CST, end at Fri 2021-02-26 12:18:40 CST. --                                                                                                                             │···························
Feb 25 16:52:56 azkware.net bitwarden_rs[761]: Error: No matching routes for HEAD /.                                                                                                                             │···························
Feb 25 22:52:56 azkware.net bitwarden_rs[761]: Error: Unauthorized Error: Invalid claim                                                                                                                          │···························
Feb 25 22:52:56 azkware.net bitwarden_rs[761]: Warning: Responding with 401 Unauthorized catcher.                                                                                                                │···························
Feb 26 10:42:48 azkware.net bitwarden_rs[761]: Warning: Response was `None`.                                                                                                                                     │···························
Feb 26 10:42:48 azkware.net bitwarden_rs[761]: Warning: Responding with 404 Not Found catcher.                                                                                                                   │···························
Feb 26 12:06:09 azkware.net bitwarden_rs[761]: Error: Unauthorized Error: Invalid claim                                                                                                                          │···························
Feb 26 12:06:09 azkware.net bitwarden_rs[761]: Warning: Responding with 401 Unauthorized catcher.                                                                                                                │···························
Feb 26 12:06:53 azkware.net bitwarden_rs[761]: Error: Unauthorized Error: Invalid claim                                                                                                                          │···························
Feb 26 12:06:53 azkware.net bitwarden_rs[761]: Warning: Responding with 401 Unauthorized catcher.                                                                                                                │···························
Feb 26 12:10:51 azkware.net bitwarden_rs[761]: Error: Unauthorized Error: Invalid claim                                                                                                                          │···························
Feb 26 12:10:51 azkware.net bitwarden_rs[761]: Warning: Responding with 401 Unauthorized catcher.                                                                                                                │···························
Feb 26 12:11:27 azkware.net bitwarden_rs[761]: Error: Unauthorized Error: Invalid claim                                                                                                                          │···························
Feb 26 12:11:27 azkware.net bitwarden_rs[761]: Warning: Responding with 401 Unauthorized catcher.

Browser console:

ERROR Error: Uncaught (in promise): Error: Token not found.
d</n.prototype.decodeToken@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:1059742
d</n.prototype.getPremium@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:1061009
p</n.prototype.canAccessPremium/</<@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:1070084
o/</<@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:1067111
o/<@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:1067216
t</<@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:1066128
t@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:13891
t<@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:1065902
p</n.prototype.canAccessPremium@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:1069968
g</n.prototype.ngOnInit/</</l</</<@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:372022
o/</<@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:370475
o/<@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:370580
i@https://pass.azkware.net/app/main.ec1191668ddd60d16e05.js:1:369323
c</t.prototype.invoke@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:7006
onInvoke@https://pass.azkware.net/app/vendor.ec1191668ddd60d16e05.js:624:1087
c</t.prototype.invoke@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:6946
a</e.prototype.run@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:2205
E/<@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:13683
c</t.prototype.invokeTask@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:7690
onInvokeTask@https://pass.azkware.net/app/vendor.ec1191668ddd60d16e05.js:624:999
c</t.prototype.invokeTask@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:7611
a</e.prototype.runTask@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:2868
y@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:9981
o@https://pass.azkware.net/app/vendor.ec1191668ddd60d16e05.js:1576:57020
D/<@https://pass.azkware.net/app/vendor.ec1191668ddd60d16e05.js:1576:57166
c@https://pass.azkware.net/app/vendor.ec1191668ddd60d16e05.js:1544:72219
c</t.prototype.invoke@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:7006
a</e.prototype.runGuarded@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:2366
a</e.prototype.wrap/<@https://pass.azkware.net/app/polyfills.ec1191668ddd60d16e05.js:8:2085
    Angular 2
    o main.ec1191668ddd60d16e05.js:1
    Angular 10
    o es6.promise.js:75
    D es6.promise.js:92
    c _microtask.js:18
    Angular 3
core.js:15714:18
    Angular 4
    RxJS 5
    Angular 11
    o es6.promise.js:75
    D es6.promise.js:92
    c _microtask.js:18
    Angular 3

alexAubin commented 3 years ago

This furiously sounds like https://github.com/YunoHost-Apps/bitwarden_ynh/issues/3 which was in fact fixed/merged a few days ago, c.f. new version 1.19.0~ynh1

Can you confirm Yunohost proposes an upgrade to 1.19.0~ynh1 ?

csolisr commented 3 years ago

I already tried a manual yunohost app upgrade bitwarden but YunoHost insists that it's the latest version.

csolisr commented 3 years ago

Just managed to force-upgrade the apps repository, and lo and behold BitWarden has finally upgraded. Web is working fine, but the browser addon is still not opening completely, I'll wait until the other upgrades are done to see if it's a performance bottleneck.

yalh76 commented 3 years ago

Can you give more informations about the browser addon issue ? because I don't know how it works ...

YunoHost-Apps / vaultwarden_ynh