mirror of
https://github.com/open-webui/docs.git
synced 2026-01-02 09:49:38 +07:00
2.5 KiB
2.5 KiB
sidebar_position, title
| sidebar_position | title |
|---|---|
| 6 | Enabling HTTPS Encryption |
Secure Your Open WebUI with HTTPS 🔒
While HTTPS is not strictly required for basic local operation, it is highly recommended for all deployments and mandatory for enabling specific features like Voice Calls.
:::warning Critical Feature Dependency
Modern browsers require a Secure Context (HTTPS) to access the microphone.
Voice Calls will NOT work if you access Open WebUI via http:// (unless using localhost).
:::
Why HTTPS Matters 🛡️
Enabling HTTPS encryption provides essential benefits:
- 🔒 Privacy & Security: Encrypts all data between the user and the server, protecting chat history and credentials.
- 🎤 Feature Unlocking: Enables browser restrictions for Microphone (Voice Mode) and Camera access.
- 💪 Integrity: Ensures data is not tampered with in transit.
- ✅ Trust: Displays the padlock icon, reassuring users that the service is secure.
Choosing Your Solution 🛠️
The best method depends on your infrastructure.
🏠 For Local/Docker Users
If you are running Open WebUI with Docker, the standard approach is to use a Reverse Proxy. This sits in front of Open WebUI and handles the SSL encryption.
- Nginx: The industry standard. Highly configurable, great performance.
- Caddy: Easiest option. Automatically obtains and renews Let's Encrypt certificates with minimal config.
- HAProxy: Robust choice for advanced load balancing needs.
☁️ For Cloud Deployments
- Cloud Load Balancers: (AWS ALB, Google Cloud Load Balancing) often handle SSL termination natively.
- Cloudflare Tunnel: Excellent for exposing localhost to the web securely without opening ports.
🧪 For Development
- Ngrok: Good for quickly testing Voice features locally. Not for production.
📚 Implementation Guides
Ready to set it up? Check out our dedicated tutorial category for step-by-step configurations: