Cloudron Forum

Hello @harryz The OpenWebUI Cloudron app no longer comes bundles with an internal ollama server. Sorry, the documentation is outdated and I will update it accordingly. Please install the Ollama app. Inside the Ollama app web terminal you can run this command to pull a modell: ollama pull tinyllama In the Ollama app web terminal also run: cat /app/data/.api_key Note down this key, you will need it. Then you need to configure the OpenWebUI app. Login as an admin and navigate to https://YOUR.DOMAIN.TLD/admin/settings/connections: Press the configuration button for Ollama: [image: 1764460178345-3942698c-53b8-4d6e-9ff6-082ccc8bf98f-image-resized.png] Click on local to change it to external: [image: 1764460213007-8b8e92ce-61ea-427e-b558-64dc97a17470-image.png] Now when it shows external (1) configure the URL to your Ollama app url and paste the key from before into Auth [image: 1764460364968-8fe3dc2a-53bb-40e5-85b4-5c3cac1c5c17-image.png] You can press the 'reload' icon to verify the connection: [image: 1764460422084-908ae333-8664-4068-85c5-01b7b7468b47-image.png] If you see the success message in the top right, you should be good to go and click the Save button. [image: 1764460460840-1cd29bad-20fc-4c61-9f13-b381136b6586-image.png] Now you can use your own Ollama server and modells in OpenWebUI: [image: 1764460517410-d8686e0a-8b90-4eb7-b91e-77961aa14ab8-image-resized.png]

@robi this worked, thank you. I hadn't realized there was a way to check services like that (I had another issue previously telling me to restart nginx, which I never could find out how, but this worked for that too). thanks for the help!

Thank you, @canadaduane for the great analysis! In case it’s helpful, here are some examples of API usage in different languages: JavaScript PHP Python Bash You can find full working examples here: https://docs.mirotalk.com/mirotalk-sfu/api/

Since the call for action was rather on short notice and only @msbt replied so far I'll postpone to another date. Creating a new poll for dates

@MaxMan something networking related is wrong. The server is unreachable from here (cannot even ping) . How do you ssh into your server? With the public IP?

So the only version 9 of cloudron i can upgrade to is a prerelease version. This is a prod system, so id rather not.

oK, Im not sure if I just fat fingered something or if this was fixed, but the yaml is now set up to be working. Here is my .yaml file name: Sync Repo with Cloudron LAMP app on: workflow_dispatch: push: branches: [main] jobs: deploy-to-cloudron-app: runs-on: ubuntu-latest environment: [WHATEVER YOUR ENVIRONMENT NAME WAS IN SETTINGS OF REPO] steps: - name: Checkout Repository uses: actions/checkout@v4 - name: Diagnostic – Print environment context run: | echo "=== GITHUB CONTEXT ===" echo "Branch: $GITHUB_REF" echo "Workflow: $GITHUB_WORKFLOW" echo "Runner: $RUNNER_NAME" echo "Workspace: $GITHUB_WORKSPACE" echo "======================" - name: Diagnostic – Check secret presence shell: bash run: | declare -A secrets secrets["CLOUDRON_FQDN"]="${{ secrets.CLOUDRON_FQDN }}" secrets["CLOUDRON_TOKEN"]="${{ secrets.CLOUDRON_TOKEN }}" secrets["CLOUDRON_APP_ID"]="${{ secrets.CLOUDRON_APP_ID }}" echo "Checking secrets..." for key in "${!secrets[@]}"; do if [ -z "${secrets[$key]}" ]; then echo "❌ $key is EMPTY" else echo "✅ $key is set" fi done - name: Cloudron Push to App uses: cloudron-io/cloudron-push-to-app@latest with: CLOUDRON_FQDN: "${{ secrets.CLOUDRON_FQDN }}" CLOUDRON_TOKEN: "${{ secrets.CLOUDRON_TOKEN }}" CLOUDRON_APP_ID: "${{ secrets.CLOUDRON_APP_ID }}" CLOUDRON_PUSH_DESTINATION: "/app/data" CLOUDRON_CREATE_APP_BACKUP: "false"

Hello @james, and thank you! Remarkable indeed. As I don't know anything about the number of Cloudron instances, their respective user counts etc., I could only make wild assumptions. But guess immich is quite popular. (Perhaps lots of people set a default storage quota in their configuration? Or maybe having a local config was obligatory at some point? Or most just adjust the quota for every user individually?)

3 1/2 years ago? Sorry, no I don’t even remember what I had for dinner yesterday….

Hello @imc67 Could it be that you simply need to zoom out of your terminal or make the window larger? Had the same first thought when running this command but when resizing the window or zooming out: [image: 1764363715688-4b9b8272-3458-4bf8-8e45-7adb9cc95592-image-resized.png]

The disk space warning is about the percentage being over 90%. Given the size of your disk, this is not really an issue, since you have plenty of GBs left and freescout does not need nearly that much of temporary disk space. Not quite sure what to make out, that a whole server reboot fixed this temporarily but a freescout app instance restart did not. Is freescout using mailboxes on that same Cloudron? If so and the issue arises again, does it help if you restart the mail service (and maybe freescout)?

@luckow thanks for sharing, got my signature.