You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment we can create tunnels through the Cloudflare web dashboard. But these tunnels when started with the provided token on a Kubernetes cluster has full access to everything. We can just configure in the dashboard what we want a domain to point to. That makes the Cloudflare dashboard very vulnerable from a security perspective.
I would like to be able to create a tunnel in the dashboard, but then when starting the Cloudflared container be able to specify which ips/hosts/ports should be allowed and which should be blocked.
Describe alternatives you've considered
Making manual tunnels using a config file. But loses the advantages of the dashboard
The text was updated successfully, but these errors were encountered:
maggie44
changed the title
💡allow dashboard tunnel creation and route limits simultaneously
💡Allow dashboard tunnel creation and route limits simultaneously
Aug 13, 2024
Describe the feature you'd like
At the moment we can create tunnels through the Cloudflare web dashboard. But these tunnels when started with the provided token on a Kubernetes cluster has full access to everything. We can just configure in the dashboard what we want a domain to point to. That makes the Cloudflare dashboard very vulnerable from a security perspective.
I would like to be able to create a tunnel in the dashboard, but then when starting the Cloudflared container be able to specify which ips/hosts/ports should be allowed and which should be blocked.
Describe alternatives you've considered
Making manual tunnels using a config file. But loses the advantages of the dashboard
The text was updated successfully, but these errors were encountered: