I think I can clarify this. Let's summarise what we all should know: Open Web UI needs to create a user automatically as admin. Even if you use Cloudron for authentication, this user will only have user rights. You need to log in using the account with the demo credentials and give your Cloudron account admin rights. There is no way around this account. If you decide to use the automatically created account, you cannot change its e-mail address, at least not using the GUI. It probably could be done in the database. If you want to delete this automatically created admin user, you don't need external software. Within the cloudron app settings, you can go into the terminal and connect to postgres, then there is a user table. This is probably the best approach.

thanks, fixed.

Yes, it's the same as branding - https://docs.cloudron.io/branding/#cloudron-name and https://docs.cloudron.io/user-directory/#openid-connect mention it.

@Lanhild said in ETA for GPU support? Could we contribute to help it along?: A lot of companies that might deploy Cloudron for its ease of life features don't necessarily have a VPS with a GPU. Also, (might help you to deepen your Cloudron knowledge) Cloudron packages usually are only one component/application. Moreover, OpenWebUI is "just" a UI that supports connections to Ollama and isn't affiliated with it. Meaning that Ollama isn't a dependency of it at all. Excellent points @Lanhild - you've convinced me. And there are benefits on the Ollama side too. I would appreciate the benefit in using Cloudron to keep our Ollama installation automatically up to date on its own, for instance. In fact, given our remaining inability to modify the existing Cloudron OpenWebUI app to run with our GPUs, for our small clients we are now thinking this way - I.e. using Cloudron just for the OpenWebUI component and letting them connect to our separately hosted Ollama. It's a bit less convenient than we were hoping, but at least we'll still have segregated data and user management for each client in OpenWebUI. So now, I also want a Cloudron OpenWebUI app that does not come with bundled Ollama, so that I can be sure these customers don't hammer our CPUs and get frustrated by a slow user experiences.

I resolved the issue. I had the directory set to /media/TSYSAI instead of just /media. Thanks!

@micmc yes, hopefully anythingllm can also come to live in Cloudron

ok I think it was RAM issue when there is no enough RAM. it gives this error. thanks guys

@micmc agreed i do use it on my computer but i was wanting to let my buddies play with it but hey thanks

This is out now

thanks I was able to reproduce and fix it. It will be part of the next package update

Awesome, now everything works just fine...salute for cloudron team

We would have to adjust the package to pre-configure the app to use optionally redis. However this is only relevant for multi-instance setups which is anyways not the case for Cloudron and only relevant for instances with many concurrent users, which is likely not the main focus for this app on Cloudron. So so far this optional redis is out of scope. From the Changelog: Enhanced load balancing capabilities for multiple instance setups

The Open Web UI project initially started out as a Ollama frontend. To run local models, one needs GPU support and Cloudron currently does not have GPU support. Over time, Open Web UI has shifed to be a frontend for OpenAI API compatible services . It is also now possible to configure Ollama in another computer which has a GPU and then point Open Web UI to use that Ollama. I guess we can mark this as stable since it's still useful while we figure out GPU support in Cloudron.

@vladimir-d In the future, I believe we should let the app handle most of it's configuration, environment-wise. Variables such as RAG_EMBEDDING_MODEL, etc. are all set via the application UI and saved in the config.json file. Now, for the initial issue of this topic, I've solved it by resetting the embedding model engine.

@firmansi not needed. apps are packaged as containers that have the right dependencies