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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Certificate issues when connecting to IMAP

Certificate issues when connecting to IMAP

Scheduled Pinned Locked Moved Solved Support
email
4 Posts 3 Posters 1.6k Views 4 Watching
  • 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.
  • BounzB Offline
    BounzB Offline
    Bounz
    wrote on last edited by girish
    #1

    Hi there.
    Today after restarting Cloudron service (it asked about restart due to some security reasons) my mail clients stopped connecting to IMAP with errors related to the SSL certificate.
    I tried to renew certificates through the admin panel but this didn't help.
    Here how it looks from Thunderbird client. First, it says that certificate information is outdated:
    d5e1bbd4-1422-40d1-91c1-4bd61e939744-image.png

    After clicking on Get certificate button it says that it can't get information:
    9768fcb9-8723-4af8-b959-be0eecf617e0-image.png

    How can I fix this issue? At the moment I can use email only trough SOGo client.

    1 Reply Last reply
    1
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      @Bounz There is a bug a in Cloudron that when the certificate gets renewed, the mail container is not updated with the new certificate. We are pushing an update in coming days to fix this.

      To workaround:

      1. Go to domains view and add a new domain called example.com (sic) with the No-op provider
      2. Remove the example.com domain

      The above process will update the mail container with the correct certificate. Let me know if that works (or not!)

      1 Reply Last reply
      1
      • BounzB Offline
        BounzB Offline
        Bounz
        wrote on last edited by
        #3

        Yes, this did the trick, thank you!

        1 Reply Last reply
        0
        • T Offline
          T Offline
          tadeas
          wrote on last edited by
          #4

          Had this happen as well. Thanks for fixing in future versions.

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Bookmarks
          • Search