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
M-arcusM

M-arcus

@M-arcus
About
Posts
46
Topics
11
Shares
0
Groups
0
Followers
2
Following
3

Posts

Recent Best Controversial

  • Cloudron not reachable after 7.0.1 Update & Reboot
    M-arcusM M-arcus

    @schnyd said in Cloudron not reachable after 7.0.1 Update & Reboot:

    @m-arcus I had the same issue this morning. Somehow after the update all my disk space was being used crashing the server. I had to roll my VPS back to a backup from a week ago.

    Yes, same issue with the space. I deleted all my backups and restarted the server. Then everything stopped working. I wonder why so much space got used, I disabled all app backups.

    @girish said in Cloudron not reachable after 7.0.1 Update & Reboot:

    @m-arcus When you say cannot access, do you mean the dashboard says as "offline" ? What do you see in the logs - /home/yellowtent/platformdata/logs/box.log ?

    It straight up refused to connect. I fixed it by deleting all backups (for space), executing docker kill $(docker ps -q) and then /home/yellowtent/box/setup/start.sh

    Support

  • Cloudron not reachable after 7.0.1 Update & Reboot
    M-arcusM M-arcus

    I logged into my cloudron, it told me to reboot, I clicked the button, and it rebooted.
    Now I can't access it any more via browser.

    Support

  • Update to v6.3.4 (Ubuntu 20.04.2 LTS) fails
    M-arcusM M-arcus

    @girish @nebulon
    I did not follow the upgrade tutorial for 16.04 → 18.04 → 20.04 entirely because I have some minor adjustments on the server that were blocking the upgrade. Also, there was a minor issue with docker in the past, where I edited the file /etc/apt/sources.list.d/docker.list so this whole problem was my fault 🙂

    Support update install installation

  • Update to v6.3.4 (Ubuntu 20.04.2 LTS) fails
    M-arcusM M-arcus

    It was 20.10.3, i had 20.10.7 installed.

    I executed:

    curl -sL "https://download.docker.com/linux/ubuntu/dists/focal/pool/stable/amd64/containerd.io_1.4.3-1_amd64.deb" -o /tmp/containerd.deb
    curl -sL "https://download.docker.com/linux/ubuntu/dists/focal/pool/stable/amd64/docker-ce-cli_20.10.3~3-0~ubuntu-focal_amd64.deb" -o /tmp/docker-ce-cli.deb
        curl -sL "https://download.docker.com/linux/ubuntu/dists/focal/pool/stable/amd64/docker-ce_20.10.3~3-0~ubuntu-focal_amd64.deb" -o /tmp/docker.deb
    apt install -y --allow-downgrades /tmp/containerd.deb  /tmp/docker-ce-cli.deb /tmp/docker.deb
    

    and then rebooted. Now it's installing the update to 6.3.5.

    Maybe there should be --allow-downgrades option in the cloudron box installer script

    Support update install installation

  • Update to v6.3.4 (Ubuntu 20.04.2 LTS) fails
    M-arcusM M-arcus

    @nebulon @girish
    To what version?

    I updated the server to 20.04 from 16.04 a month ago

    Support update install installation

  • Update to v6.3.4 (Ubuntu 20.04.2 LTS) fails
    M-arcusM M-arcus

    @girish said in Update to v6.3.4 (Ubuntu 20.04.2 LTS) fails:

    /home/yellowtent/platformdata/logs/updater/cloudron-updater-2021-08-10_08-42-37.log

    WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
    
    Reading package lists...
    Building dependency tree...
    Reading state information...
    The following packages were automatically installed and are no longer required:
      btrfs-progs docker-scan-plugin libargon2-0 linux-image-4.15.0-147-generic
      linux-modules-4.15.0-147-generic linux-modules-extra-4.15.0-147-generic
    Use 'apt autoremove' to remove them.
    Suggested packages:
      aufs-tools cgroupfs-mount | cgroup-lite
    Recommended packages:
      docker-ce-rootless-extras
    The following packages will be DOWNGRADED:
      containerd.io docker-ce docker-ce-cli
    0 upgraded, 0 newly installed, 3 downgraded, 0 to remove and 37 not upgraded.
    E: Packages were downgraded and -y was used without --allow-downgrades.
    2021-08-11T08:35:17 ==> installer: Failed to install docker. Retry
    
    Support update install installation

  • Update to v6.3.4 (Ubuntu 20.04.2 LTS) fails
    M-arcusM M-arcus

    @girish

    2021-08-10T08:42:37.896Z box:shell update (stdout): => Run installer.sh as cloudron-updater.
    
    2021-08-10T08:42:37.917Z box:shell update (stdout): => starting service (ubuntu 18.04) cloudron-updater. see logs at /home/yellowtent/platformdata/logs/updater/cloudron-updater-2021-08-10_08-42-37.log
    
    2021-08-10T08:42:37.934Z box:shell update (stdout): Failed to start transient service unit: Unit cloudron-updater.service already exists.
    
    2021-08-10T08:42:37.936Z box:shell update (stdout): Failed to install cloudron. See log for details
    
    Support update install installation

  • Update to v6.3.4 (Ubuntu 20.04.2 LTS) fails
    M-arcusM M-arcus

    Hello,

    the update to v6.3.5 fails when executed in the "Settings" view and the Automatic Update at 3am (it gets stuck at installing then).

    The log output is:

    Aug 10 10:42:27 box:locker Acquired : box_update
    Aug 10 10:42:27 box:tasks startTask - starting task 6847 with options {"timeout":72000000,"nice":15,"memoryLimit":1024}. logs at /home/yellowtent/platformdata/logs/tasks/6847.log
    Aug 10 10:42:27 box:shell startTask spawn: /usr/bin/sudo -S -E /home/yellowtent/box/src/scripts/starttask.sh 6847 /home/yellowtent/platformdata/logs/tasks/6847.log 15 1024
    Aug 10 10:42:27 box:shell startTask (stdout): Running as unit: box-task-6847.service
    Aug 10 10:42:37 box:shell startTask (stdout): Finished with result: exit-code
    processes terminated with: code=exited/status=50
    runtime: 10.064s
    Aug 10 10:42:37 box:shell startTask code: 50, signal: null
    Aug 10 10:42:37 box:tasks startTask: 6847 completed with code 50 and signal null
    Aug 10 10:42:37 box:locker Released : box_update
    Aug 10 10:42:37 box:updater Update failed with error {
    stack: 'BoxError: update exited with code 1 signal null\n' +
    ' at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:74:17)\n' +
    ' at ChildProcess.emit (events.js:315:20)\n' +
    ' at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)',
    name: 'BoxError',
    reason: 'Spawn Error',
    details: {},
    message: 'update exited with code 1 signal null',
    code: 1,
    signal: null
    Aug 10 10:42:37 box:tasks startTask: 6847 done
    

    journalctl -f output:

    Aug 10 08:42:37 my.domain.com systemd[1]: box-task-6847.service: Main process exited, code=exited, status=50/n/a
    Aug 10 08:42:37 my.domain.com systemd[1]: box-task-6847.service: Failed with result 'exit-code'.
    

    I tried to reboot, update all other boxes, execute apt -f install, dpkg --configure -a, restart the box by systemctl restart box and /home/yellowtent/box/setup/start.sh, sadly nothing worked.

    When executing apt -f install there was a lock problem though, but deleting the lock didn't help either:

     apt -f install
    Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 216171 (apt)      
    Reading package lists... Done                                                                             
    Building dependency tree       
    Reading state information... Done
    The following packages were automatically installed and are no longer required:
      btrfs-progs libargon2-0 linux-image-4.15.0-147-generic linux-modules-4.15.0-147-generic linux-modules-extra-4.15.0-147-generic
    Use 'apt autoremove' to remove them.
    0 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
    

    What are other possible solutions?

    Support update install installation

  • shopware - eCommerce business solution
    M-arcusM M-arcus

    Maybe this can be used for the development of this app
    https://github.com/shopwareLabs/shopware-docker

    App Wishlist

  • Graphs are empty
    M-arcusM M-arcus

    I found the problem: Screenshot-20190731144259-690x46.png

    Container graphite was always max. 75MB memory limit.
    I increased it to 256, then it worked without problem.

    Support graphs

  • my.domain.tld tries to pull cert from another-domain-on-this-cloudron.com
    M-arcusM M-arcus

    I found a few from 2017, deleted them with rm -rf 2017-* inside the backups folder.

    Support

  • Graphs are empty
    M-arcusM M-arcus

    When I try to load a graph it just shows some empty areas. Any ideas where i can start looking for a solution?
    empty graph

    Support graphs

  • my.domain.tld tries to pull cert from another-domain-on-this-cloudron.com
    M-arcusM M-arcus

    This disk space was full. I fixed it thanks to @nebulon instructions.

    I'm curious about how this happened. the backup folder is very big despite only 4 avaiable backups per app

    Support

  • my.domain.tld tries to pull cert from another-domain-on-this-cloudron.com
    M-arcusM M-arcus

    Is it safe to run sudo apt autoremove on cloudron servers?

    Support

  • my.domain.tld tries to pull cert from another-domain-on-this-cloudron.com
    M-arcusM M-arcus

    If i disable web-security in chrome, it redirects me from my.domain.tld to another-domain-on-this-cloudron.com.

    Support

  • my.domain.tld tries to pull cert from another-domain-on-this-cloudron.com
    M-arcusM M-arcus

    I rebooted the server and after that I couldn't connect to it anymore.

    domain.tld (works)
    aaa.domain.tld, bbb.domain.tld and my.domain.tld don't work

    How can i fix this?

    Support

  • Grav - CMS that requires no database
    M-arcusM M-arcus

    +1

    I tried it on the LAMP App, installation time: 30 secs

    This is amazing

    cd public/
    wget https://github.com/getgrav/grav/releases/download/1.5.7/grav-admin-v1.5.7.zip
    unzip grav-admin-v1.5.7.zip
    rm grav-admin-v1.5.7.zip
    mv grav-admin/* grav-admin/.[!.]* .
    chown -Rf www-data:www-data .
    
    App Wishlist

  • LAMP App - How to enable mod_expires.c ?
    M-arcusM M-arcus

    A bunch of mods are already installed, but not activated.

    I would separate this into:

    • Activating already installed mods
    • Installing and activating new monds
    LAMP lamp

  • LAMP App - How to enable mod_expires.c ?
    M-arcusM M-arcus

    @girish Thanks for the quick update.

    Maybe you can symlink the apache2 folder to a writable folder inside /app

    LAMP lamp

  • LAMP App - How to enable mod_expires.c ?
    M-arcusM M-arcus

    I am trying to enable the expires module for apache2.

    But if I try to do it via /app/data/run.sh or via the repair-mode, it tells me that the Apache2 mod folder is read-only.

    How do I enable this module?

    LAMP lamp
  • Login

  • Don't have an account? Register

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