Hello @superhua
Without more details about your set-up it is close to impossible to make an assumption what the issue could be.
It might be the systems IO, network speed or something else.
Maybe you can check your browser console with these request if they really take this long.
If the browser console reports back faster the web log viewer it might be system related.

Maybe also provide the output of cloudron-support --troubleshoot so we can get a better understand of what you are working with.

Hello @fbartels
This is fixed.

Hello @oskarardolo
It is possible what with extra effort.
Similar to https://forum.cloudron.io/post/126448

Hello @limpmerry1
We had a lot of spam users who just signed up to put ads into the profile picture and signature.
After some time you gain reputation and then you will be able to change these things.

[1.14.2]

• FIX: run scheduled jobs as www-data so cron-created invoice folders are writable by the web UI

Hello @matth33
Sorry it took so long.
It was actualy a simple fix and the latest app update fixes this issue.

Hello @Matth33
I am looking into this issue today.

Hello @simon
We just published an update for the @gitlab app that reduces the puma work count.

Hello @fbartels
Thanks for reporting, we will fix this.

Hello @mononym
I did not yet look into this myself.

Hello @potemkin_ai
Here you can find instructions on how to enable or disable apps in Nextcloud https://docs.cloudron.io/packages/nextcloud#fixing-a-broken-install

Hello @saikarthik

Could you explain how are trying to use proxyAuth?
I assume this is a custom app that does not support OIDC.
The proxyAuth add-on exists for apps that do not have LDAP or OIDC support and is rarely used.

I will have to look into it if proxyAuth even supports setting multiple paths, because I think it might not currently.

Hello @luckow
We will publish an announcement soon that will explain it.

Hello @simon
Thanks for reporting.
It should be possible to limit the ram usage of the puma workers according to https://docs.gitlab.com/administration/operations/puma/

Hello @ekevu123
I understand the request but in my opinion adding "advanced" sections to the Cloudron dashboard will only lead to issues.
Someone who is less skilled will see the button and use it.

"Don't press the red button, it will wipe the DB server!"
"Oh! A red button!"

In your case, since you still need to use the terminal anyway, why not use the cloudron cli directly and have a bash alias ready to execute the interactive DB shell directly for an app?
This would even reduce your time spend getting there even further.
Instead of your mention steps 1>4 or future 3-dot sub menu, moving the mouse, clicking moving again yada yada, one command from the local shell, and you got what you need.

For example:

cloudron exec --tty --app $APPID -- sh -c 'mysql --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE}'

Tracking this issue in this topic with a maintainer of Grist https://forum.cloudron.io/post/126499

Current solution, restore to Cloudron app version 1.2.3 which packages Grist version 1.7.15.
This version does not have the issue.

Hello @paulfitz
Did something change with updates from 04.06.2026 until now in Grist change regarding the enterprise logic or stuff?

In the following thread https://forum.cloudron.io/topic/15602/allow-email we noticed that clicking Switch to Full Grist is no longer working for the Cloudron Grist app.
Thus, also the enterprise and email notifications are no longer working.
Some change must have created this issue from Grist version 1.7.15 or 1.7.16.

Since we only recently added the enterprise option again after it was reinstated with install:ee on 19.05.2026 having it fail on us just after two updates again is rather frustrating.

---

EDIT:

I have narrowed down that the issue arises when updating Grist from version 1.7.15 to version 1.7.16.
In version 1.7.15.

In the changelog of grist 1.7.16 is this statement:

yarn install in grist-core now builds the full edition by default, via a post-install hook that downloads the ext material from grist-ee. Use yarn run set-community-edition to skip it (the previous behavior) or yarn run set-full-edition to opt in explicitly. The chosen edition is saved to grist-edition, GRIST_EDITION takes precedence, and GRIST_SKIP_EXT_AUTOSETUP skips the hook for contexts where extensions are installed manually (Docker builds, grist-desktop, grist-static) (commit )

According to that, the default should be full but the Cloudron app defaults to community.
Using the admin ui and clicking Switch to Full Grist does nothing after a restart.
The edition stays community.
Even when setting export GRIST_EDITION=full and restarting the app the edition stays community.
Even putting the app in recovery mode to allow full read-write, running yarn run set-full-edition:

yarn run set-full-edition
yarn run v1.22.22
$ echo full > grist-edition && yarn install
[1/4] Resolving packages...
warning Resolution field "@gristlabs/sqlite3@6.0.1-grist.1" is incompatible with requested version "@gristlabs/sqlite3@^5.1.4-grist.7"
success Already up-to-date.
$ buildtools/install_edition.sh
+ ext already at grist-ee (date-2026-06-29-15-21-09); using cached copy
warning package.json: No license field
warning No license field
[1/4] Resolving packages...
success Already up-to-date.
+ Full edition ready (ext/ and ext/node_modules).
Done in 1.38s.

creates the grist-edition file

cat grist-edition 
full

But still, the UI will not use the full edition and stays community.

So neither of the documented ways to set the edition nor the web UI is working for the Cloudron app, even when the app is in recovery mode allowing full read-write access.

Hello @sansguidon
Thank you very much for looking into this and also providing a solution.

Hello @beardmancer
Please go into your Cloudron dashboard Domains settings.
There you will find the Sync DNS section.
Press the Sync DNS button and all records should be synchronized.
If you have done so, you can check your Porkbun management UI or inform me so I can run the dig commands again to validate the DNS records have been set.

I hate money

Detail	Link / Info
Wishlist topic	Link to wishlist topic
Author	@filter
Repository	Repository
Install	CloudronVersions.json

If you have questions or issues about this community app, please open a separate topic in the @community-apps category and link to this reply.