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
  • 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 | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Let's Encrypt Didn't seem to auto-renew

Let's Encrypt Didn't seem to auto-renew

Scheduled Pinned Locked Moved Solved Support
letsencryptcertificates
39 Posts 17 Posters 9.9k Views 15 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.
  • J Offline
    J Offline
    jk
    wrote on last edited by jk
    #8

    I had a similar issue: the certificate was actually renewed (as evidenced by crt.sh), but the old one expired today, causing certificate errors on my website.

    Restarting the app fixed that, but that should happen automatically after renewal, I think.

    In case it matters, I was using the Surfer app (io.cloudron.surfer@5.17.8), on Cloudron v7.3.4 (Ubuntu 18.04.4 LTS)

    1 Reply Last reply
    0
    • stumitchellS Offline
      stumitchellS Offline
      stumitchell
      wrote on last edited by
      #9

      I had the same issue had to restart cloudtron (incognito mode works to get you in). Then restart the apps

      1 Reply Last reply
      0
      • scookeS Offline
        scookeS Offline
        scooke
        wrote on last edited by
        #10

        Wouldn't you know it, I also had a similar issue recently - went to an app and suddenly it wouldn't load. A bunch of others too. I didn't know the trick that @humptydumpty shared, so I just pressed the button on the main Domain tab on the Dashboard to renew ALL the certs, and suddenly more weren't loading. I checked the logs, and I had a domain in there that didn't have an AAAA record, and was thus stalling ALL the renewals. The thing is, I'm certain many of the other domains also don't have an AAAA record. Maybe because the one in question is an IDN? Anyways, I figured out the IPv6 address and made a new AAAA record, and voila! Everything is back to normal.

        A life lived in fear is a life half-lived

        1 Reply Last reply
        0
        • R Ropyro

          Hi Everyone ---

          I received an automated email on Jan 6 telling me to renew my Let's Encrypt certificate. I ignored it because it has always auto-renewed. It didn't. And, on the 13th, I found myself unable to connect to Cloudron/Apps. I don't know what to do from here. Any idea why it didn't auto-renew and what I can do to move forward?

          Thanks very much!

          BrutalBirdieB Offline
          BrutalBirdieB Offline
          BrutalBirdie
          Partner
          wrote on last edited by
          #11

          @staff
          @nebulon you remember? I had the same issue with multiple Cloudron servers.

          Okay, check if your Cloudron is still running Ubuntu 18.X.
          If so check the box.service for errors, if there is an error with the note of:

          Jan 09 17:15:00 ubuntu-2gb-fsn1-2 systemd[1]: Reload failed for Cloudron Admin.
          Jan 09 17:15:03 ubuntu-2gb-fsn1-2 sudo[30793]: pam_unix(sudo:session): session opened for user root by (uid=0)
          Jan 09 17:15:04 ubuntu-2gb-fsn1-2 systemd[1]: Reloading Cloudron Admin.
          Jan 09 17:15:04 ubuntu-2gb-fsn1-2 sudo[30793]: pam_unix(sudo:session): session closed for user root
          Jan 09 17:15:09 ubuntu-2gb-fsn1-2 systemd[30858]: box.service: Failed to execute command: No such file or directory
          Jan 09 17:15:09 ubuntu-2gb-fsn1-2 systemd[30858]: box.service: Failed at step EXEC spawning /usr/bin/kill: No such file or directory
          Jan 09 17:15:09 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Control process exited, code=exited status=203
          Jan 09 17:15:09 ubuntu-2gb-fsn1-2 systemd[1]: Reload failed for Cloudron Admin.
          

          On Ubuntu 18 it seems there is no /usr/bin/kill just /bin/kill then also check your /home/yellowtent/platformdata/CRON_SEED
          The first int is the hour of the day.
          Mine was 16:8 with the 1 hour diff of wrong timezone this matched up to the box crash.

          Also please check if the renew log has anything inside, for me it was total empty.


          So to everyone having this issue, please report if you are using Ubuntu 18 and if so your box.service has the same error.

          Like my work? Consider donating a drink. Cheers!

          nebulonN 1 Reply Last reply
          3
          • BrutalBirdieB BrutalBirdie

            @staff
            @nebulon you remember? I had the same issue with multiple Cloudron servers.

            Okay, check if your Cloudron is still running Ubuntu 18.X.
            If so check the box.service for errors, if there is an error with the note of:

            Jan 09 17:15:00 ubuntu-2gb-fsn1-2 systemd[1]: Reload failed for Cloudron Admin.
            Jan 09 17:15:03 ubuntu-2gb-fsn1-2 sudo[30793]: pam_unix(sudo:session): session opened for user root by (uid=0)
            Jan 09 17:15:04 ubuntu-2gb-fsn1-2 systemd[1]: Reloading Cloudron Admin.
            Jan 09 17:15:04 ubuntu-2gb-fsn1-2 sudo[30793]: pam_unix(sudo:session): session closed for user root
            Jan 09 17:15:09 ubuntu-2gb-fsn1-2 systemd[30858]: box.service: Failed to execute command: No such file or directory
            Jan 09 17:15:09 ubuntu-2gb-fsn1-2 systemd[30858]: box.service: Failed at step EXEC spawning /usr/bin/kill: No such file or directory
            Jan 09 17:15:09 ubuntu-2gb-fsn1-2 systemd[1]: box.service: Control process exited, code=exited status=203
            Jan 09 17:15:09 ubuntu-2gb-fsn1-2 systemd[1]: Reload failed for Cloudron Admin.
            

            On Ubuntu 18 it seems there is no /usr/bin/kill just /bin/kill then also check your /home/yellowtent/platformdata/CRON_SEED
            The first int is the hour of the day.
            Mine was 16:8 with the 1 hour diff of wrong timezone this matched up to the box crash.

            Also please check if the renew log has anything inside, for me it was total empty.


            So to everyone having this issue, please report if you are using Ubuntu 18 and if so your box.service has the same error.

            nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #12

            @BrutalBirdie right that kill fix will be part only for next release, however we have by now also seen Cloudrons on Ubuntu 20 hitting a cert renew or reload issue. So its only part of the fix it seems.

            1 Reply Last reply
            1
            • humptydumptyH Offline
              humptydumptyH Offline
              humptydumpty
              wrote on last edited by humptydumpty
              #13

              I’m on v7.3.4 (Ubuntu 22.04.1 LTS), contabo vps, automated cloudflare dns w/ no proxying enabled.

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

                If anyone with this situation, can contact us on support@cloudron.io, I think we debug this further. I check around 20 servers we have access to but they seem to updating the certs just fine. Maybe some specific cert provider is having issues.

                jdaviescoatesJ J 2 Replies Last reply
                1
                • girishG girish

                  If anyone with this situation, can contact us on support@cloudron.io, I think we debug this further. I check around 20 servers we have access to but they seem to updating the certs just fine. Maybe some specific cert provider is having issues.

                  jdaviescoatesJ Offline
                  jdaviescoatesJ Offline
                  jdaviescoates
                  wrote on last edited by
                  #15

                  @girish fyi I hit this recently for a Wildcard DNS on 18.04. The Gandi API ones on the same server seemed to update fine.

                  I use Cloudron with Gandi & Hetzner

                  robiR 1 Reply Last reply
                  0
                  • jdaviescoatesJ jdaviescoates

                    @girish fyi I hit this recently for a Wildcard DNS on 18.04. The Gandi API ones on the same server seemed to update fine.

                    robiR Offline
                    robiR Offline
                    robi
                    wrote on last edited by
                    #16

                    @jdaviescoates that's a good pivoting data point @jdaviescoates , mine is a wildcard setup too. Likely something specific to that branch of code..

                    Conscious tech

                    jdaviescoatesJ 1 Reply Last reply
                    1
                    • robiR robi

                      @jdaviescoates that's a good pivoting data point @jdaviescoates , mine is a wildcard setup too. Likely something specific to that branch of code..

                      jdaviescoatesJ Offline
                      jdaviescoatesJ Offline
                      jdaviescoates
                      wrote on last edited by
                      #17

                      @robi I thought so too, but this has just happened to me on one of my Gandi LiveDNS domains on a Cloudron running on Ubuntu 20.04 too šŸ¤”

                      I use Cloudron with Gandi & Hetzner

                      1 Reply Last reply
                      0
                      • girishG girish

                        If anyone with this situation, can contact us on support@cloudron.io, I think we debug this further. I check around 20 servers we have access to but they seem to updating the certs just fine. Maybe some specific cert provider is having issues.

                        J Offline
                        J Offline
                        jagan
                        wrote on last edited by
                        #18

                        @girish Had this issue too. Will drop a mail later today.

                        1 Reply Last reply
                        1
                        • nebulonN nebulon referenced this topic on
                        • njN Offline
                          njN Offline
                          nj
                          wrote on last edited by nj
                          #19

                          I can confirm the issue. Certificate of other domains added to Cloudron aren't renewed. Primary domain seems to be renewed.

                          Some certs are due 4 days. 😮 Good thing I had alerts enabled so I got notified.

                          2f6b3f74-ce0c-4ddf-bac4-4dca395a8632-image.png

                          Domain provider is Wildcard. Both domain.tld and *.domain.tld point to the cloudron (since last 1-2 years).
                          f20cc3d1-3cd4-4e52-a02f-95a3a86b98fa-image.png

                          Renew all Certs shows "Configuring apps .. or something" and the progressbar disappears.

                          • "Show Logs" shows empty window.
                          • Download full logs -> 1 byte empty file

                          d1075490-634d-4d81-8d00-8cf47bb2ce1e-image.png

                          Founder / Coder • My Apps

                          girishG 1 Reply Last reply
                          0
                          • njN nj

                            I can confirm the issue. Certificate of other domains added to Cloudron aren't renewed. Primary domain seems to be renewed.

                            Some certs are due 4 days. 😮 Good thing I had alerts enabled so I got notified.

                            2f6b3f74-ce0c-4ddf-bac4-4dca395a8632-image.png

                            Domain provider is Wildcard. Both domain.tld and *.domain.tld point to the cloudron (since last 1-2 years).
                            f20cc3d1-3cd4-4e52-a02f-95a3a86b98fa-image.png

                            Renew all Certs shows "Configuring apps .. or something" and the progressbar disappears.

                            • "Show Logs" shows empty window.
                            • Download full logs -> 1 byte empty file

                            d1075490-634d-4d81-8d00-8cf47bb2ce1e-image.png

                            girishG Offline
                            girishG Offline
                            girish
                            Staff
                            wrote on last edited by
                            #20

                            @nj the logs thing is fixed in 7.3.5. Can you update and check?

                            But there is still the underlying problem of certs not renewing sometimes with 7.3.

                            jordanurbsJ 1 Reply Last reply
                            0
                            • girishG girish

                              @nj the logs thing is fixed in 7.3.5. Can you update and check?

                              But there is still the underlying problem of certs not renewing sometimes with 7.3.

                              jordanurbsJ Offline
                              jordanurbsJ Offline
                              jordanurbs
                              wrote on last edited by
                              #21

                              Also having this issue for several domains on my cloudron.

                              Manually renewing all certs, restarting apps, deleting browser cookies, nothing is fixing it.

                              My cloudron is on Ubuntu 20

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

                                Wanted to update this thread. We found the issue, we will make a release with a fix (7.3.6) asap.

                                jaschaezraJ 1 Reply Last reply
                                11
                                • girishG girish

                                  Wanted to update this thread. We found the issue, we will make a release with a fix (7.3.6) asap.

                                  jaschaezraJ Offline
                                  jaschaezraJ Offline
                                  jaschaezra
                                  wrote on last edited by
                                  #23

                                  @girish Thank you! I just came to report the same issue and was delighted that already had been taking care of! Great work!

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

                                    7.3.6 is out now which should fix this, rolling out slowly.

                                    humptydumptyH 1 Reply Last reply
                                    0
                                    • girishG girish marked this topic as a question on
                                    • girishG girish has marked this topic as solved on
                                    • girishG girish

                                      7.3.6 is out now which should fix this, rolling out slowly.

                                      humptydumptyH Offline
                                      humptydumptyH Offline
                                      humptydumpty
                                      wrote on last edited by humptydumpty
                                      #25

                                      @girish I know updates are rolled out alphabetically but is it based on the installed subdomain (ex: rambo.domain.com) or the bare domain?

                                      girishG 1 Reply Last reply
                                      0
                                      • humptydumptyH humptydumpty

                                        @girish I know updates are rolled out alphabetically but is it based on the installed subdomain (ex: rambo.domain.com) or the bare domain?

                                        girishG Offline
                                        girishG Offline
                                        girish
                                        Staff
                                        wrote on last edited by girish
                                        #26

                                        @humptydumpty iirc, it's on the primary domain i.e installed subdomain.

                                        jdaviescoatesJ 1 Reply Last reply
                                        1
                                        • girishG girish

                                          @humptydumpty iirc, it's on the primary domain i.e installed subdomain.

                                          jdaviescoatesJ Offline
                                          jdaviescoatesJ Offline
                                          jdaviescoates
                                          wrote on last edited by
                                          #27

                                          @girish that isn't very clear! šŸ˜›

                                          I think it's surely based on the domain name used for my.domain.tld, no?

                                          i.e.

                                          my.aaaaa.tld gets updated before
                                          my.bbbbb.tld
                                          ....
                                          my.zzzzz.tld

                                          That's been my experience anyway.

                                          I use Cloudron with Gandi & Hetzner

                                          girishG 1 Reply Last reply
                                          0
                                          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