Vaultwarden - Can not send email anymore (STARTTLS error)
-
Just tried to invite someone to my Bitwarden instance and always reports the error: SMTP Client error: internal client error: STARTTLS is not supported on this server.
The other apps can send mail btw.
It just worked before, may be the latest Cloudron version update?
Vaultwarden 1.23.0
Cloudron v7.0.4 (Ubuntu 18.04.3 LTS) -
G girish moved this topic from Support on
-
Just tried to invite someone to my Bitwarden instance and always reports the error: SMTP Client error: internal client error: STARTTLS is not supported on this server.
The other apps can send mail btw.
It just worked before, may be the latest Cloudron version update?
Vaultwarden 1.23.0
Cloudron v7.0.4 (Ubuntu 18.04.3 LTS) -
@mrmx Just tried this and it does work on a new install. Can you go the Location view and click Save without making any changes and then try to invite someone again?
@girish Done and stays the same, here you are the log:
[2021-11-25 10:23:04.602][vaultwarden::mail][ERROR] SMTP Client error: internal client error: STARTTLS is not supported on this server
Te installation was done a month ago or so, and it's not used until now that we need it. I could reinstall for sure, but I this error can be fixed it would be better for Cloudron
-
@girish Done and stays the same, here you are the log:
[2021-11-25 10:23:04.602][vaultwarden::mail][ERROR] SMTP Client error: internal client error: STARTTLS is not supported on this server
Te installation was done a month ago or so, and it's not used until now that we need it. I could reinstall for sure, but I this error can be fixed it would be better for Cloudron
@mrmx thanks, just to quickly test, can you install a new vaultwarden instance and see if it has the same problem? If so, this looks like some problem with the new Cloudron 7 update (not sure what that is yet though). In the meantime, I am trying to reproduce this by updating from Cloudron 6.3 to 7 with vaultwarden installed.
-
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. -
@mrmx thanks, just to quickly test, can you install a new vaultwarden instance and see if it has the same problem? If so, this looks like some problem with the new Cloudron 7 update (not sure what that is yet though). In the meantime, I am trying to reproduce this by updating from Cloudron 6.3 to 7 with vaultwarden installed.
-
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...
same 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.@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
@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.
@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.
@girish Thanks for a quick fix, It's now working
