-
Notifications
You must be signed in to change notification settings - Fork 566
Update Cloudflare Tunnel docs links and steps #1259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -31,7 +31,7 @@ The simplest path. Everything configured through the Cloudflare dashboard. | |
|
|
||
| ### 1. Create the tunnel | ||
|
|
||
| 1. Go to [**Zero Trust → Networks → Tunnels**](https://one.dash.cloudflare.com/networks/tunnels) | ||
| 1. Go to [**Zero Trust → Networks → Connectors**](https://dash.cloudflare.com/?to=/:account/one/networks/connectors) | ||
| 2. Click **Create a tunnel** → select **Cloudflared** | ||
| 3. Name it (e.g., `open-webui`) | ||
| 4. Follow the install instructions to run the connector on your machine | ||
|
|
@@ -189,7 +189,7 @@ volumes: | |
| open-webui: | ||
| ``` | ||
|
|
||
| Get your tunnel token from the [Cloudflare dashboard](https://one.dash.cloudflare.com/networks/tunnels) → select your tunnel → **Configure** → copy the token from the install command. | ||
| Get your tunnel token from the [Cloudflare dashboard](https://dash.cloudflare.com/) → Go to [**Networking → Tunnels**] → Select your tunnel → Select **Add a replica** → Copy the install command. The token starts with `eyJ...`. | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. https://one.dash.cloudflare.com/networks/tunnels is also broken. This dashboard provides a way to obtain a tunnel token from the updated https://dash.cloudflare.com/?to=/:account/one/networks/connectors by selecting your tunnel, clicking “Add a connector,” choosing an operating system like Docker, Windows, or Mac from the pre-selected dropdown, and then copying the install command. However, this install command and the dropdown are different for each user. What is documented here is a simpler and more consistent method with fewer steps to obtain the tunnel token. |
||
|
|
||
| :::tip | ||
| No `ports` needed on the `open-webui` service. `cloudflared` connects to it via Docker's internal network. To use this, change the service URL in your tunnel config to `http://open-webui:8080`. | ||
|
|
@@ -201,9 +201,9 @@ No `ports` needed on the `open-webui` service. `cloudflared` connects to it via | |
|
|
||
| Cloudflare Zero Trust lets you gate access behind authentication without touching Open WebUI: | ||
|
|
||
| 1. Go to [**Zero Trust → Access → Applications**](https://one.dash.cloudflare.com/access/apps) | ||
| 2. **Add an application** → Self-hosted | ||
| 3. Set the domain to `chat.your-domain.com` | ||
| 1. Go to [**Zero Trust → Access controls → Applications**](https://dash.cloudflare.com/?to=/:account/one/access-controls/apps) | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. https://one.dash.cloudflare.com/access/apps is also broken. The "Access" dashboard has been renamed to "Access controls". Other UI elements have changed slightly, so this updates the wording. |
||
| 2. **Create new application** → Self-hosted and private | ||
| 3. Set the public hostname to `chat.your-domain.com` | ||
| 4. Create an **Access Policy** (e.g., allow only `@your-company.com` emails) | ||
|
|
||
| Users see a Cloudflare login page before reaching Open WebUI. | ||
|
|
@@ -218,5 +218,5 @@ Users see a Cloudflare login page before reaching Open WebUI. | |
| | Start tunnel | `cloudflared tunnel run open-webui` | | ||
| | Add DNS | `cloudflared tunnel route dns open-webui chat.your-domain.com` | | ||
| | Install as service | `sudo cloudflared service install` | | ||
| | Dashboard | [one.dash.cloudflare.com/networks/tunnels](https://one.dash.cloudflare.com/networks/tunnels) | | ||
| | Dashboard | [https://dash.cloudflare.com/?to=/:account/one/networks/connectors](https://dash.cloudflare.com/?to=/:account/one/networks/connectors) | | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| | Set CORS origin | `CORS_ALLOW_ORIGIN=https://chat.your-domain.com` | | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://one.dash.cloudflare.com/networks/tunnels redirects to https://dash.cloudflare.com/one/networks/tunnels, which is a broken link.
https://dash.cloudflare.com/?to=/:account/one/networks/connectors is a smart link that redirects to the dashboard in the user's current account and to the new path where tunnels have been moved to under Connectors.