Cloudron Forum

Hello,

I’m running Cloudron 10.0.4 on Ubuntu 24.04.4 LTS. I’m not receiving certain maintenance emails even though their notification categories were already enabled.

The dashboard bell shows:

• “Reboot required” to finish Ubuntu security updates.
• An EspoCRM manual package update to v3.0.0.

Both notices showed recent timestamps, but I couldn’t find corresponding recent emails in my primary Gmail mailbox, including Spam and Trash.

Checks completed:

• Confirmed the primary email address is correct.
• “Server reboot required” and “Platform or app requires manual update” email preferences were already enabled.
• A new-login email and a manually sent Cloudron test email arrived successfully.
• An older reboot-required email was received in August.
• Reviewed downloaded Box logs covering September 6–9, 2026 (UTC). They repeatedly report that the CRM requires a manual update because a major package version requires reviewing breaking changes. No corresponding maintenance-email send or mailer-error entries were found in that log. I understand that absence from this log alone does not establish the cause.

I have not run the troubleshooting command in the topic template. Please advise if specific diagnostic output is needed; I would review and redact it before posting.

Questions:

1. Are maintenance emails sent only when a notice is first created? Can its dashboard timestamp change without another email being sent?
2. What read-only diagnostic can distinguish expected suppression of repeat notifications from a failure to generate or send the email?
3. All available email notification categories are now enabled. Does this cover every new bell notification? If not, which are dashboard-only?
4. Is there a supported way to receive email reminders for unresolved urgent notices?

The only previously disabled email category was “App automatic update succeeded.” Enabling that does not explain the missing reboot/manual-update emails.

I checked the older solved thread “Does anyone else have an annoying notification ‘Reboot Required’?” It discusses retained/read notifications in Cloudron 8.2.1. I also saw that the Cloudron 9 announcement lists reboot-required email notifications. My question concerns the behavior on 10.0.4 with those preferences enabled.

I rarely open the dashboard and want reliable maintenance alerts—not automatic updates or reboots.

Thank you in advance!

I’m trying to establish the supported build/deployment workflow for an existing custom app on Cloudron 10.0.5 before making further production changes.

Current evidence:

• Installed Cloudron CLI: 8.2.2.
• The CLI reports “Build service type: local.”
• A previous update attempt returned HTTP 400 “Missing dockerImage.”
• The local app manifest has no dockerImage field, and no local .cloudron image configuration was found.
• The CLI source contains a source-archive update path, but we have not established whether this is supported by our server version.

Could you clarify:

1. Which CLI version and workflow should we use to build and deploy a custom app from source on Cloudron 10.0.5?
2. Can the Cloudron server accept source and build the app directly, or is a separate build service and/or container registry required?
3. Is there a supported build-only compatibility test that does not install, update, or restart an app?
4. For rollback, does restoring an app backup require the previous Docker image to remain available, and how can we verify that availability beforehand?

We want to avoid another production update attempt until the supported workflow and recovery requirements are clear.

@james Thanks ~!

I’m looking for clarification on two WordPress Managed update questions.

1. Package availability
   Has a WordPress Managed package containing the fix for CVE-2026-87902—WordPress 7.1.2, or an equivalent documented fix—been published?
   The latest entry I found in the Managed WordPress package-update thread (https://forum.cloudron.io/topic/2407/wordpress-managed-package-updates?page=2) was 3.20.2 / WordPress 7.1.1. If there’s a newer release or an existing discussion about this patch, a link would be appreciated.
2. Automatic-update behavior
   The documentation explains how to disable automatic updates for an individual app, but I couldn’t find what happens to updates already in progress through the scheduling process.
   If that app’s automatic-update toggle is turned off, what happens to:

• An available update displayed as pending;
• An update already queued for execution;
• An update already running?
  Is the setting checked again before a queued task starts, or does it only prevent future scheduling?
  Also, does Check for updates only refresh availability, with installation handled separately by the configured schedule, or can it initiate installation under the current automatic-update policy?
  I’m trying to understand the supported maintenance process, not bypass Cloudron’s managed updater. Thanks for any documentation links or clarification.