Vaultwarden config.json is empty (0 B)
-
I was about to enable the Vaultwarden admin panel when I noticed that the config.json file is empty (0 bytes in size).
At first I thought it was the last update. But that was not the case (a restore didn't change anything).
Now I'm wondering if it's just a display error or if I've somehow got a mistake in thinking. - the config.json is the right place for these setting parameters, isn't it?
I'm worried that the settings are totally lost. Can they be read, edited and/or exported in other ways?Does anyone else have this problem too? I hope someone may have a solution.
(The file change time is set to 10 minutes caused by the restored backup) -
@kk_cloudron not sure, but mine isn't 0 B
I have this:
{ "domain": "xxx", "ip_header": "X-Forwarded-For", "_enable_smtp": true, "smtp_host": "mail", "smtp_ssl": false, "smtp_explicit_tls": false, "smtp_port": 2525, "smtp_from": "xxx", "smtp_from_name": "Vaultwarden", "smtp_username": "xxx", "smtp_password": "xxx", "smtp_auth_mechanism": "Plain", "smtp_timeout": 15, "smtp_accept_invalid_certs": true, "smtp_accept_invalid_hostnames": true, "admin_token": "xxx", "disable_admin_token": false, "signups_domains_whitelist": "", "signups_allowed": true, "invitations_allowed": true, "invitation_org_name": "Vaultwarden", "smtp_security": "off" }
Obviously where I've put
xxx
there are actual values. -
Hm the file should not be empty. If restoring to the previous versions also has an empty file, then can you try to restore the one before?
Generally you could remove the file and restart the app, then it will generate a new one. Not sure where the
admin_token
is used, since it will also recreate that one then. -
@nebulon said in Vaultwarden config.json is empty (0 B):
Not sure where the admin_token is used
I'm not certain, but I think it is only used to login to the admin at /admin as per https://docs.cloudron.io/apps/vaultwarden/#admin
-
-