This is very easy to solve! You don't need any S3 storage just to serve images. That's like using nuke to bomb an ant. Here is the solution: Step1: Create a repository on your github account. Step2: Upload an image (e.g. bot avatar) to your repository. Step3: Copy the link of your image, then paste to jsdelivr (select "convert from Github"). [image: 1715934680451-d1ca53cb-6e7f-468e-9abc-e05540baea9f-image-resized.png] Step4: Copy the JSdelivr link to your Typebot. [image: 1715934804835-5677227c-ec50-4db0-95f9-38de57586ecb-image-resized.png] Now, you have a world-class CDN provider serving your image FOR FREE!!! This link is permanent unless you purge it!

I do not, but you were right, It was a plugin that I had to see if any emails were related to a website. I removed it, and it now works; thank you for the assistance!

in long: how? ^^

We only update apps to the upstream versions which are marked as latest stable.

Thank You

@roseantonio If you install the latest version of the package, it lets you install without Cloudron SSO. After that, you can set up SMTP auth like above.

Thanks for answering, you made my day.

cool you found it! Feel free to mark this thread as a question and then as solved.

You'd have to install GPT-llama and have it use a local LLM, and configure TypeBot to use an alternate AI API URL provided by GPT-llama.

have you looked into this? https://docs.typebot.io/editor/blocks/integrations/openai

@nebulon said in Typebot does not restart after changing the env.sh: Well are there any errors in the app logs then? Also maybe you can share the exact env variables you are trying to set with a link to the upstream docs. Hey, nebulon! Thanks for asking. I solved the problem: do not include a space before or after the = in the configuration line: Good: export NEXT_PUBLIC_GIPHY_API_KEY=StringfromGiphyhere Bad: export NEXT_PUBLIC_GIPHY_API_KEY = StringfromGiphyhere Also, remember to include export at the beginning of the line, as mentioned in the Cloudron documentation.

Visit the upstream thread to see the full post and screenshots. To summarize, you can organize and hide table data similar to NocoDB's method. You can also send the form data as an email by using the email block integration.

We fixed the issue and the new package with typebot version 2.18.2 is out now

@girish said in Migrate custom typebot app to official typebot app while keeping the same database: If typebot offers an export/import, then you can use that. Otherwise, you will have to migrate the database (https://docs.cloudron.io/guides/import-postgresql/) and the files manually . Just make sure the typebot custom package and the cloudron package have the same typebot version. @saranade Indeed you can export all your flows in Typebot, and then import them in your new instance. So, in any typebot, simply click the 3 dots menu bar on the top right of the typebot's canvas, then choose export flow. It will send you a json file to download on your computer. Then, you can import the files in your new instance when creating a new typebot you simply choose import file.

There are basically two apps in one with Typebot. There's the "builder" app which is the admin interface used to create and manage bot flow (this has the auth tied to it), and the "viewer" app, which is where published bots can be viewed by the public. I don't think you can add auth to the viewer URLs. [image: 1693783583421-cleanshot-2023-09-03-at-19.24.05-resized.jpeg]

First: you must have a s3 storage like minio. Second: You need a bucket and some credentials configured in minio. Third: add the credentials for the s3 storage to the typebot env.sh file. Remember to add export to every key=value. (= export S3_ENDPOINT=minio-api.example.org) Restart the app. fourth: collect an image in your flow. insert the image into a variable. If you want to show the image to the user, add an image as a bubble and insert the variable into the link field. Here is a quick flow https://www.luckow.org/bot.html

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: [image: 1693638138423-brave_bitjdjatrt.png]

This is most likely the same issue as handled later in the thread at https://forum.cloudron.io/topic/9867/typebot-on-cloudron-is-great-you-should-try-it/13 Basically if you reinstall it with the latest version, it's probably fixed.

@LoudLemur said in Typebot Chat invitation links appear on social media with an image - Where is that setting?: 3rd party tools and and the text/image are already out cached in social media as the viral image The tools are provided by the social media platforms themselves and when you use them they remove and update the cache. But yes, ideal to know in advance.

@robi right on, Robi!