Your tunnels.
In plain sight.
Cloudflare Tunnel routes and Access applications, together. A self-hosted dashboard for the services you run.
Install with dockerLinux AMD64 & ARM64
Less digging.
More doing.
- Follow every route.
- Inspect tunnels and their published routes in a canvas or a list. Search by hostname and filter by matching Access application.
- Access first. Route second.
- Create and verify an Access application with your existing policies before publishing DNS and the tunnel route, in one New service flow.
- Keep it on your own ground.
- Run the dashboard on your infrastructure. Saved Cloudflare credentials are encrypted and persist across container restarts.
Install with docker.
Pull it. Run it.
With Docker installed, pull the image from GitHub Container Registry and start the dashboard. Docker selects the AMD64 or ARM64 image for your machine.
The edge tag follows development on main. Versioned tags and latest are published with GitHub Releases.
docker pull ghcr.io/pitu/mogura:edge
docker run -d --name mogura \
--restart unless-stopped \
-p 127.0.0.1:3000:3000 \
-v mogura-data:/data \
ghcr.io/pitu/mogura:edge- Open the dashboard.
On the Docker host, open localhost:3000. The command binds to loopback.
- Connect Cloudflare.
Enter your account ID and API token in Settings. No environment file is needed for this connection method.
- Keep your connection.
Retain the
mogura-datavolume when updating. It stores the encryption key and saved credentials.
Build from source
Prefer a local build? Clone the GitHub repository and use the included Compose configuration.
git clone https://github.com/Pitu/mogura.git
cd mogura
docker compose up -d --buildCompose keeps its data in the dashboard-data volume. See the README for configuration and updates.
API token permissions
Scope the token to your account and the zones you manage.
- Account: Cloudflare Tunnel: Edit
- Account: Access: Apps and Policies: Edit
- Zone: Zone: Read
- Zone: DNS: Edit, when creating DNS records
Before exposing the dashboard
The dashboard has no separate user login. Protect it with Cloudflare Access before exposing it to the internet. Everyone who can reach it shares its saved credentials.
Set APP_ORIGIN to your dashboard’s HTTPS origin when publishing through a tunnel. This is the application address, separate from this landing page.
The local default is http://localhost:3000. For a public tunnel, set APP_ORIGIN to your own HTTPS origin, for example https://dashboard.example.com. If cloudflared runs on the host, point it to http://localhost:3000. In a shared Docker network, use http://dashboard:3000.
Follow the project.
Read the code, report an issue, or follow upcoming releases on GitHub.
Browse the published images in GitHub Packages.