So probably need to start some basic 'differences' test :
I'm running cloudron 9.2
Are you the same or are you upgraded to 10 ?

Any logs showing what was happening before the crash ?

EDIT : I did a fresh install of AppsMonitor and did not meet any errors.
Is that message from the app's Logs panel ? or where did it show up ?

Needs more and deeper tests, and nothing will ever be a guarantee.
But it's a start.

I really understand and support the official stance - it is simply not viable otherwise.

Some other simple defences :

• have registered app packager scheme : no fees, basic metadata, probably already publicly known, enough to know legit packager and no more
• ca.cloudron.io only takes submissions from registered packagers (currently must have a Cloudron account)
• Cloudron will hate (understandably) any form of stars or likes on ca.cloudron.io, but maybe a simple more neutral voluntary “I installed this” counter

@necrevistonnezr said:

Just out of curiosity (and little technical knowledge): Shouldn't a system that isolates apps via docker not be taken down completely by a malformed configuration file of one app?

Yeah, absolutely. This is a good conversation to have

Cloudron was written primarily for pre-packaged apps written by us and not as a sandboxing environment to run arbitrary applications. When packages were written by us, we could "trust" the input in the manifest file, description, post install etc. When we made custom apps possible, the worst case was that a user sabotages himself with a poorly written manifest. But now with community apps, there is a new vector that malicious apps can do unknown things. For example, what if the description has some clickjacking or scam link? So, you can hit problems even without installing or running an app (so we don't hit run time isolation). This is also why we don't want to integrate community listing straight into the main dashboard, this would give too many good feelings of trust.

We are fixing issues (like this) as and when they come, but one should only run 3rd party packages they trust. Cloudron company's primary focus is still to runs the apps from the main app store and not to make a general trusted environment to run random stuff (FWIW, I don't think such a product exists out there).

Just out of curiosity (and little technical knowledge): Shouldn't a system that isolates apps via docker not be taken down completely by a malformed configuration file of one app?

someone will correct me if I am seeing this wrongly.
it wasn't malformed configuration of an app
it was a box service that failed

Ideally and mostly running containers are isolated.
But every cloudron app depends on box services, from nginx to maybe addons like proxyAuth. If the box service trips up, the app can't function as it should.

just done a 3rd test install
both cloudron box services and app seem ok

If I am understand this correctly, it wasn't me or the app

Is it working for you now ?
Not seeing any issues on a fresh install

Just out of curiosity (and little technical knowledge): Shouldn't a system that isolates apps via docker not be taken down completely by a malformed configuration file of one app?

Correct link :
https://communityapps.appx.uk/cloudron-appsmonitor/media/screenshot.png

nginx fails to start:

[emerg] directive "location" has no opening "{" in /etc/nginx/applications/<app-id>/mon.domain.net.conf:181

The app seems to use the proxyAuth addon. The generated location block contains HTML entities instead of literal single quotes:

Had to use a screenshot, as the HTML entity ' gets converted on a block quote on this forum

nginx treats "#" as the start of a comment, so the opening brace is lost and the config test fails, which takes down nginx for all apps.

Environment: Cloudron 10.0.5, Ubuntu 26.04, kernel 7.0.0-31-generic

[emerg] directive "location" has no opening "{" in
/etc/nginx/applications/ad146d5a-3e5f-417c-a377-7bc89fad201a/mon.domain.net.conf:181

So for now: DO NOT INSTALL

The log I could see before Cloudron went down:

