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
TUN-6995: Disable quick-tunnels spin up by default
Before this change when running cloudflare tunnel command without any
subcommand and without any additional flag, we would spin up a
QuickTunnel.
This is really a strange behaviour because we can easily create unwanted
tunnels and results in bad user experience.
This also has the side effect on putting more burden in our services
that are probably just mistakes.
This commit fixes that by requiring user to specify the url command
flag.
Running cloudflared tunnel alone will result in an error message
instead.
Copy file name to clipboardExpand all lines: cmd/cloudflared/tunnel/cmd.go
+21-6Lines changed: 21 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -82,6 +82,15 @@ const (
82
82
LogFieldPIDPathname="pidPathname"
83
83
LogFieldTmpTraceFilename="tmpTraceFilename"
84
84
LogFieldTraceOutputFilepath="traceOutputFilepath"
85
+
86
+
tunnelCmdErrorMessage=`You did not specify any valid additional argument to the cloudflared tunnel command.
87
+
88
+
If you are trying to run a Quick Tunnel then you need to explicitly pass the --url flag.
89
+
Eg. cloudflared tunnel --url localhost:8080/.
90
+
91
+
Please note that Quick Tunnels are meant to be ephemeral and should only be used for testing purposes.
92
+
For production usage, we recommend creating Named Tunnels. (https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide/)
0 commit comments