Vaultwarden - Can not send email anymore (STARTTLS error)

[mrmx]

@girish Nope, I'm sorry but keep the fresh instance and deleted the failing one, so this problem will be in the unknown...

[arshsahzad]

same problem with me...

[arshsahzad]

@girish I have to invite someone, after the recent update of vaultwarden, my SMTP is not working in vaultwarden, earlier it was working, I didn't make any changes, I'm getting below error:-

An error has occurred.
SMTP 5xx error: permanent error (535) - Authentication credentials invalid

[girish]

@arshsahzad are you still facing this issue? Can you tell me which version of Cloudron you are on? I thought we sorted the STARTTLS issues out in Cloudron 7.0.4

[arshsahzad]

@girish I'm using Cloudron v7.0.4 and vaultwarden 1.23.1, When installing the new vaultwarden, it's working fine but the existing vault producing the above-mentioned error.

[girish]

@arshsahzad If you like, I can debug the instance to find out what's happening. Please drop us a mail at support@cloudorn.io. I initially suspected that maybe vaultwarden is caching env vars in the database or something but that doesn't seem to be the case. The env vars explicitly disable STARTTLS and TLS.

[arshsahzad]

@girish I have mailed for support request, with the subject - SMTP Error

[girish]

@arshsahzad thanks, was just investigating. It seems vaultwarden has two sources of configs - env vars and config.json . The latter is editing via the admin/ui interface and overrides the former. In Cloudron package, we use env vars. In your config, I see that SMTP variables are set which means that they have now gone out of sync with the env vars.

https://github.com/dani-garcia/vaultwarden/wiki/Configuration-overview

I am fixing Cloudron package to use config.json instead of be consistent.

[girish]

@arshsahzad I have pushed a new package. Can you try now? I already updated your instance.

[arshsahzad]

@girish Thanks for a quick fix, It's now working