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


Navigation

    Cloudron Forum

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

    Cloudron 2.1 released

    Announcements
    2
    7
    836
    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.
    • girish
      girish Staff last edited by

      2.1 is now available for all. You can read more in our blog post

      Highlights:

      • We have reworked how mailboxes work. Mailboxes and aliases can now be managed in the email view. All Cloudron subscription plans include unlimited mailboxes and aliases.
      • Initial support for installation for apps from private a docker registries like Amazon ECR, quay.io.
      1 Reply Last reply Reply Quote 0
      • girish
        girish Staff last edited by girish

        Known issues:

        • (only multi-domain email setups) If there was an alias in one domain with name say 'foobar' and a mailbox in another domain with the same name 'foobar', then the migration code sometimes imports the mailbox of the second domain incorrectly as an 'alias' instead of a 'mailbox'. If you encounter this issue, please contact us at support@cloudron.io (and enable ssh access). We have to patch up the DB by hand. Note that the mail server itself is running fine and there is no issue sending/receiving email. Just that the db entry is wrong which causes authentication to fail.
        1 Reply Last reply Reply Quote 1
        • girish
          girish Staff last edited by girish

          We have a few Cloudrons that are failing to update because the disk is full for apt to work. A possible reason is that the many kernel updates pushed by the VPS providers for spectre/meltdown did not completely work.

          First check if sudo du -hcs /var/tmp has lots of data. Or check if /boot is full using df -h /boot. If /boot is full, you have to manually remove some of the old kernels:

          root@my:/boot# uname -nar
          Linux my.cloudron 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
          root@my:/boot# rm initrd.img-4.4.0-101-generic initrd.img-4.4.0-103-generic
          

          Now /boot should have some free space:

          apt -f install
          purge-old-kernels   # this removes old kernels and cleans up /boot
          rm -rf /var/tmp/mkinitramfs*
          dpkg --configure -a
          apt-get install
          apt autoremove
          

          Check if unbound is working:

          systemctl status unbound
          

          It must say active (running). If not, run the following commands:

          sudo unbound-anchor -a /var/lib/unbound/root.key
          sudo systemctl restart unbound
          
          1 Reply Last reply Reply Quote 0
          • V
            vnr last edited by

            Hello

            This dosen't Works for me.
            i can't update from 2.0.1 to 2.1.0

            the update process remains at "Downloading and installing new version"
            i am using Ubuntu Server 16.04.3 LTS

            Please Help

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

              @vnr Can you check journalctl -fa logs?

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

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • girish
                  girish Staff last edited by girish

                  We have another issue related to docker not upgrading because of unmet deps.

                  Check journalctl -fa and if it shows something like below over and over again:

                  The following packages have unmet dependencies:
                   docker-ce : Depends: libseccomp2 (>= 2.3.0) but 2.2.3-3ubuntu3 is to be installed
                  E: Unable to correct problems, you have held broken packages.
                  

                  To fix:

                  apt update
                  

                  You might have to run the above command a couple of times since it might says it cannot get the lock. Once the update is done, it should update automatically.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post