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


Skip to content
  • Updates not found on the instance ?

    Solved Support
    3
    1 Votes
    3 Posts
    42 Views
    J

    I can confirm.Thank you!

  • 1 Votes
    3 Posts
    60 Views
    C

    @girish Thanks for the complete and thorough explanation. I guess I was fooled by the apt update I saw in one of your docker image definitions (thinking that others would be following your best practice). If you are comfortable with the risk/reward balance then I am comfortable:)

  • 0 Votes
    19 Posts
    862 Views
    L

    Can confirm that the update to Immich v1.91.4 is going well.

    If you are running Immich, just think about how much work and time and effort Cloudron has saved us by supporting this application. No headaches. Just one-click.

    Thank you so much for Cloudron!

  • 4 Votes
    1 Posts
    88 Views
    No one has replied
  • 2 Votes
    1 Posts
    49 Views
    No one has replied
  • 1 Votes
    5 Posts
    165 Views
    jegillikin 0J

    FWIW, I just upgraded from Ubuntu 18 this evening. Cloudron's documentation from going from 18 to 20 was quite helpful, re: a collectd edit that I never would have thought to make, plus the specific MySQL Server migration rules. Everything went smoothly, but without the documentation, it wouldn't have. So kudos to the team.

  • 5 Votes
    41 Posts
    859 Views
    mhgcicM

    @jdaviescoates said in Cloudron update to 7.5.1 - Success!:

    @mhgcic said in Cloudron update to 7.5.1 - Success!:

    I could increase the RAM to see if that helps.

    Regardless if it is what's causing the issues you're currently facing, I'd definitely get more RAM if I were you.

    Each instance of Mastodon needs at least 1.5GB and each instance of Discourse at least 2GB. Already that is at least 10.5GB RAM you need before you've included all your other apps plus Cloudron and Ubuntu themselves.

    And these are bare minimums. If you have users actually actively using these apps they'll need more.

    We know this and monitor daily, and we have software that lets us know that RAM needs to be increased whether it is on a server level or on an app level.

    We upgrade as and when needed, We also use throttling so if extra RAM or CPU is needed it is given until we decide on its upgrade needs.

    After testing it had nothing to do with CPU or RAM it seems to be networking or a service possibly.

  • 1 Votes
    9 Posts
    162 Views
    iamthefijI

    I got everything working now by skipping some updates, finding a problematic one and debugging it a bit. I'm leaving a message I was going to send mid debugging before I managed to get it working just in case anyone else comes across the same issue.

    I got it working by skipping versions until I got to one that wouldn't apply. It was v4.41.0. It would run but the database migration would never connect to MySQL. This happened even after I got to the version just before and tried to apply it a few times.

    While I was debugging I found that the MySQL connection wouldn't work from the Terminal. Then I put the app into recovery to debug further. It MySQL worked in the Terminal there, so I turned off recovery mode and it booted just fine! Not sure what the root issue was though. Unusual that I was able to reproduce it but then it kind of resolved itself. Maybe switching to or from recovery resets some value causing an issue. I'm not sure.

    Original message:

    So, this is now pretty specific to Ghost. I've made it up to v4.40.2 just fine, but when I apply the next version v4.41.0, Ghost fails to start.

    The log shows

    Jul 11 14:39:18 ==> Start ghost Jul 11 14:39:18 ==> Clear potential migration lock Jul 11 14:39:18 mysql: [Warning] Using a password on the command line interface can be insecure. Jul 11 14:39:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:39:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:39:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:39:50 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:10 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:50 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:10 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:32 json: updated "/app/data/config.production.json" in-place Jul 11 14:41:32 json: updated "/app/data/config.production.json" in-place Jul 11 14:41:32 json: updated "/app/data/config.production.json" in-place Jul 11 14:41:32 ===> Copy frotend/public folder for asset generation Jul 11 14:41:32 ==> Loading /app/data/env for potential overrides Jul 11 14:41:32 ==> Ensure permissions Jul 11 14:41:32 ==> Migrating database Jul 11 14:41:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:44 [2023-07-11 21:41:44] ERROR Invalid database host. Jul 11 14:41:44 Jul 11 14:41:44 Invalid database host. Jul 11 14:41:44 Jul 11 14:41:44 "Please double check your database config." Jul 11 14:41:44 Jul 11 14:41:44 Error ID: Jul 11 14:41:44 500 Jul 11 14:41:44 Jul 11 14:41:44 Error Code: Jul 11 14:41:44 DATABASE_CREATION_FAILED Jul 11 14:41:44 Jul 11 14:41:44 ---------------------------------------- Jul 11 14:41:44 Jul 11 14:41:44 Error: connect ETIMEDOUT Jul 11 14:41:44 at /home/cloudron/ghost/versions/5.41.0/node_modules/knex-migrator/lib/database.js:134:19 Jul 11 14:41:44 at /home/cloudron/ghost/versions/5.41.0/node_modules/knex-migrator/lib/database.js:50:23 Jul 11 14:41:44 at Connection._handleTimeoutError (/home/cloudron/ghost/versions/5.41.0/node_modules/knex-migrator/node_modules/mysql2/lib/connection.js:202:17) Jul 11 14:41:44 at listOnTimeout (node:internal/timers:564:17) Jul 11 14:41:44 at process.processTimers (node:internal/timers:507:7)

    The diff for this version bump is here: https://git.cloudron.io/cloudron/ghost-app/-/commit/93e180df6ad9216f8f04480b9b60212816f86c28

    I've tried restoring my backup to v4.40.2 and re-applying multiple times but it continues to fail. It also fails if I use the CLI to skip this version and jump to the latest.

  • Updates failing (v7.3.6)

    Solved Support
    7
    0 Votes
    7 Posts
    60 Views
    girishG

    @robi instead of clickable, the logs are unified now into a single stream (similar to app logs).

  • 1 Votes
    5 Posts
    133 Views
    girishG

    tl;dr - If you have the above problem apt install python3-magic . Then, run apt update . On another server, unattended-upgrades package was missing as well (!) Not sure how because Cloudron installs it at install time. So, install it and run unattended-upgrade -d.

  • Apps Not Starting After Upgrade to 7.4.1

    Solved Support
    7
    0 Votes
    7 Posts
    212 Views
    R

    @nebulon Gotcha -- so it would have cleared up eventually, anyway. Well, thanks again. I really appreciate your support!

  • Nextcloud 26

    Solved Support
    2
    1 Votes
    2 Posts
    154 Views
    fbartelsF

    Hi @Thedurancode,

    the way apps are designed on Cloudron it is not possible to change any of the actual application code (and therefore you get the file permission errors). Instead you will either need to wait until Nextcloud 26 is generally available (you can check this post to check for the latest release) or you would need to fork the app code and perform the update there. The latter is easy to do if you are familar with Cloudron app development, but not really recommended for beginners (ihmo).

  • Best approach to updating Ghost to latest?

    Solved Support
    12
    0 Votes
    12 Posts
    201 Views
    tshirt-chihuahuT

    @girish 🤔 it seems the most recent update worked....while i did change some email settings, the only other action I took was manually bumping along the updates several versions. So there must have been some sort of inconsistent state that came up.

    It seems all is well with the world and no way to track down what happened.

    Thanks for the help, all.

  • 0 Votes
    19 Posts
    437 Views
    scookeS

    @jdaviescoates Phew, my thoughts and prayers worked!

  • 0 Votes
    9 Posts
    233 Views
    robiR

    @jdaviescoates you could set up a cron that gets usage info, and prints out a webpage you can monitor with Kuma for a keyword. When a threshold is met, you add/remove the keyword and fire off an alert via TG.

    Similar for monitoring something with change detection app or n8n workflow.

  • cloudron not working after update

    Solved Support
    3
    0 Votes
    3 Posts
    230 Views
    girishG

    The issue here was that unbound was not working. Because of that, all the docker image updates are failing like so:

    2022-12-06T03:38:02.801Z box:shell startGraphite exec: docker run --restart=always -d --name="graphite" --hostname graphite --net cloudron --net-alias graphite --log-driver syslog --log-opt syslog-address=udp://127.0.0.1:2514 --log-opt syslog-format=rfc5424 --log-opt tag=graphite -m 429916160 --memory-swap 536870912 --dns 172.18.0.1 --dns-search=. -p 127.0.0.1:2003:2003 -v "/home/yellowtent/platformdata/graphite:/var/lib/graphite" --label isCloudronManaged=true --read-only -v /tmp -v /run "cloudron/graphite:3.2.0@sha256:182e5cae69fbddc703cb9f91be909452065c7ae159e9836cc88317c7a00f0e62" Box GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 10.852 ms - 89 2022-12-06T03:38:03.581Z box:shell startGraphite (stdout): null 2022-12-06T03:38:03.581Z box:shell startGraphite (stderr): Unable to find image 'cloudron/graphite:3.2.0@sha256:182e5cae69fbddc703cb9f91be909452065c7ae159e9836cc88317c7a00f0e62' locally docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: server misbehaving. See 'docker run --help'.

    It was hard to figure why unbound is not working, all queries fail with ESERVFAIL (VM, Hyper-V, router, many things here). It's some networking related issue hard to diagnose without getting a full hand on the setup. The workaround was to add a file called /etc/unbound/unbound.conf.d/forward-everything.conf with the following:

    forward-zone: name: "." forward-addr: 1.1.1.1 forward-addr: 8.8.8.8

    Then, systemctl restart unbound . After that, host cloudron.io 127.0.0.1 should work.

    Finally, systemctl restart box will then bring up all the containers again.

  • 0 Votes
    124 Posts
    11k Views
    girishG

    See https://forum.cloudron.io/topic/8101/fix-for-kernel-bug-in-ubuntu-20-04-causing-various-issues for a solution.

  • How to skip updates to the latest update?

    Solved Support
    8
    0 Votes
    8 Posts
    206 Views
    humptydumptyH

    Cloudron won’t skip an update and will install them per your defined schedule. I have a shut down Wordpress app but temporarily keeping it for archiving purposes and I had to update it several times to get to the latest. I know from experience that WP won’t play nice if you skip updates (especially major version ones).

  • 2.8.10 security update available

    Solved Discourse
    6
    0 Votes
    6 Posts
    167 Views
    jdaviescoatesJ

    @nebulon thanks! I'm not getting my hopes up too far, but hopefully this will somehow also resolve all the issues that loads of the official plugins have when trying to install them on Cloudron...

  • 1 Votes
    3 Posts
    162 Views
    nebulonN

    @girish this has been reworked and will not explicitly state if there is no new update available, while hiding the disabled update button again.