
TunnelMC
Expose any server port to the internet via ngrok and cloudflared tunnels — no extra port allocations needed.
Список изменений
🆕 What's New in 1.2.0
Cloudflared Support
Every tunnel now has its own provider field. Choose ngrok or cloudflared per tunnel, or mix them in the same config.
Cloudflared quick tunnels — zero account setup, random *.trycloudflare.com URL, HTTP only. Great for dashboards and web services.
Cloudflared named tunnels — paste a Cloudflare Zero Trust token and your custom hostname. Persistent URL, any protocol you've configured in Cloudflare.
Multiple ngrok Accounts
Each ngrok tunnel now has its own authtoken field (required for ngrok v3). Authtokens are passed as a CLI flag instead of writing to the global ngrok config, so you can run tunnels from completely different ngrok accounts at the same time.
Per-Tunnel Region
Each ngrok tunnel can set its own region, overriding the global default.
Web Dashboard
A full browser-based management dashboard on port 8090 (local only). From it you can:
- View all tunnels — status, URL, uptime, restarts
- Start / stop / restart tunnels individually
- Create, edit, and delete tunnels live — no server restart needed
- Download ngrok and cloudflared binaries with one click
- Edit all global settings
Auto-Expose on First Run
If no tunnels are configured, TunnelMC automatically downloads cloudflared and creates a quick tunnel to the dashboard on first startup so you can access it from anywhere right away.
Per-Tunnel Auto-Start
Each tunnel has its own auto-start field. Set it to true to start a tunnel on server boot even when global auto-start is off. The default dashboard tunnel ships with auto-start: true.
