I don't mind them being like this they are labeled as unstable after-all. I would rather work through issues with cloudron.
CptPlastic
Posts
-
postiz won't log out -
Install IssuesAhh I just assumed that was fixed from reading this forum. That was it set to 1MB still.
Thanks
-
Install IssuesAnyone else run into this when installing?
Mar 29 20:34:07 => Healtheck error: Error: Timeout of 7000ms exceeded Mar 29 20:34:10 TypeError: fetch failed Mar 29 20:34:10 at node:internal/deps/undici/undici:13502:13 Mar 29 20:34:10 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Mar 29 20:34:10 at async /app/code/dist/apps/frontend/.next/server/app/auth/page.js:1:9720 Mar 29 20:34:10 at async u (/app/code/dist/apps/frontend/.next/server/app/auth/page.js:1:8996) { Mar 29 20:34:10 digest: '4026516519', Mar 29 20:34:10 [cause]: AggregateError [ECONNREFUSED]: Mar 29 20:34:10 at internalConnectMultiple (node:net:1122:18) Mar 29 20:34:10 at afterConnectMultiple (node:net:1689:7) Mar 29 20:34:10 at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) { Mar 29 20:34:10 code: 'ECONNREFUSED', Mar 29 20:34:10 [errors]: [ [Error], [Error] ] Mar 29 20:34:10 } Mar 29 20:34:10 } Mar 29 20:34:11 TypeError: fetch failed Mar 29 20:34:11 at node:internal/deps/undici/undici:13502:13 Mar 29 20:34:11 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Mar 29 20:34:11 at async /app/code/dist/apps/frontend/.next/server/app/auth/page.js:1:9720 Mar 29 20:34:11 at async u (/app/code/dist/apps/frontend/.next/server/app/auth/page.js:1:8996) { Mar 29 20:34:11 digest: '4026516519', Mar 29 20:34:11 [cause]: AggregateError [ECONNREFUSED]: Mar 29 20:34:11 at internalConnectMultiple (node:net:1122:18) Mar 29 20:34:11 at afterConnectMultiple (node:net:1689:7) Mar 29 20:34:11 at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) { Mar 29 20:34:11 code: 'ECONNREFUSED', Mar 29 20:34:11 [errors]: [ [Error], [Error] ] Mar 29 20:34:11 } Mar 29 20:34:11 }
-
Auto-update to 8.3 - various apps down - database issue@girish Man this is bad
-
Auto-update to 8.3 - various apps down - database issueSHAME ON YOU! I just woke up to a mess of cloudron servers being all messed up over this 8.3 update. To make matters worse almost every single database had to be restored. Some of this caused data loss because the apps on some accounts are used for logging 24/7. I learned a valuable lesson. Turn off auto update.
-
Last update broke 404 on any team pageShould 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.
-
Last update broke 404 on any team pageAfter rolling back everything works Admin included.
Version I'm on Cal.com 4.7.14 -
Last update broke 404 on any team pageThe link update never runs. I ended up rolling back.
-
Last update broke 404 on any team pagehttps://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 update 3.1.0Please build new release 3.1.0
-
Leantime 3.2.0 update issueI reached out via the leantime discord but no reply.
-
Heads up on next version 3.0.1Im 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.
-
PLEASE UPDATE 3.2.1Can someone please update this app. There are numerous bugs to include the plugin issues that are fixed in 3.2.1.
-
Leantime 3.2.0 update issueSame boat here can you please update this?
-
Is this auto updating?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?
-
1.5 Broke email and is buggyYeah I that is the same I ended up using CAL. This is just getting worse it seems.
-
Documenso Errors When Signing/Completing a DocumentCan 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.
-
Create New CERTHere is a solution to fix this. Its a workaround till documentoso gets this fixed.
https://github.com/documenso/documenso/issues/1171Use the
-legacy
flagSame steps as before.
openssl genrsa -out private.key 2048
openssl req -new -x509 -key private.key -out certificate.crt -days 365
a. Fill out all the details.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}
- Restart your app.
-
Create New CERTI think I found a solution. I'm testing it now.
-
Create New CERT@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.