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.
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: