As the documentation is wrong and in now way clear how does one installed the cloudflared daemon so that the argo tunnel starts automatically ???
I managed to work it out. As I advice the support team the documentation really need to be updated.
Now that I have Argo Tunnel working and know the setup it is very easy.
Which part of the documentation is wrong?
How long does it take for the service to take into effect? I still can connect to my original IP.
For one, the page at https://developers.cloudflare.com/argo-tunnel/reference/arguments/ has no documentation for the dns-proxy command nor the associated configuration.
Further lack of documentation is compounded by the barrier to learning in the fact that the key names in the YAML file do not match up with the command-line arguments. For example, in command line " –upstream " to specify an upstream server, you type:
--upstream https://22.214.171.124/dns-query https://126.96.36.199/dns-query.
Confusingly… in the YAML file, it is proxy-dns-upstream
proxy-dns-upstream: - https://188.8.131.52/dns-query - https://184.108.40.206/dns-query
This is just one of many that differ.
It would be nice to actually have the command line commands align 1:1 with the YAML.
[Request] Unify Argo cli Keys with YAML Keys
Seems dead around here. I just clicked on threads tagged:argo and most of the inquiries closed due to no response (no response by staff). CloudFlare should step up their game on addressing and responding to the community threads.
Especially bugs that are filed and opened for 8 months. https://github.com/cloudflare/cloudflared/issues/7
Best part is, we do pay $5,000/mo at my workplace for them. Guess I need to squeak up to get some grease.
I played with the Argo smart routing on my personal site at home and did see some gain, but only for distant connections. If the traffic was coming from stateside, the smart routing didn’t gain much, and was costing me money to only improve latency ~10 ms for a fraction of the stateside traffic – but the majority of the stateside traffic had slightly increased latency (less than 10ms) and was just costing me money. In my opinion, it can be good if you’re dealing with traffic on the other side of the world, but it isn’t 100% accurate on the decision making once you start dealing with traffic that is close to origin; the latency differentials become more and more of a draw.
My current frustration with Argo is that there are known bugs and lacking documentation, and it seems like it’s not seeing any progress on the Argo client. I’m not trying to bash CloudFlare here, but it seems to be a Beta despite being out of beta, at least that is how it appears to me with the argo client development progress. I’m still hoping they will see this and make some operational improvements to their product development.
Can you link back to that post? I’d like to see what I overlooked so it doesn’t happen again. Thank you.
UPDATE: It looks like Ben deleted his post. Going back through this thread, I see ‘webmaster’ was kind enough to post the link and describe the issue after I asked for clarification. I guess Ben’s rant was not directed at me.
If you want a response from Cloudflare staff, open a support ticket. This is a community meaning that most of the users here are just Cloudflare customers themselves. I think it is very unreasonable to expect response as you would expect with a support ticket as most people here are volunteers, giving up their own time to help out others who are having issues with their sites.
Hi! Zack from the Argo Tunnel team here. I’m sorry you ran into those issues. There’s no doubt the API docs could be more clear, and the YAML format could be closer to the command line arguments. They’re both things we’re trying to improve over time. In general the Argo Tunnel documentation doesn’t document DNS arguments as 220.127.116.11 is actually not a part of the Argo Tunnel product, it’s a separate feature of the cloudflared client. We’re working on making that separation more clear and providing a single place to go for all cloudflared help, but it’s a work in progress.
18.104.22.168 is primarily a project for the community, please by all means feel free to make a pull request to cloudflared with the changes you think are appropriate, we would be happy to review.