Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Vaultwarden - Can not send email anymore (STARTTLS error)

    Vaultwarden
    vaultwarden email smtp starttls bitwarden
    3
    16
    1446
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • mrmx
      mrmx last edited by

      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)

      girish 1 Reply Last reply Reply Quote 0
      • Moved from Support by  girish girish 
      • girish
        girish Staff @mrmx last edited by

        @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?

        mrmx 1 Reply Last reply Reply Quote 0
        • mrmx
          mrmx @girish last edited by mrmx

          @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 1 Reply Last reply Reply Quote 0
          • girish
            girish Staff @mrmx last edited by girish

            @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.

            mrmx 1 Reply Last reply Reply Quote 0
            • girish
              girish Staff last edited by

              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 arshsahzad 2 Replies Last reply Reply Quote 0
              • mrmx
                mrmx @girish last edited by

                @girish Yep a fresh install works like a charm.
                I tried with a previous backup and it's not the the data, so it seems an instance networking problem.

                1 Reply Last reply Reply Quote 0
                • mrmx
                  mrmx @girish last edited by

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

                  arshsahzad 1 Reply Last reply Reply Quote 1
                  • arshsahzad
                    arshsahzad @mrmx last edited by arshsahzad

                    same problem with me...

                    1 Reply Last reply Reply Quote 0
                    • arshsahzad
                      arshsahzad @girish 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 1 Reply Last reply Reply Quote 0
                      • girish
                        girish Staff @arshsahzad last edited by

                        @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 1 Reply Last reply Reply Quote 0
                        • arshsahzad
                          arshsahzad @girish last edited by 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 1 Reply Last reply Reply Quote 0
                          • girish
                            girish Staff @arshsahzad last edited by

                            @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 1 Reply Last reply Reply Quote 0
                            • arshsahzad
                              arshsahzad @girish last edited by

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

                              girish 2 Replies Last reply Reply Quote 0
                              • girish
                                girish Staff @arshsahzad last edited by

                                @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.

                                1 Reply Last reply Reply Quote 3
                                • girish
                                  girish Staff @arshsahzad last edited by girish

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

                                  arshsahzad 1 Reply Last reply Reply Quote 3
                                  • arshsahzad
                                    arshsahzad @girish last edited by

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

                                    1 Reply Last reply Reply Quote 1
                                    • First post
                                      Last post
                                    Powered by NodeBB