Cloudron Forum

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

the more i look into this I think its on the Mistral API side. Looks like they are not supporting openAI' API structure.

I get an odd error that says Mistral API is malformed but it works if I install open webui locally via docker.

May 29 11:14:06 ERROR:apps.openai.main:400 Client Error: Bad Request for url: https://api.mistral.ai/v1/chat/completions <30>1 2024-05-29T16:14:06Z iron 85872407-1b89-46c1-ae6f-868b66ed9a71 950 85872407-1b89-46c1-ae6f-868b66ed9a71 - Traceback (most recent call last): <30>1 2024-05-29T16:14:06Z iron 85872407-1b89-46c1-ae6f-868b66ed9a71 950 85872407-1b89-46c1-ae6f-868b66ed9a71 - File "/app/code/backend/apps/openai/main.py", line 361, in proxy <30>1 2024-05-29T16:14:06Z iron 85872407-1b89-46c1-ae6f-868b66ed9a71 950 85872407-1b89-46c1-ae6f-868b66ed9a71 - r.raise_for_status() <30>1 2024-05-29T16:14:06Z iron 85872407-1b89-46c1-ae6f-868b66ed9a71 950 85872407-1b89-46c1-ae6f-868b66ed9a71 - File "/usr/local/lib/python3.10/dist-packages/requests/models.py", line 1021, in raise_for_status <30>1 2024-05-29T16:14:06Z iron 85872407-1b89-46c1-ae6f-868b66ed9a71 950 85872407-1b89-46c1-ae6f-868b66ed9a71 - raise HTTPError(http_error_msg, response=self)
May 29 11:14:06 requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://api.mistral.ai/v1/chat/completions
May 29 11:14:06 INFO: 75.19.98.88:0 - "POST /openai/api/chat/completions HTTP/1.1" 500 Internal Server Error

Anyone know what causes this error to popup after a few sec. Is it port related?

Not sure if you seen that a new tag was added for in between version updates.

https://github.com/baptisteArno/typebot.io/releases/tag/next