Cloudron Forum

@james I have some news
The update refreshed the server to 2.9.0 in /app/code, but the prebuilt frontend in the persistent volume /app/data/twenty-front was never re-synced — it still held the original 0.14.0 front from install (files dated from install day; index.html still pointing to the old bundle index-CGzHeZZA.js).
That stale bundle queries GaugeChartConfiguration, a type removed server-side in 2.3. So a 2.8.0-era front was served against a 2.9.0 schema → Unknown type "GaugeChartConfiguration" → blank page on load.

Confirmed: the string is present in /app/data/twenty-front/assets/ but absent from the fresh package front in /app/code/packages/twenty-server/dist/front.orig/assets/ (different hashes).

Fix: copied assets/, images/, manifest.json, index.html from dist/front.orig/ → /app/data/twenty-front/ (keeping the .env symlink), then restarted. App works.

Hope this helps

After the package update to Twenty 2.9.0, the app no longer loads — blank page in the browser.
The server side is healthy and fully on 2.9.0:

yarn command:prod upgrade:status → Instance 2.9.0 and the single workspace 2.9.0, both Up to date, 0 workspaces failed.
Server logs: [NestApplication] Nest application successfully started, all routes mapped, healthcheck green after boot (0 ECONNREFUSED once started), BullMQ worker processing jobs, no 500s and no GraphQL errors server-side.

The failure is frontend-only. At app load, the browser console throws:

Uncaught (in promise) CombinedGraphQLErrors: Unknown type "GaugeChartConfiguration".
Did you mean "BarChartConfiguration", "LineChartConfiguration", "PieChartConfiguration",
"AggregateChartConfiguration", or "CalendarConfiguration"?
  at /assets/index-CGzHeZZA.js

So the shipped frontend bundle queries a GraphQL type (GaugeChartConfiguration) that the 2.9.0 server schema does not define the package's front and server look built against different schemas.

Already tried, no effect:

• Reproduced in a clean private/incognito window → rules out browser cache.
• yarn command:prod cache:flush + restart → same error.
• App Repair → same error.

The only thing that would restore a working UI is rolling back to the pre-2.9.0 backup, which loses ~3 days of data, so I'd rather not.

Questions:
Is this a known front/server mismatch in the 2.9.0 package?
Is a corrected 2.9.x already available, or coming?
Is there a supported way to realign the frontend bundle with the server without a full rollback?