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 SSL error connecting mail server from client

    Support
    2
    4
    158
    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.
    • A
      augusto last edited by

      Hi,

      I have 3 domains on my cloudron and use it as a mail server for the 3 of them. I use 2 clients (fastmail and mailbird) to connect to it but yesterday out of nowhere I started getting a connection error on my clients.

      Here is the error I get in fastmail: Hmm, that didn’t work. Could not connect to server: SSL error SSL connect attempt failed error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

      Similar error I get on mailbird. I can access my email and looks to be working ok on Roundcube, but can't access it on the other clients.

      I checked some other posts but nothing worked so far. My cloudron is on AWS and already tried opening outbound 53 UDP and renewing certs, logs show no errors and certs appear to be valid.

      nebulon 1 Reply Last reply Reply Quote 0
      • nebulon
        nebulon Staff @augusto last edited by

        @augusto can you try if restarting the mail service from the Cloudron dashboard's Services view fixes the issue? If so, on which Cloudron version are you?

        1 Reply Last reply Reply Quote 0
        • A
          augusto last edited by

          Hi! Thanks, restarting services worked. Do you know what might have caused it and how do I prevent from happening again? I'm on version 6.3.6

          1 Reply Last reply Reply Quote 0
          • nebulon
            nebulon Staff last edited by

            Looks like we have to investigate again, but a similar issue was fixed in that version, apparently didn't fix all the cases.

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