starred/panel
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-07-16 05:53:54 +03:00
Code Issues 42 Packages Projects Releases 14 Wiki Activity

[PR #1945] [CLOSED] Add Cloudflared configuration with Internet & Internet+LAN examples #1668

New Issue
Closed
opened 2026-02-04 20:06:37 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-04 20:06:37 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/panel/pull/1945
Author: @k3vmcd
Created: 11/29/2025
Status: ❌ Closed

Base: main ← Head: cloudflared

📝 Commits (4)

  • 479919e Add Cloudflare Tunnel example with configuration files and usage instructions
  • a8018c1 Refactor Cloudflare Tunnel configuration to use environment variables for better flexibility
  • 5e65a04 Add PHP upload limit configuration and update related files
  • 37cf975 Add Cloudflare Tunnel + LAN example

📊 Changes

8 files changed (+226 additions, -0 deletions)

View changed files

➕ examples/cloudflare-tunnel-lan/.env.example (+22 -0)
➕ examples/cloudflare-tunnel-lan/Caddyfile (+38 -0)
➕ examples/cloudflare-tunnel-lan/README.md (+24 -0)
➕ examples/cloudflare-tunnel-lan/docker-compose.yml (+43 -0)
➕ examples/cloudflare-tunnel/.env.example (+19 -0)
➕ examples/cloudflare-tunnel/Caddyfile (+18 -0)
➕ examples/cloudflare-tunnel/README.md (+20 -0)
➕ examples/cloudflare-tunnel/docker-compose.yml (+42 -0)

📄 Description

This pull request adds two new example configurations for running Pelican Panel behind a Cloudflare Tunnel, with one variant also supporting secure LAN access via HTTPS. Each example includes a complete Docker Compose stack, Caddy server configuration, environment variable templates, and documentation to help users deploy Pelican Panel securely in different network scenarios.

Cloudflare Tunnel + LAN HTTPS Example:

Configuration and documentation:

  • Added the cloudflare-tunnel-lan example with a full docker-compose.yml stack that binds HTTPS on a specified LAN IP for local clients, while keeping Cloudflare Tunnel for remote access.
  • Provided a Caddyfile that serves the app over HTTP for the tunnel and HTTPS (with internal CA) for LAN traffic, including support for higher PHP upload limits.
  • Added a .env.example file with new variables such as LAN_BIND_ADDRESS to help users configure LAN HTTPS access.
  • Included a detailed README.md explaining setup steps, LAN certificate trust, and DNS configuration for split-horizon access.

Cloudflare Tunnel Example (Internet-only):

Configuration and documentation:

  • Added the cloudflare-tunnel example with a minimal Docker Compose stack for serving Pelican Panel exclusively through Cloudflare Tunnel, keeping host ports closed.
  • Provided a Caddyfile tuned for reverse proxy and upload limits, and a .env.example template for required environment variables. [1] [2]
  • Included a concise README.md guiding users through tunnel setup and deployment.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/pelican-dev/panel/pull/1945 **Author:** [@k3vmcd](https://github.com/k3vmcd) **Created:** 11/29/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `cloudflared` --- ### 📝 Commits (4) - [`479919e`](https://github.com/pelican-dev/panel/commit/479919e53ca1acefa0d0d82f9d40a69b1131ff09) Add Cloudflare Tunnel example with configuration files and usage instructions - [`a8018c1`](https://github.com/pelican-dev/panel/commit/a8018c177b00a02cb4cd7c2c3738f6928038ff7d) Refactor Cloudflare Tunnel configuration to use environment variables for better flexibility - [`5e65a04`](https://github.com/pelican-dev/panel/commit/5e65a04982f6e39fcc51cc7bea02bbec2ab7d58e) Add PHP upload limit configuration and update related files - [`37cf975`](https://github.com/pelican-dev/panel/commit/37cf975bef22d55fef9b47d0c4c537ab161c1fe7) Add Cloudflare Tunnel + LAN example ### 📊 Changes **8 files changed** (+226 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `examples/cloudflare-tunnel-lan/.env.example` (+22 -0) ➕ `examples/cloudflare-tunnel-lan/Caddyfile` (+38 -0) ➕ `examples/cloudflare-tunnel-lan/README.md` (+24 -0) ➕ `examples/cloudflare-tunnel-lan/docker-compose.yml` (+43 -0) ➕ `examples/cloudflare-tunnel/.env.example` (+19 -0) ➕ `examples/cloudflare-tunnel/Caddyfile` (+18 -0) ➕ `examples/cloudflare-tunnel/README.md` (+20 -0) ➕ `examples/cloudflare-tunnel/docker-compose.yml` (+42 -0) </details> ### 📄 Description This pull request adds two new example configurations for running Pelican Panel behind a Cloudflare Tunnel, with one variant also supporting secure LAN access via HTTPS. Each example includes a complete Docker Compose stack, Caddy server configuration, environment variable templates, and documentation to help users deploy Pelican Panel securely in different network scenarios. **Cloudflare Tunnel + LAN HTTPS Example:** Configuration and documentation: * Added the `cloudflare-tunnel-lan` example with a full `docker-compose.yml` stack that binds HTTPS on a specified LAN IP for local clients, while keeping Cloudflare Tunnel for remote access. * Provided a `Caddyfile` that serves the app over HTTP for the tunnel and HTTPS (with internal CA) for LAN traffic, including support for higher PHP upload limits. * Added a `.env.example` file with new variables such as `LAN_BIND_ADDRESS` to help users configure LAN HTTPS access. * Included a detailed `README.md` explaining setup steps, LAN certificate trust, and DNS configuration for split-horizon access. **Cloudflare Tunnel Example (Internet-only):** Configuration and documentation: * Added the `cloudflare-tunnel` example with a minimal Docker Compose stack for serving Pelican Panel exclusively through Cloudflare Tunnel, keeping host ports closed. * Provided a `Caddyfile` tuned for reverse proxy and upload limits, and a `.env.example` template for required environment variables. [[1]](diffhunk://#diff-56f98a08ebf627c90788528fe5fa1296dae2192ffdc54252505886f86715908dR1-R18) [[2]](diffhunk://#diff-bbb8bd91a1cb860a42cecbb650472d452d8631ba2da4e38dab44a93072cb9b86R1-R19) * Included a concise `README.md` guiding users through tunnel setup and deployment. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-04 20:06:37 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel#1668
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?