khanh.pndc/open-webui-docs
1
0
Fork 0
mirror of https://github.com/open-webui/docs.git synced 2026-01-03 02:09:51 +07:00
Code Issues Packages Projects Releases Wiki Activity

fix some links

Browse Source
This commit is contained in:
DrMelone
2025-12-20 21:24:44 +01:00
parent 720b1aec38
commit 1578d308c8
4 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/getting-started/advanced-topics/https-encryption.md
View File

@@ -28,9 +28,9 @@ 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](../../../tutorials/https/nginx.md)**: The industry standard. Highly configurable, great performance.
* **[Caddy](../../../tutorials/https/caddy.md)**: **Easiest option**. Automatically obtains and renews Let's Encrypt certificates with minimal config.
* **[HAProxy](../../../tutorials/https/haproxy.md)**: Robust choice for advanced load balancing needs.
* **[Nginx](../../tutorials/https/nginx.md)**: The industry standard. Highly configurable, great performance.
* **[Caddy](../../tutorials/https/caddy.md)**: **Easiest option**. Automatically obtains and renews Let's Encrypt certificates with minimal config.
* **[HAProxy](../../tutorials/https/haproxy.md)**: Robust choice for advanced load balancing needs.
### ☁️ For Cloud Deployments
* **Cloud Load Balancers**: (AWS ALB, Google Cloud Load Balancing) often handle SSL termination natively.