# Pangolin: Free Open Source Alternative to Cloudflare Tunnels

Source: https://www.youtube.com/watch?v=CrM8uhD5BIs
Recap page: https://rapidrecap.app/video/CrM8uhD5BIs
Generated: 2026-03-06T09:04:00.376+00:00

---
## Quick Overview

The video successfully demonstrates deploying the open-source reverse proxy and VPN solution, Pangolin, using the Elestio platform, which involves setting up DNS records, running an installation script, and configuring a site resource to expose a local React application running on port 5174 to the internet securely via HTTPS.

**Key Points:**
- Pangolin, an open-source, identity-based remote access platform built on WireGuard, is deployed as a free alternative to Cloudflare Tunnels using Elestio's managed service.
- The deployment process requires setting up a wildcard DNS A record pointing to the VM's IP address on a custom domain provider (Cloudflare was used for the example domain 'causticlab.com').
- After service creation on Elestio, the user executes a script via the terminal (`/opt/app/install.sh`) to finalize the Pangolin setup, inputting the base domain ('demo-pangolin.causticlab.com').
- A new resource is created in Elestio under the 'Sites' section, named 'react three fiber', using the recommended 'Newt Tunnel' for connectivity.
- The local React application, running on port 5174, is exposed by configuring the resource's target to 'localhost:5174' via HTTP, which is then routed through the Pangolin tunnel.
- After saving the configuration, the deployed application is confirmed accessible online via the custom subdomain URL: https://myproject.demo-pangolin.causticlab.com.

![Screenshot at 00:04: The Elestio landing page is displayed, introducing Pangolin as an open-source, identity-based remote access platform built on WireGuard, emphasizing its capability for secure connectivity to private and public resources.](https://ss.rapidrecap.app/screens/CrM8uhD5BIs/00-00-04.jpg)

**Context:** The video provides a detailed tutorial on setting up Pangolin, an open-source identity-based remote access platform that utilizes WireGuard technology, as a free alternative to commercial solutions like Cloudflare Tunnels. The demonstration is conducted entirely within the Elestio cloud management interface, showcasing how to provision the Pangolin service, configure necessary networking prerequisites (DNS), and then deploy a sample local application (a React/Three Fiber project) through the established secure tunnel.

## Detailed Analysis

The tutorial begins by navigating to Elestio to deploy Pangolin, an open-source alternative to Cloudflare Tunnels. The deployment starts by selecting Pangolin from the available services (0:05), choosing a provider (Netcup is selected, 1:01), region, and service plan (MEDIUM-2C-4G, 1:03). After initiating deployment (0:56), the user receives an email confirming the service is ready (1:20). The critical next step involves configuring DNS, as Pangolin requires a custom domain; the user navigates to Cloudflare (1:54) to add a wildcard A record (e.g., *.demo-pangolin.causticlab.com) pointing to the VM's IP address (1:44). Following DNS setup, the user returns to the Elestio dashboard, opens the terminal for the new Pangolin instance (2:39), and runs the provided installation script (`/opt/app/install.sh`) (2:54), entering the base domain ('demo-pangolin.causticlab.com') when prompted (3:17). After the script successfully establishes the tunnel connection (5:55), the user creates a new 'Site' named 'react three fiber' (4:07) and configures the resource proxy settings (6:24). The resource is set to proxy HTTP requests using a subdomain ('myproject.demo-pangolin.causticlab.com') (6:38) to the local development server running on port 5174 (4:42). After saving the targets configuration, the application is accessible securely via HTTPS (7:45) at the custom URL, confirming the successful setup of Pangolin as a reverse proxy.

### Pangolin Deployment on Elestio

- Selecting Pangolin service on Elestio
- Choosing Netcup provider and MEDIUM-2C-4G plan
- Receiving service ready email after deployment

### Prerequisite

- DNS Configuration: Setting up a wildcard A record on the custom domain provider (Cloudflare) pointing to the VM's IP address
- This step is mandatory because Pangolin requires a custom domain, not the Elestio CNAME.

### Finalizing Installation via Terminal

- Executing the provided script (`/opt/app/install.sh`) in the instance terminal
- Inputting the base domain ('demo-pangolin.causticlab.com') when prompted by the script
- Confirmation of successful tunnel connection to the server.

### Exposing Local Project

- Navigating to 'Resources' in Elestio to create a new site named 'react three fiber'
- Selecting 'HTTPS Resource' type
- Configuring the target as 'localhost:5174' where the local Vite server is running (4:41).

### Verification

- Accessing the application online via the custom subdomain URL (e.g., https://myproject.demo-pangolin.causticlab.com)
- Observing the local React application (a rotating cube) loading successfully through the tunnel (7:35).

![Screenshot at 0:04: The presenter introduces Pangolin on the Elestio homepage, highlighting it as an open-source, identity-based remote access platform built on WireGuard.](https://ss.rapidrecap.app/screens/CrM8uhD5BIs/00-00-04.jpg)
![Screenshot at 1:00: The user searches for 'Pangolin' in the Elestio service catalog and selects the option to create a new service instance.](https://ss.rapidrecap.app/screens/CrM8uhD5BIs/00-01-00.jpg)
![Screenshot at 1:53: The user is viewing the Network details in the Elestio dashboard, specifically copying the IPv4 address needed for DNS configuration.](https://ss.rapidrecap.app/screens/CrM8uhD5BIs/00-01-53.jpg)
![Screenshot at 7:22: The user edits the vite.config.js file to add the server.allowedHosts configuration required to bypass Vite's host restriction error.](https://ss.rapidrecap.app/screens/CrM8uhD5BIs/00-07-22.jpg)