Sep 16 07:27:06 apptask: run: app error for state pending_install: BoxError: Error reloading nginx: /usr/bin/sudo exited with code 1 signal null
    at file:///home/yellowtent/box/src/reverseproxy.js:103:26
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)
    at async reload (file:///home/yellowtent/box/src/reverseproxy.js:101:5)
    at async writeAppConfigs (file:///home/yellowtent/box/src/reverseproxy.js:572:5)
    at async Object.configureApp (file:///home/yellowtent/box/src/reverseproxy.js:594:5)
    at async installCommand (file:///home/yellowtent/box/src/apptask.js:504:5) {
  [stack]: [Getter/Setter],
  [message]: 'Error reloading nginx: /usr/bin/sudo exited with code 1 signal null',
  name: 'BoxError',
  reason: 'Nginx Error',
  extra: {}
}
Sep 16 07:27:06 reverseproxy: Attempt 3 failed. Will retry: Error reloading nginx: /usr/bin/sudo exited with code 1 signal null BoxError: Error reloading nginx: /usr/bin/sudo exited with code 1 signal null
    at file:///home/yellowtent/box/src/reverseproxy.js:103:26
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)
    at async reload (file:///home/yellowtent/box/src/reverseproxy.js:101:5)
    at async writeAppConfigs (file:///home/yellowtent/box/src/reverseproxy.js:572:5)
    at async Object.configureApp (file:///home/yellowtent/box/src/reverseproxy.js:594:5)
    at async installCommand (file:///home/yellowtent/box/src/apptask.js:504:5)
Sep 16 07:27:06 tasks: setCompleted - 24688: {"result":null,"error":{"message":"Error reloading nginx: /usr/bin/sudo exited with code 1 signal null","reason":"Nginx Error","stack":"BoxError: Error reloading nginx: /usr/bin/sudo exited with code 1 signal null\n    at file:///home/yellowtent/box/src/reverseproxy.js:103:26\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)\n    at async reload (file:///home/yellowtent/box/src/reverseproxy.js:101:5)\n    at async writeAppConfigs (file:///home/yellowtent/box/src/reverseproxy.js:572:5)\n    at async Object.configureApp (file:///home/yellowtent/box/src/reverseproxy.js:594:5)\n    at async installCommand (file:///home/yellowtent/box/src/apptask.js:504:5)"},"percent":100}
Sep 16 07:27:06 tasks: updating task 24688 with: {"completed":true,"result":null,"error":{"message":"Error reloading nginx: /usr/bin/sudo exited with code 1 signal null","reason":"Nginx Error","stack":"BoxError: Error reloading nginx: /usr/bin/sudo exited with code 1 signal null\n    at file:///home/yellowtent/box/src/reverseproxy.js:103:26\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)\n    at async reload (file:///home/yellowtent/box/src/reverseproxy.js:101:5)\n    at async writeAppConfigs (file:///home/yellowtent/box/src/reverseproxy.js:572:5)\n    at async Object.configureApp (file:///home/yellowtent/box/src/reverseproxy.js:594:5)\n    at async installCommand (file:///home/yellowtent/box/src/apptask.js:504:5)"},"percent":100}
Sep 16 07:27:06 BoxError: Error reloading nginx: /usr/bin/sudo exited with code 1 signal null
    at file:///home/yellowtent/box/src/reverseproxy.js:103:26
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)
    at async reload (file:///home/yellowtent/box/src/reverseproxy.js:101:5)
    at async writeAppConfigs (file:///home/yellowtent/box/src/reverseproxy.js:572:5)
    at async Object.configureApp (file:///home/yellowtent/box/src/reverseproxy.js:594:5)
    at async installCommand (file:///home/yellowtent/box/src/apptask.js:504:5)
Sep 16 07:27:06 Exiting with code 0
Sep 16 07:27:06 taskworker: Task took 39.389 seconds
Sep 16 07:26:40 WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
Sep 16 07:26:40 Press CTRL+C to quit
Sep 16 07:26:40 * Debug mode: off
Sep 16 07:26:40 * Running on all addresses (0.0.0.0)
Sep 16 07:26:40 * Running on http://127.0.0.1:3000

Troubleshoot info:

═══ Host ═══
Vendor: AZW Product: EQ
Linux: 7.0.0-31-generic
Ubuntu: resolute 26.04
Cloudron: 10.0.5
Execution environment: none
none
Processor: Intel(R) N100 x 4
RAM: 15616096KB
Disk: /dev/mapper/ubuntu--vg-ubuntu--lv  193G

═══ System ═══
[OK]Root disk usage is OK (57%)
[OK]Memory usage is OK (44%)
[OK]Disk I/O on /home/yellowtent (ubuntu--vg-ubuntu--lv, unknown): 461 MB/s write, iowait 1%
[OK]Clock is NTP-synchronized
[OK]node version is correct
[OK]IPv6 is enabled in kernel. Public IPv6 address detected
[OK]docker is running
[OK]docker version is correct

═══ Networking ═══
[OK]no incompatible persistent-firewall packages installed
[OK]DNS is resolving via systemd-resolved
[OK]unbound is running
[OK]IPv4 HTTPS to api.cloudron.io/api/v1/helper/public_ip
[OK]IPv6 HTTPS to api.cloudron.io/api/v1/helper/public_ip
[OK]IPv4 HTTPS to auth.docker.io/token
[OK]IPv6 HTTPS to auth.docker.io/token
[OK]IPv4 HTTPS to acme-v02.api.letsencrypt.org
[OK]IPv6 HTTPS to acme-v02.api.letsencrypt.org
[OK]netplan is good

═══ Cloudron Platform ═══
[OK]MySQL is running
[FAIL]nginx is down. Removing extraneous dashboard domain configs ...
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for details.
[FAIL]nginx is still down, please investigate the error by inspecting 'journalctl -u nginx' and /var/log/nginx/error.log
[OK]Dashboard cert is valid (83 days remaining, expires Dec  8 14:12:24 2026 GMT)
[FAIL]Could not load dashboard website with loopback check
[OK]No pending database migrations
[OK]Service 'mysql' is running and healthy
[OK]Service 'postgresql' is running and healthy
[OK]Service 'mongodb' is running and healthy
[OK]Service 'mail' is running and healthy
[OK]Service 'graphite' is running and healthy
[OK]Service 'sftp' is running and healthy
[OK]box v10.0.5 is running
[FAIL]IPv4: could not load https://my.domain.net
Hairpin NAT may not be working. Please check if your router supports it
[FAIL]IPv6: could not load https://my.domain.net
[OK]Domain domain.net is valid (170 days remaining, expires 2027-03-05T10:29:03Z)

======== Summary ========
PASS:  29
WARN:  0
FAIL:  5
SKIP:  0

Failures:
  - nginx is down. Removing extraneous dashboard domain configs ...
  - nginx is still down, please investigate the error by inspecting 'journalctl -u nginx' and /var/log/nginx/error.log
  - Could not load dashboard website with loopback check
  - IPv4: could not load https://my.domain.net
  - IPv6: could not load https://my.domain.net