Failed to restart vaultwarden.service: Unit vaultwarden.service not found.
runagent -m vaultwarden1 systemctl --user restart vaultwarden.service
Sir,
you are one of the best. Now it works. Thank you. ![]()
Nice Nice
I will work on Adding Custom email configs to avoid this
I spoke too soon… After rebooting the server, Vaultwarden can no longer find the configuration. I get a message saying that there are no services and the configuration cannot be found.
I will reset the server and try again tomorrow.
Weired
What is the vaultwarden1 status page saying
Can you screenshot
The page is empty. There is only the message
No configuration found. No status of the app, no status of the services. Screenshot is not possible, because server is in recovery modus
@kemboielvis22 let Deploy a testing server, that utilizes internal email for sending, i have noted, a number of failures on apps originate from internal email used. so that we can discover and resolve this on time.
@transocean allow us investigate this, and provide a permanent resolution, based on your scenarios.
Thank you.
Hmm… I have now reinstalled Vaultwarden and configured it according to @kemboielvis22 instructions. Now the application survives the server restart.
Nice
What might have happened before to cause the application to crash
If only I knew…
The cause was probably my impatience. My cluster consists of 2x NS8. 1x leader as DC with Samba and then 1x worker with the individual applications. After a reboot, both need a little time to find each other again. And starting the individual services also takes a certain amount of time. I probably should have just waited two minutes longer. Now everything is fine.
An update has been released.
add-module ghcr.io/geniusdynamics/vaultwarden:dev 1
Help In Testing
Please give me the command for update.
api-cli run update-module --data '{"module_url":"ghcr.io/geniusdynamics/vaultwarden:dev","instances":["vaultwarden1"],"force":true}'
For testing
Can you check you vaultwarden id its seems its not vaultarden1
Sorry, I selected the wrong Nethserver.
It looks good. The update is running smoothly. Backup and restore are also working fine.