[ VaultWarden ] [ 1.28.0.0 ] Password management solution for individuals, teams, and business organizations.

[QNAP_Stephane]

I see seems easy to fix juste and export ADMIN_TOKEN in startup qpkg script.. William give à try

Envoyé de mon MI 9 en utilisant Tapatalk

[sondi2003]

Many thanks to everyone for the quick response.
I have now done it exactly according to your specifications.
Then Bitwarden restart, no change.
Qnap NAS restart, no change
Safari browser cache cleared, no change
But why?

[mbino]

So you put config.json in the folder: /share/MD0_DATA/.qpkg/BitWarden/data ?

[sondi2003]

yes I have, the way I see it

[mbino]

try a simple admin_token first, to verify it works, you can change it through the web interface after login in with a simple one like "test".

[sondi2003]

I set the token to test,
restart Bitwarden, same problem
Then I uninstalled Bitwarden and checked whether all data had been removed, then reinstalled it and created the json again. Then restart again and then try to call up the admin panel https://sub.domain.ch:8000/admin.
Unfortunately still not fixed.
for further information. I created a letsencrypt certificate and then uploaded it to the Qnap under certificates. if this is still important.
Thank you

[sondi2003]

Hi,
I was able to solve the problem below.
I installed bitwardenrs docker, the config.json was created there. I then exported this complete with all settings and imported it into the Qnap qpkg version.
Then reboot the app and successfully access the admin portal
Greeting
sondi2003

[QNAP_Stephane]

I will work on it.. Hope provide a version soon

Envoyé de mon MI 9 en utilisant Tapatalk

[QNAP_Stephane]

updated to 19.0.1 is an internal update QPKG

Code: Select all

this version check if token.txt is available in $QPKG_ROOT
if not, it generates a token for admin access via openssl for each new install ( https://ip:8000/admin ) and do an export ADMIN_TOKEN for current session (survive at reboot)
this token will be display in NAS event log and can be found in $QPKG_ROOT/token.txt (/opt/BitWarden/tokens.txt)

[QNAP_Stephane]

updated

[QNAP_Stephane]

updated to 1.21.0

renamed Bitwarden_rs to VaultWarden

Code: Select all

Changelog
Add support for enabling auto-deletion of trash items after X days, disabled by default
Set TRASH_AUTO_DELETE_DAYS to a positive value to enable this functionality
You can also configure how often this process runs, using cron sintax with the variable TRASH_PURGE_SCHEDULE
Updates to the icon fetching, making it more reliable in detecting icon types
Updated admin page, improving version checks and SQLite backup feature

[n30c0r73x]

Hello all,

I updated my QNAP to QTS 5.0 yesterday. After that, VaultWarden (I'm running version 1.22.2.0) is having problems starting...

[/share/CE_CACHEDEV2_DATA/.qpkg/BitWarden] # ./BitWarden.sh start
token file exists
ADMIN_TOKEN for bitwarden
#############################################################
vaultwarden : Found MyQnapCloud Lets Encrypt/SSL certificate and use it
./vaultwarden: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
[/share/CE_CACHEDEV2_DATA/.qpkg/BitWarden] #

Looks like QTS 5 has broken it.

Any ideas for a fix?

N

[QNAP_Stephane]

openssl has been updated in QTS5 it needs a fix

[QNAP_Stephane]

updated for QTS 5

[n30c0r73x]

updated for QTS 5

Thank you QNAP_Stephane!