Welcome to the Open WebUI FAQ page! Here you’ll find answers to common questions about setting up, using, and troubleshooting Open WebUI, including information on Docker usage, security, updates, and more. Whether you’re just getting started or need specific guidance, this page has the resources to help you ensure a smooth experience with Open WebUI.
Why am I asked to sign up? Where is my data being sent?
We require you to sign up to establish yourself as the admin for enhanced security. This protects your data if Open WebUI is ever accessed externally. Rest assured, all your data stays local—we do not collect any of it. When you sign up, all your information remains within your server and never leaves your device. Your privacy and security are our top priorities, ensuring full control over your data at all times.
Why can’t my Docker container connect to services on the host using localhost?
Inside a Docker container, localhost refers to the container itself, not the host machine. To connect from your container to services running on the host, use the DNS name host.docker.internal instead of localhost. This special DNS name allows Docker containers to recognize the host machine, overcoming the limitations of localhost.
How do I make my host’s services accessible to Docker containers?
To make host services accessible to Docker containers, configure those services to listen on all network interfaces by using the IP address 0.0.0.0 instead of 127.0.0.1, which is restricted to localhost. This setup enables services to accept connections from any IP address, including Docker containers. Keep in mind the security implications and consider measures such as firewalls and authentication to mitigate risks in external environments.
Why isn’t my Open WebUI updating? I’ve re-pulled/restarted the container, and nothing changed.
Pulling a new Docker image only updates the image, not the running container or its data. Here’s how to ensure the update is applied:
- Update the Docker Image: Run
docker pull ghcr.io/open-webui/open-webui:mainto get the latest image. - Persistent Data in Docker Volumes: Docker stores data in volumes, which persist through container updates.
- Applying the Update: Remove the old container (without deleting the volume) and create a new one using the updated image. This method updates the app while keeping your data safe.
Wait, delete my container—won’t I lose my data?
Deleting a container doesn’t delete your data if you’re using Docker volumes correctly. Here’s why:
- Volumes Preserve Data: Docker volumes store data outside the container’s lifecycle. As long as your data is in a volume, it remains safe.
- Safe Update Process: When updating Open WebUI, remove the old container and create a new one with the updated image. As long as the volume isn’t deleted (e.g., using
docker volume rm), your data remains intact. This ensures your app updates without losing data.
Should I use the distro-packaged Docker or the official Docker package?
We recommend using the official Docker package over distro-packaged versions. The official package is frequently updated with the latest features, bug fixes, and security patches, ensuring optimal performance and security. It also supports important functionalities like host.docker.internal, which may not be available in distro-packaged versions. This consistency provides a smoother experience and better support from the Docker community.
Is GPU support available in Docker?
Yes, GPU support is available in Docker, but it depends on the platform. Official support is offered in Docker for Windows and Docker Engine on Linux. However, Docker Desktop for Linux and macOS currently do not support GPUs. For applications requiring GPU acceleration, we recommend using Docker on platforms that officially support GPU integration.
Why does the WebUI project emphasize the use of Docker?
Docker ensures consistency, isolates dependencies, and simplifies deployment across different environments. This minimizes compatibility issues and makes it easier to get WebUI running. While Docker has a learning curve, the benefits for deployment and maintenance are significant. The project’s reliance on Docker is a key part of its design, though community-driven alternatives may offer different deployment options.
Why doesn’t STT/TTS work in my deployment?
Speech-to-Text (STT) and Text-to-Speech (TTS) services in your deployment may require HTTPS to function. Many modern browsers enforce security measures that restrict STT and TTS to HTTPS connections. If your deployment isn’t using HTTPS, these features may not work. Switching to HTTPS can resolve this issue and enable STT/TTS functionality.
Why doesn’t the WebUI include built-in HTTPS support?
We opted not to include built-in HTTPS support to provide flexibility for users. Integrating HTTPS directly could limit adaptability and may not meet the specific requirements of all users. We leave HTTPS termination setup to users, allowing for more customization. While we don’t offer official documentation on setting up HTTPS, the community may share insights and guidance as needed.
I updated/restarted/installed new software, and now my WebUI isn’t working!
If Open WebUI fails to launch after an update or software installation, the issue may stem from not using a virtual environment for backend dependencies. Direct installations can cause conflicts when system environments change. To prevent this, we recommend using a virtual environment to manage dependencies, isolating them from the system and minimizing risks.
I updated/restarted, and now my login isn’t working. I had to create a new account, and all my chats are gone.
This typically happens if a Docker container is created without mounting a volume for /app/backend/data or if the Open WebUI volume was deleted. Docker volumes ensure your data persists across container lifecycles. If you’re prompted to create a new account after a restart, it’s likely because the existing volume wasn’t attached. Ensure the Docker run command includes the correct volume mount to prevent data loss.
I tried to log in and couldn’t, so I made a new account. Now I’m being told my account needs admin activation.
This occurs when you forget the password for the initial admin account created during setup. The first account is designated as the admin account. Creating a new account without access to the admin account will trigger a request for admin activation. Keep track of your admin credentials or follow the guide to reset the admin password.
Why does the WebUI project fail to start with an SSL error?
An SSL error at startup may be due to missing SSL certificates or incorrect configuration of huggingface.co. To fix this, set up a mirror like hf-mirror.com and define it as the endpoint when starting the Docker container. Add -e HF_ENDPOINT=https://hf-mirror.com/ to your Docker run command:
docker run -d -p 3000:8080 -e HF_ENDPOINT=https://hf-mirror.com/ --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main