Cloudron Forum

@umnz the package is unstable (and not the app itself) . unstable means we just packaged and released it . maybe we have to make some drastic changes to the package and break existing installations because we did something wrong.

I agree that it needs it's own category. cc @james

cc @nebulon @girish

Agreed, either the feature needs to change or the text . This change was made in Cloudron 9 - https://git.cloudron.io/platform/box/-/blob/master/CHANGES?ref_type=heads#L2959 .

I think Cloudron OIDC now exposes the avatar to apps and it's not a purely personal thing anymore since other user's will now see the avatar if the app supports it. This was the reason for the change iirc.

You mean the Lock profile option, correct? That also locks down the avatar. I think the idea of that option is that it locks down the profile so that your users don't attempt "goofy things" like setting some funny image as avatar or some funny name.

The mail relay requires STARTTLS - https://docs.cloudron.io/email/#relay-outgoing-mails . Is that enabled in Proxmox?

as in, you want the Cloudron dashboard to indicate that the app has it's own robots.txt ? That would be complicated given that an app can choose to handle paths however it wants. It's all dynamic.

The mail service seems running fine. But it seem like may be all non-http ports got blocked on your server (if you are unable to connect to SSH port and the Email ports) ? Did some new firewall deploy? Networking change?

@IniBudi said:

And my question is how to make the update process automatically from Cloudron dashboard?

Do you mean you want Cloudron to track upstream releases and make new packages and have an update available? If so, there is no such feature. An idea is to automate this in your CI (Cloudron team uses renovate for it's packages).

https://github.com/plankanban/planka/releases/tag/v2.2.0

There is a discussion at https://github.com/plankanban/planka/issues/1754

⚠️ Breaking changes — read before updating

1. OIDC/SSO has been removed from PLANKA Community.

    After updating, all SSO-based users are deactivated, because they no longer
    have a password login.
    An admin can restore access by setting a password for each affected user and
    reactivating them.
    If your only admin account is SSO-based, you will be locked out. Create a
    new admin user first (via script or environment variables) before updating:
    https://docs.planka.cloud/docs/configuration/admin-user
    If SSO is critical for your team, plan this migration before you update.
    Background and reasoning: #1754 · OIDC/SSO is now part of PLANKA Pro:
    https://planka.app/pro

Works here. Can you check the value with the instructions at https://forum.cloudron.io/topic/2969/how-can-i-increase-the-maximum-size-of-an-email-with-the-build-in-smtp/2 . Maybe try restarting mail server? Services -> Restart ?

hi @nozy i replied from support.

Using the backup should be straightforward . https://docs.cloudron.io/backups#move-cloudron-to-another-server is the necessary docs.

The license will automatically move, yes. (it moved with the domain name during migration and is not IP based)

Feel free to ask any question here and we can help.

Same I don't see the screenshots

@nckne correct, the restore process always starts from scratch. But there is a workaround.

Once the restore has failed, ssh into the server and edit the mysql dump directly. This file is /home/yellowtent/appsdata/<appid>/mysqldump . Specifically, from the error message it seems this is around line 2047. Maybe comment out that line?

After that, using the CLI tool (on your laptop and not on the server), run cloudron import --in-place --app humhub. This does a restore of the app without redownloading the backup. So, it will reimport your modified sql dump.

@nckne we don't even have a table named translator_cache . Could it be this comes from some module/plugin? Maybe you disabled it and afterwards may be migrations are not run ? Most likely it is because 8.4 MySQL is not accepting something that previous MySQL accepted.

@nckne I can check the schema in our HumbHub .

Update to 2.63.0 is blocked by https://github.com/kimai/kimai/issues/6102

@nckne sometimes you will find the import error in the Service -> MySQL logs . Can you check if you see anything there when importing?

Ha ha ok, I misunderstood @james it seems https://downloads.metabase.com/v0.63.5/metabase.jar is available , so we may have to create a manual MR .

I guess the question is how did you know it has a security issue (or how did your CEO know?) https://www.metabase.com/changelog/63 has no info on this release either .

Have you tried the raw link https://raw.githubusercontent.com/Tymeslot/tymeslot/refs/heads/main/CloudronVersions.json ?