Files
open-webui-docs/docs/reference/https/index.md
2026-02-14 11:37:32 +01:00

41 lines
1.9 KiB
Markdown

---
sidebar_position: 6
title: "HTTPS & Reverse Proxies"
---
# 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:
1. **🔒 Privacy & Security**: Encrypts all data between the user and the server, protecting chat history and credentials.
2. **🎤 Feature Unlocking**: Enables browser restrictions for Microphone (Voice Mode) and Camera access.
3. **💪 Integrity**: Ensures data is not tampered with in transit.
4. **✅ 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](./nginx)**: The industry standard. Highly configurable, great performance.
* **[Caddy](./caddy)**: **Easiest option**. Automatically obtains and renews Let's Encrypt certificates with minimal config.
* **[HAProxy](./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.*