Last update broke 404 on any team page

[CptPlastic]

https://cal.app.p7n.net/team/homeinspection

Every link or embed just returns 404's (is this even tested before its deployed?)

Not much in the logs just some warns.

- ⚠ metadata.metadataBase is not set for resolving social open graph or twitter images, using "http://localhost:3000". See https://nextjs.org/docs/app/api-reference/functions/generate-metadata#metadatabase
Dec 04 16:17:00 - react-i18next:: You will need to pass in an i18next instance by using initReactI18next
Dec 04 16:17:01 - 22:17:01:167 [WARN] RateLimit Disabled due to not finding UNKEY_ROOT_KEY env variable
Dec 04 16:17:01 - [PERF]: getEventTypesFromGroup(1) took 83.33565092086792ms
Dec 04 16:17:05 - [PERF]: getByViewer(1) took 38.18396472930908ms
Dec 04 16:17:12 - [PERF]: getEventTypesFromGroup(1) took 116.85779571533203ms
Dec 04 16:17:13 - Warning: data for page "/event-types" is 183 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
Dec 04 16:17:13 - Warning: data for page "/teams" (path "/teams?_rsc=s4kzv") is 183 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
Dec 04 16:17:44 - [PERF]: getEventTypesFromGroup(1) took 31.539581775665283ms
Dec 04 16:19:08 - [PERF]: getUserEventGroups(1) took 57.41061305999756ms
Dec 04 16:19:09 - [PERF]: getEventTypesFromGroup(1) took 62.68411207199097ms
Dec 04 16:19:11 - `markdownToSafeHTMLClient` should not be used on the server side. use markdownToSafeHTML instead
Dec 04 16:20:16 - Team billing is disabled, not generating a checkout session.
Dec 04 16:20:46 - [PERF]: getEventTypesFromGroup(1) took 19.931580066680908ms
Dec 04 16:20:46 <30>1 2024-12-04T22:08:59Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - ==> Migrate DB
Dec 04 16:20:46 <30>1 2024-12-04T22:09:05Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - 354 migrations found in prisma/migrations
Dec 04 16:20:46 <30>1 2024-12-04T22:13:14Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - See more info here: https://nextjs.org/docs/messages/large-page-data
Dec 04 16:20:46 <30>1 2024-12-04T22:14:12Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - See more info here: https://nextjs.org/docs/messages/large-page-data
Dec 04 16:20:46 <30>1 2024-12-04T22:14:12Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - See more info here: https://nextjs.org/docs/messages/large-page-data
Dec 04 16:20:46 <30>1 2024-12-04T22:16:36Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - │ │
Dec 04 16:20:46 <30>1 2024-12-04T22:16:36Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - │ │
Dec 04 16:20:46 <30>1 2024-12-04T22:16:36Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - │ Update available 5.22.0 -> 6.0.1 │
Dec 04 16:20:46 <30>1 2024-12-04T22:16:36Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - │ npm i -g prisma@latest │
Dec 04 16:20:46 <30>1 2024-12-04T22:16:36Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - │ https://pris.ly/d/major-version-upgrade │
Dec 04 16:20:46 <30>1 2024-12-04T22:16:36Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - └─────────────────────────────────────────────────────────┘
Dec 04 16:20:46 <30>1 2024-12-04T22:17:13Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - See more info here: https://nextjs.org/docs/messages/large-page-data
Dec 04 16:20:46 <30>1 2024-12-04T22:17:13Z iron d20434ce-7085-4bf8-b0c0-d03882ba226b 965 d20434ce-7085-4bf8-b0c0-d03882ba226b - See more info here: https://nextjs.org/docs/messages/large-page-data

[CptPlastic]

The link update never runs. I ended up rolling back.

[joseph]

@CptPlastic not sure which version you are on, but is your issue fixed by any chance in https://github.com/calcom/cal.com/releases ? Otherwise, can you raise an issue upstream?

Every link or embed just returns 404's (is this even tested before its deployed?)

Our tests are limited to deployment level i.e it installs, runs, passes healthcheck, can update/restore etc. It's not possible to add tests for what the app does. This is mostly covered by upstream tests. But calcom has an update almost every day, so I am sure they will fix any issue quickly.

[lrochetta]

Same issue here, and rolling back backup allows the calendar to works, but the admin app still unavailable.

[nebulon]

So the admin page also didn't work in the previous release?

[Fanch]

On my side, none of the calendars are working anymore (404 error), including in the administration interface.

[nebulon]

Alright we will revoke the release then

[CptPlastic]

After rolling back everything works Admin included.
Version I'm on Cal.com 4.7.14

[CptPlastic]

Should I try upgrading the the 4.7.18? Its not what was up on cloudron before looks like the broken one was 4.7.16 or 17.

[nebulon]

that was done accidentally while we fix up the package. Do not yet update calcom

[nebulon]

We pushed a fixed package version now. It should be safe to update. Sorry for the delay...those nextjs apps are really not designed for selfhosting unfortunately

[Jean-Henri]

Hi there,

I also had 404 page on all booking page.

Rolled back to v1.14.10 and disabled auto updates.

Is this bug coming from Cal.com or from Cloudron integration ?

Thanks,

[girish]

@Jean-Henri it was a bug in the Cloudron integration. This is fixed now. We reverted the broken packages.