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


Skip to content

Support

Get help for your Cloudron

2.5k Topics 17.6k Posts
  • 1 Votes
    3 Posts
    86 Views
    O

    Thanks for the reply. I just doubled from 15 to 30. Lets see if this helps.

  • 2 Votes
    8 Posts
    245 Views
    E

    I'll give it a try. Thank you very much for your help and explanations. đź‘Ť

  • Restoring

    Solved
    3
    1 Votes
    3 Posts
    59 Views
    girishG

    @mdc773 yes. next time around, you can download the backup config that prefills all this - https://docs.cloudron.io/backups/#restore-cloudron

  • Postmark outbound integration

    Solved
    14
    0 Votes
    14 Posts
    268 Views
    C

    @girish Nice. Wish Cloudron could fix all the other mistakes I make.

  • your friend and mine, DMARC

    Solved
    8
    1 Votes
    8 Posts
    180 Views
    bmannB

    Yes I have DKIM setup. Thanks for the “relaxed” incantation. I’ll try that.

  • 1 Votes
    6 Posts
    109 Views
    jdaviescoatesJ

    @girish said in resolvconf failed by Install to Cloudron:

    Did I understand correctly, that cloudron-setup is failing and that the error you posted is from /var/log/cloudron-setup.log ? What's the log lines before the error ? See if you can fix those errors manually and run cloudron-setup --redo .

    It's not me this time, but I've hit this before yes cloudron-setup does not work at all on Netcup VPS vServers because they are running some custom minimized version of Ubuntu.

    See also this previous thread https://forum.cloudron.io/post/74252

    Netcup said on Twitter they would look into it here https://twitter.com/netcup/status/1711394283347960098 but presumably they haven't fixed it.

  • Backup failed

    Unsolved
    6
    2 Votes
    6 Posts
    231 Views
    archosA

    @d19dotca I also suspect it's a problem with the iDrive storage. Because the backup problem is not a regular one. If he writes to iDrive support please let me know.

  • Using Cloudron Behind a Reverse Proxy

    Solved
    2
    1 Votes
    2 Posts
    122 Views
    girishG

    For these kind of setups, it's easiest if you use one of the automated DNS options (i.e not manual or wildcard).

    Setup service1.domain.tld as one of the automated DNS options. Not sure where domain.tld is already hosted but it's not one of the options we support, you can always create a zone called service1.domain.tld and put host the zone is one of the DNS services. In your proxy, forward https://service1.domain.tld AND ``https://*.service1.domain.tld` (hope it supports wildcard) to Cloudron VM.

    It should work with valid certs with the above setup.

  • Having issues with unbound again

    Solved
    4
    0 Votes
    4 Posts
    75 Views
    girishG

    @genies305 you can just email us at support@cloudron.io

  • Cloudron update failing

    Solved
    20
    0 Votes
    20 Posts
    802 Views
    girishG

    To close the thread here, the issue was simply that update to 7.5 was failing because @squareclouds 's cloudron is still on ubuntu 18 . One must upgade to Ubuntu 20 first before updating to 7.5.

  • Draw 2.0 stuck on Starting...

    Solved
    8
    0 Votes
    8 Posts
    118 Views
    timconsidineT

    Yay !
    Screenshot 2023-11-01 at 17.10.55.png

  • PTR record on AWS EC2

    Solved
    4
    1 Votes
    4 Posts
    139 Views
    G

    @girish Ha ok, makes sense, will try setting up the relay and update the thread. Thx!

  • 1 Votes
    6 Posts
    205 Views
    C

    @girish Thank you. Your solution did the trick.
    But we needed the ipv6 to be functional.
    So what we did to make it work was > reinstall Ubuntu 22.04 LTS OS and didn't install unbound in advance. All is good now.

  • File and Folder Ownership in /yellowtent/boxdata

    Solved
    6
    0 Votes
    6 Posts
    92 Views
    M

    Okay, I figured out what my problem was.

    I had some failed backups from yesterday, when I tried to get hardlinking working (and I also had a permission issue with the MySQL dump). As of such, I cleared the backup disk manually, and then triggered a backup cleanup in the Cloudron UI. Then I tried to back up again, however, I believe that Cloudron keeps an index of files it has already backed up to keep things speedy (which is nice). As of such, even though the other files no longer existed, it was only backing up the changes.

    To solve it, I just changed the backup method to a different method, and then changed it back again, which cleared the index.

    Thanks for all your help on this :).

  • 0 Votes
    8 Posts
    251 Views
    M

    @d19dotca said in Backup to ext4 disk mount, using rsync, fails on first full backup but succeeds in all future ones.:

    Setup a new public cloud instance at OVH
    Create a block storage disk and attach it to the public instance created in step 1
    Format the block storage disk and mount it according to this article: https://docs.ovh.com/ca/en/public-cloud/create_and_configure_an_additional_disk_on_an_instance/#using-linux
    Install and restore Cloudron from old server via DigitalOcean Spaces latest Cloudron backup ID
    Once Cloudron is running off latest backup, change backup configuration to file system using rsync non-encrypted with hardlinks, then initiate the first backup to the new location. This is where it failed for me.

    Hey, I know this is quite old, but I just had this issue too (v7.4.3), and I think I know what the issue is.

    So the Backup type is 'Filesystem (Mountpoint). Cloudron tries to hardlink between one device (primary boot, or one particular mountpoint) and the other (another mountpoint). Hardlinking isn't supported between devices sometimes though, so the hardlink fails.

    This issue seems to occur even with encryption though.

    Just a heads up in case anybody runs into this issue.

    Solution in the main time is to just not use hardlinks.

  • 1 Votes
    5 Posts
    143 Views
    C

    @girish I am just finding this thread. I would suggest adding these options:
    { name: '7 daily, 4 weekly, 3 monthly', value: { keepDaily: 7, keepWeekly: 4, keepMonthly: 3 }},
    { name: '7 daily, 4 weekly, 6 monthly', value: { keepDaily: 7, keepWeekly: 4, keepMonthly: 6 }},

    The first option is a common backup cycle (I think) and the second option allows for 3 more months of retention (and is halfway between the first and the current 12 month option).

  • Upgrade Netcup to Ubuntu 22.04

    Moved Solved
    14
    2 Votes
    14 Posts
    602 Views
    nebulonN

    This then means, that the system is using cgroups v2 now. I have updated the main docs section at https://docs.cloudron.io/packaging/cheat-sheet/#memory-limit for a start to make an app compatible with cgroup v1 and v2 (I guess in your case its sufficient to only support v2 now.)

  • Reinstall cloudron on another VPS from tar.gz backup file

    Solved
    5
    1 Votes
    5 Posts
    90 Views
    Q

    Thanks ! It's working ! 🙂

  • How to debug Cloudron directory server?

    Solved
    10
    1 Votes
    10 Posts
    358 Views
    fbartelsF

    @andreasdueren i think I just followed their documentation: https://goauthentik.io/docs/providers/ldap/generic_setup

  • cloudron-syslog.service Failed

    Solved
    14
    1 Votes
    14 Posts
    96 Views
    M

    Hey all, reinstalled and then did a restore to fix things. Had a few trouble with restore, but was able to work them out. Also wrote a quick rsync command to take the emails from lost+found and restore them to their proper directories, so no emails lost :).