7 comments

[ 3.3 ms ] story [ 22.0 ms ] thread
"Here are why"? That doesn't appear in the article at all, let alone in its title.
I think op/author may not be a native English speaker and the title is indicative of the gist of the article.
The more important question: why not?
Because, as proven last week, you're also adding another point of potential failure.
One of my favorite CloudFlare products is Argo.

I recently shipped a RaspberryPi-controlled device to a client. Its API needed to be exposed to the internet securely and with little hassle. Doing this with Argo was super simple: Install the daemon and configure it to expose the internal web server port on some subdomain. When the device arrived in the client's hand, they only had to power it on.

This is similar to ngrok, etc, but more production focused and gives you all features of CloudFlare out of the box.

Sites hosted behind cloudflare have been down for me for 8 days now. It seems like there’s something up with TLS connections.

As a user, there is no easy recourse. I had to create an account on dash.cloudflare.com, which I was able to do after SSH tunneling to another server and doing a SOCKS proxy. This because they don’t accept emails to support@cloudflare.com unless you have created an account.

Once you open a ticket, you are doing so from a free account, because you are not the user. You are not prioritized.

I have no idea why I can’t access tons of sites right now, but it’s fucking frustrating. I’m in Chile and all the VPNs I can use are in the US so that makes for a terrible browsing experience.

This has really slowed me down this week. If I didn’t have a VPN, like most people in Chile, I’m sure a small part of the internet just be broken.

Please email jgc AT cloudflare DOT com so we can see what's going on.