-
@plains-digital Don't know about Sendgrid, but the OpenAI key works fine for me at least.
-
@shrey infuriatingly, using my openai api key on typebot.io directly worked without a hitch, but self hosted - buggered.
so im going to try an resinstall and if that fails build on their hosted service as a proof of concept and then hopefully migrate if they ever gets addressed
reinstall for the win, fingers crossed!
-
@plains-digital said in Typebot on Cloudron is great! You should try it:
reinstall for the win, fingers crossed!
It is quite exciting! Please let us know if this solves the mystery!
-
@plains-digital said in Typebot on Cloudron is great! You should try it:
@shrey infuriatingly, using my openai api key on typebot.io directly worked without a hitch, but self hosted - buggered.
so im going to try an resinstall and if that fails build on their hosted service as a proof of concept and then hopefully migrate if they ever gets addressed
reinstall for the win, fingers crossed!
Resintalled, updated cloludron, cleared my caches. still invalid length - but works fine on typebot.io.
is everyone else installing via the Cloudron CLI? I will do that if need be lol
someone rescue me, this is the app my project has been dreaming of for a month and im SOOO CLOSE lol.
i refuse to build it on anything but self hosted though... and its still a stellar chat bot builder, even without openai
sigh -
@plains-digital Sorry, i hadn't tried Typebot on Cloudron yet.
My current instance is hosted elsewhere, where everything's working fine.
@plains-digital said in Typebot on Cloudron is great! You should try it:
@shrey infuriatingly, using my openai api key on typebot.io directly worked without a hitch, but self hosted - buggered.
Indeed, there seems to be some issue with the way Typebot is set up on Cloudron.
Logs for Cloudron team:
Aug 28 12:07:28 Something went wrong DataError: Invalid key length Aug 28 12:07:28 at new DOMException (node:internal/per_context/domexception:53:5) Aug 28 12:07:28 ... 8 lines matching cause stack trace ... Aug 28 12:07:28 at async outputMiddleware (file:///app/code/builder/node_modules/.pnpm/@trpc+server@10.34.0/node_modules/@trpc/server/dist/index.mjs:297:24) { Aug 28 12:07:28 code: 'INTERNAL_SERVER_ERROR', Aug 28 12:07:28 name: 'TRPCError', Aug 28 12:07:28 [cause]: DOMException [DataError]: Invalid key length Aug 28 12:07:28 at new DOMException (node:internal/per_context/domexception:53:5) Aug 28 12:07:28 at __node_internal_ (node:internal/util:509:10) Aug 28 12:07:28 at validateKeyLength (node:internal/crypto/aes:78:11) Aug 28 12:07:28 at Object.aesImportKey (node:internal/crypto/aes:279:7) Aug 28 12:07:28 at SubtleCrypto.importKey (node:internal/crypto/webcrypto:562:10) Aug 28 12:07:28 at encrypt (/app/code/builder/apps/builder/.next/server/chunks/5044.js:40:37) Aug 28 12:07:28 at /app/code/builder/apps/builder/.next/server/chunks/4548.js:1691:124 Aug 28 12:07:28 at async resolveMiddleware (file:///app/code/builder/node_modules/.pnpm/@trpc+server@10.34.0/node_modules/@trpc/server/dist/index.mjs:416:30) Aug 28 12:07:28 at async callRecursive (file:///app/code/builder/node_modules/.pnpm/@trpc+server@10.34.0/node_modules/@trpc/server/dist/index.mjs:452:32) Aug 28 12:07:28 at async outputMiddleware (file:///app/code/builder/node_modules/.pnpm/@trpc+server@10.34.0/node_modules/@trpc/server/dist/index.mjs:297:24) Aug 28 12:07:28 }
-
-
@plains-digital it worked!
-
-
-
You are amazing to have solved this and fixed it so quickly, @nebulon.
To get the typebots you were running working again, you can try this:
- Restore from an earlier working backup
- Navigate to your typebot flow and at the three dots at the top right .... export the flow. Save it in a safe place.
- Reinstall Typebot in Cloudron
- create a new typebot by selecting the import flow
- When you try and re-publish, it will give the typebot a new address, so you might like to edit that option to set it to your previously published address: