Vaultwarden - Can not send email anymore (STARTTLS error)
-
OK, I did a full test and this works fine for me .
Just to double check, have you configured anything mail related in
/app/data/config.env? If you like I can debug this further, if you write to support@cloudron.io and give us remote access. -
@girish Nope, I'm sorry but keep the fresh instance and deleted the failing one, so this problem will be in the unknown...
wrote on Dec 16, 2021, 3:36 PM last edited by arshsahzad Dec 17, 2021, 11:25 AMsame problem with me...
-
OK, I did a full test and this works fine for me .
Just to double check, have you configured anything mail related in
/app/data/config.env? If you like I can debug this further, if you write to support@cloudron.io and give us remote access.wrote on Dec 17, 2021, 11:26 AM last edited by@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 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@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 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
wrote on Jan 6, 2022, 8:22 AM last edited by arshsahzad Jan 10, 2022, 12:45 PM@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 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.
@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 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.
wrote on Jan 10, 2022, 12:44 PM last edited by@girish I have mailed for support request, with the subject - SMTP Error
-
@girish I have mailed for support request, with the subject - SMTP Error
@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 I have mailed for support request, with the subject - SMTP Error
@arshsahzad I have pushed a new package. Can you try now? I already updated your instance.
-
@arshsahzad I have pushed a new package. Can you try now? I already updated your instance.
wrote on Jan 12, 2022, 5:13 AM last edited by@girish Thanks for a quick fix, It's now working