Cloudron Forum

This looks interesting! Something you want to release into the world?

@timconsidine said:

@fbartels @jdaviescoates
I think girish comment was in discussion of moving from Tachyon community to Tachyon official. But I don’t have good access at the moment to search.

This is Cypht, not Tachyon (fork of Snappymail)?

Firefox and / or caching issue? Never have a problem on Safari.

@jdaviescoates said:

Oooh, always interested in web email clients as non of them are up to scratch. I'm hoping there is an option to not have a split screen UI...

This is a fork of Snappymail

@timconsidine said:

@necrevistonnezr what cloudron version are you on ? 9.2.0 ? or 10.0.5 ?

10.0.5

@timconsidine said:

But the logs do expose the real suspect. Line 417 (writeAppLocationNginxConfig) shows the generated proxyAuth nginx location:

"path":"!regexp:^/(public|health)(/|$)"
"location":"~ ^(?!(regexp:\\^/\\(public\\|health\\)\\(/\\|\\$\\)))"

Decoded, that location is ~ ^(?!(regexp:\^/\(public\|health\)\(/\|\$\))) — the literal regexp: prefix leaked into the pattern and every char is backslash-escaped, so it matches a string, not a regexp. That is malformed and is what changed between box versions; it is not a '/' issue.

That’s literally the bug I reported here: https://forum.cloudron.io/post/129507 ?

And BTW it’s not an issue for my own app using proxyAuth.

@timconsidine Yes, this was more directed at the Cloudron Team...

No, I de-installed as soon as the system was up and running again, I had my share of experiments for the day

Thanks!

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?

@girish @timconsidine
Or maybe it’s a bug with HTML-escaped quotes in proxyAuth nginx config?

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

This seems to be the culprit, “mon.domain.net” was the domain I tried to use:

[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

@timconsidine
Did that install just kill the nginx.service?
Since installing that, Cloudron doesn’t come up.

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

No worries - and 12.1 with a lot of fixes is out: https://github.com/jellyfin/jellyfin/releases/tag/v12.1

https://github.com/jellyfin/jellyfin/releases/tag/v12.0

A new major release.

Before upgrading from an earlier version, a full backup of the data directory is strongly recommended, as this release includes database changes that prevent rolling back without a full restore.

Direct upgrades from 10.10.7 and 10.11.x to 12.0 are supported; intermediate upgrades are not required. Users running releases older than 10.10.7 are strongly encouraged to upgrade to 10.10.7 before migrating to 12.0.

Installed repository plugins (anything not built-in) should also be removed before migrating. Plugins will likely need time to adapt to the new database changes, so re-adding them afterward is the safest approach for testing.

Official plugins compatible with Jellyfin are available through the stable plugin repository. If you have changed to the unstable plugin repository please change it back.

Go to Dashboard -> Plugins -> Manage Repositories
Update the Plugin Repository URL to: https://repo.jellyfin.org/files/plugin/manifest.json
After migrating please perform the following steps.

Perform a full library scan to restore alternative versions.

@girish said:

To give an update, docs are mostly updated. 10.0.5 has been published. There is now a Ubuntu 26 migration guide (but only follow this after updating to 10.0.5 !)

Just run the upgrade to Ubuntu 26.04 according to the docs - just worked. Thanks!

https://github.com/FreshRSS/FreshRSS/releases/tag/1.30.0

Just FYI:

This is a security-oriented major release with several important security patches, so users are encouraged to update without delay.

From this release, we are also making it clear that our rolling-release channel (edge) is recommended for faster security patches.

@LoudLemur said:

@necrevistonnezr has a valid point, too. What else can we do, though? "Understand it better?" This problem meant people were not receiving emails. Not sending a bug report, particularly when the ai had found a fix, didn't seem public spirited. It also is a bit like self-censorship.

It’s pretty simple: Read the output, work with it it, make it your own. Don‘t just forward it unfiltered. If that’s too much, leave it.

In case of a bug report, if you don’t want to put in the work, what’s the point? How does the team know your report was verified by you and has merits? It would probably more helpful to leave the team your result in 3-4 sentences and provide the prompt - then they can see for themselves.

Sorry, but pushing a wall of unread and unrefined AI-output is just super-rude.

With a lot of updates, including their own and open-sourced compression and preflight engine plus direct PDF editing, I believe this would be a great addition to our apps:
https://github.com/alam00000/bentopdf/releases/tag/v2.8.8

@jayonrails It‘s literally in the post from girish that I cited above : „We will have a guide during release time to upgrade manually from Ubuntu 24.04.“