Configuration to review
- Tunnel token
- Internal service targets
- Public hostnames
- Access policies in Cloudflare
Cloudflared is the connector used by Cloudflare Tunnel to publish private services through Cloudflare without directly opening inbound application ports. MyVibe runs the cloudflared connector with a tunnel token or credentials and routes selected internal services through the configured Cloudflare tunnel.
Ready environment
Networking
Secure tunnels
Private apps
Recommended MyVibe plan
Start or Plus for access tools; Builder if paired with many private services.
Application overview
Cloudflared is the connector used by Cloudflare Tunnel to publish private services through Cloudflare without directly opening inbound application ports.
MyVibe runs the cloudflared connector with a tunnel token or credentials and routes selected internal services through the configured Cloudflare tunnel.
Read the official Cloudflared documentationTechnical details reviewed:
Ready template
Application configuration
MyVibe keeps deployment controls in one panel while the application runs within your selected VPS resources.
Start is normally sufficient for the connector itself. Size the plan for the applications and traffic that share the same MyVibe server.
Compare MyVibe plansWhat you get in MyVibe
Run tunnel, mesh, and private network clients to connect MyVibe services with private devices, edge networks, or secure admin paths.
Deploy app code and services from repositories when your workflow needs source-controlled releases.
Attach custom domains and run production-ready endpoints with HTTPS.
Pair apps with PostgreSQL, MySQL, MongoDB, Redis, object storage, automation tools, and more.
Manage runtime values and inspect app behavior without turning every task into SSH work.
Your CPU, RAM, storage, and bandwidth define how many apps and services you can run.
Use a real VPS foundation with MyVibe deployment controls layered on top.
Inside the MyVibe panel
Cloudflared on MyVibe is a ready environment for safely exposing selected internal services. It starts from a curated service template, then you manage domains, SSL, variables, logs, storage, and related services from the MyVibe panel.
Networking template on MyVibe
Cloudflared
Tunnel
Managed in MyVibe
Mesh
Managed in MyVibe
DNS
Managed in MyVibe
Access
Managed in MyVibe
Source-informed controls
Based on the networking service category and application port/access controls.
Use cases
Safely exposing selected internal services.
Deployment flow
MyVibe keeps the flow simple without hiding the server resources you own.
Compare related ready-to-use applications that can run on the same MyVibe platform.
Common questions
MyVibe runs the cloudflared connector with a tunnel token or credentials and routes selected internal services through the configured Cloudflare tunnel.
The template includes Cloudflared connector, Tunnel credentials, Ingress rules, Private service routes. You can review domains, SSL, environment variables, storage, logs, and service resources from MyVibe.
Start is normally sufficient for the connector itself. Size the plan for the applications and traffic that share the same MyVibe server.
MyVibe simplifies deployment and runtime controls. You remain responsible for application configuration, data protection, and compatible updates. Recommended tasks include: Protect tunnel credentials; Review ingress routes; Monitor connector logs; Manage DNS and access from Cloudflare.
Start with the server size that fits your workload. Upgrade later when your apps, users, or databases grow.