Cloudron Forum

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.

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

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

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

Please build new release 3.1.0

I reached out via the leantime discord but no reply.

Im not sure what you use to build but there was a quick fix pushed for a Vercel bug. I use Vercel in dev to build this. So prob should update straight to 3.0.1.

Can someone please update this app. There are numerous bugs to include the plugin issues that are fixed in 3.2.1.

Same boat here can you please update this?

There is a breaking change that just got fixed and I was curios if cloudron uses a webhook or something to release the new build?

Yeah I that is the same I ended up using CAL. This is just getting worse it seems.

Can you check the logs and see if there is an error? How much ram do you have allocated to your app? Mine ran out of memory I set the ram to 2gb.

Here is a solution to fix this. Its a workaround till documentoso gets this fixed.
https://github.com/documenso/documenso/issues/1171

Use the -legacy flag

Same steps as before.

1. openssl genrsa -out private.key 2048
2. openssl req -new -x509 -key private.key -out certificate.crt -days 365
   a. Fill out all the details.
3. openssl pkcs12 -export -out cert.p12 -inkey private.key -in certificate.crt -legacy
   a. If you set a password you have to add this line to your .env file.
   NEXT_PRIVATE_SIGNING_PASSPHRASE={YourStrongPassHere}
4. Restart your app.

I think I found a solution. I'm testing it now.

@nebulon This is true, however if you have a signing inspector this will not pass as the signing cert is not related to the origin of the document. That is what lead me down this path to try and get the new cert to work. Also the one that comes with it will expire.

I did try to set the owner to cloudron. I may try again to see if I can get it to work.

Im not sure what im doing wrong here. I created a new signing cert as per the updated instructions I created one with a password and one without thinking it was not getting the password from someplace. I dont see any cert configuration in the .env file so im not sure that its even needed. Here is the error I get now.

Error: Failed to get private key bags
Aug 12 10:21:16 at I (/run/documenso/apps/web/.next/server/chunks/8946.js:1:1144118)
Aug 12 10:21:16 at async I (/run/documenso/apps/web/.next/server/chunks/8946.js:1:1142215)
Aug 12 10:21:16 at async k (/run/documenso/apps/web/.next/server/chunks/8946.js:1:6584)
Aug 12 10:21:16 at async h (/run/documenso/apps/web/.next/server/pages/api/trpc/[trpc].js:1:44521)
Aug 12 10:21:16 at async /run/documenso/apps/web/.next/server/pages/api/trpc/[trpc].js:1:142833
Aug 12 10:21:16 at async resolveMiddleware (file:///run/documenso/node_modules/@trpc/server/dist/index.mjs:420:30)
Aug 12 10:21:16 at async callRecursive (file:///run/documenso/node_modules/@trpc/server/dist/index.mjs:456:32)
Aug 12 10:21:16 at async callRecursive (file:///run/documenso/node_modules/@trpc/server/dist/index.mjs:456:32)
Aug 12 10:21:16 at async resolve (file:///run/documenso/node_modules/@trpc/server/dist/index.mjs:486:24)
Aug 12 10:21:16 at async inputToProcedureCall (file:///run/documenso/node_modules/@trpc/server/dist/resolveHTTPResponse-cd1a9112.mjs:46:22) {
Aug 12 10:21:16 code: 'GenericFailure'
Aug 12 10:21:16 }

Not sure what happened but it seems the new update broke email and some random dates showing that should not be.

This is what was updated in Cloudron

I was working on getting a fix for the Mistral API issue and noticed that cloudron is on and older Ollama version based on OI integration testing. Ollama should be at 0.1.39