Open remorses opened 1 month ago
I think i managed to get this working, congrats on making the most user hostile cli i ever used, and i used a lot of clis
cloudflared tunnel token --cred-file .cloudflared/tunnel.json tunnel-name
.cloudflared/config.yml
and add the contents
tunnel: tunnel-name
credentials-file: ./.cloudflared/tunnel.json
cloudflared tunnel --config ./.cloudflared/config.yml run --url http://localhost:8040 tunnel-name
. Notice how you have to pass the config manually and not after run because otherwise it breaks. Cloudflared only searches ~/.cloudflared
because everyone knows non reproducible user based global configs are the best
Describe the feature you'd like Currently to create a tunnel you have to run the following commands (dx is already very bad, should be 1 command)
This won't create a tunnel on tunnel.example.com if for some reason you used the cloudflared on another domain previously (for example x.com), instead it will create one on
tunnel.example.com.x.com
Describe alternatives you've considered Use the website with domain example.com if i am trying to create a tunnel there, not tunnel.example.com.x.com
Additional context Maybe you have to run
cloudflared tunnel login
again? But there is only 1 global cloudflared config at/Users/user/.cloudflared/cert.pem
, this doesn't make sense