3 ms·

All our sites using Argo Tunnels go down whenever the API goes down, but the dashboard still claims Argo Tunnels are unaffected :/ At least we'll get a good bl

All our sites using Argo Tunnels go down whenever the API goes down, but the dashboard still claims Argo Tunnels are unaffected :/ At least we'll get a good blog post out of it in a few days.

jbergstroem 7y ago
Yes, same here -- which equals site down. Nothing on status page yet. > Apr 15 17:01:37 mysite cloudflared[12412]: time="2020-04-15T17:01:37Z" level=info msg="Connected to SJC" connectionID=0 > Apr 15 17:03:09 mysite cloudflared[12412]: time="2020-04-15T17:03:09Z" level=error msg="Register tunnel error from server side" connectionID=0 error="Server error: Reached maximum retry 5: dial tcp 198.41.248.96:9100: connect: connection timed out" > Apr 15 17:03:09 mysite cloudflared[12412]: time="2020-04-15T17:03:09Z" level=info msg="Retrying in 8s seconds" connectionID=0
- nikisweeting 7y ago
  Here's our logs in case it helps anyone: > hera ra | time="2020-04-15T17:08:09Z" level=error msg="Unable to dial edge" error="DialContext error: dial tcp 198.41.200.233:7844: i/o timeout" > hera | time="2020-04-15T17:08:09Z" level=info msg="Retrying in 1s seconds" hera | time="2020-04-15T17:08:09Z" level=error msg="Unable to dial edge" error="Handshake with edge error: read tcp 172.18.0.2:36016->198.41.192.227:7844: i/o timeout" > hera | time="2020-04-15T17:08:09Z" level=info msg="Retrying in 1s seconds" hera | time="2020-04-15T17:08:11Z" level=error msg="Unable to dial edge" error="Handshake with edge error: read tcp 172.18.0.2:44626->198.41.192.7:7844: i/o timeout" > hera | time="2020-04-15T17:08:11Z" level=info msg="Retrying in 4s seconds" > hera | time="2020-04-15T17:08:13Z" level=info msg="Connected to EWR" > hera | time="2020-04-15T17:08:13Z" level=error msg="Register tunnel error from server side" connectionID=0 error="Server error: Reached maximum retry 5: dial tcp 198.41.248.96:9100: connect: connection timed out" > hera | time="2020-04-15T17:08:13Z" level=warning msg="Tunnel disconnected due to error" error="Server error: Reached maximum retry 5: dial tcp 198.41.248.96:9100: connect: connection timed out" > hera | time="2020-04-15T17:08:19Z" level=error msg="Unable to dial edge" error="Handshake with edge error: read tcp 172.18.0.2:51974->198.41.192.107:7844: i/o timeout"
rkwasny 7y ago
What's worse is that a status page is making it look like we are down and cloudflare is up...
- deleted 7y ago
  [deleted]
inapis 7y ago
Does Argo help much with performance? How much of a difference are we talking about here?
- robertcope 7y ago
  Argo is kind of an overloaded term... Argo (not tunneling) is better routing from the edge, which can have a measurable impact on performance. Argo (tunneling) can also impact performance in a positive way but it is also a nice way to secure things, provide access to secure/internal sites, provide ssh/rdp access into a datacenter, and other things.
- buildbuildbuild 7y ago
  Argo Tunnels are most useful for security: you can serve HTTP from a server that allows no inbound connections. Or, you can use it to reliably serve a public site from behind NAT. Argo routing’s ability to improve page load times depends on how international your user base is, and how poor your origin’s transit quality is. It’s great at improving the latency and reliability of a cheap host.
buildbuildbuild 7y ago
Confirmed, and an interesting opportunity to spot who is using Argo Tunnels based on their current downtime. Tunnels are one of Cloudflare’s best features for developers, instant NAT traversal for home-hosted demos and prototypes. It’s a shame you have to pay for Argo on your entire domain in order to use Argo Tunnels even on one subdomain. Cloudflare, please offer origin tunnels as a separate service rather than bundling it with Argo routing on the client side.
- jbergstroem 7y ago
  I believe they are separate; its just naming confusion. One is called "tiered routing" and is a dropdown in settings whereas the "nat" solution nowadays is implemented as cloudflared.
robertcope 7y ago
Yup, I am emailed my account rep about Argo tunnels being down and the status page not really reflecting that issue... which is much larger than the dashboard being offline or APIs not working, IMHO.
rohansingh 7y ago
Dashboard must have updated, because it now says that Argo Tunnels is offline.

All our sites using Argo Tunnels go down whenever the API goes down, but the dashboard still claims Argo Tunnels are unaffected :/ At least we'll get a good blog post out of it in a few days.

jbergstroem 7y ago

Yes, same here -- which equals site down. Nothing on status page yet. > Apr 15 17:01:37 mysite cloudflared[12412]: time="2020-04-15T17:01:37Z" level=info msg="Connected to SJC" connectionID=0 > Apr 15 17:03:09 mysite cloudflared[12412]: time="2020-04-15T17:03:09Z" level=error msg="Register tunnel error from server side" connectionID=0 error="Server error: Reached maximum retry 5: dial tcp 198.41.248.96:9100: connect: connection timed out" > Apr 15 17:03:09 mysite cloudflared[12412]: time="2020-04-15T17:03:09Z" level=info msg="Retrying in 8s seconds" connectionID=0

nikisweeting 7y ago
Here's our logs in case it helps anyone: > hera ra | time="2020-04-15T17:08:09Z" level=error msg="Unable to dial edge" error="DialContext error: dial tcp 198.41.200.233:7844: i/o timeout" > hera | time="2020-04-15T17:08:09Z" level=info msg="Retrying in 1s seconds" hera | time="2020-04-15T17:08:09Z" level=error msg="Unable to dial edge" error="Handshake with edge error: read tcp 172.18.0.2:36016->198.41.192.227:7844: i/o timeout" > hera | time="2020-04-15T17:08:09Z" level=info msg="Retrying in 1s seconds" hera | time="2020-04-15T17:08:11Z" level=error msg="Unable to dial edge" error="Handshake with edge error: read tcp 172.18.0.2:44626->198.41.192.7:7844: i/o timeout" > hera | time="2020-04-15T17:08:11Z" level=info msg="Retrying in 4s seconds" > hera | time="2020-04-15T17:08:13Z" level=info msg="Connected to EWR" > hera | time="2020-04-15T17:08:13Z" level=error msg="Register tunnel error from server side" connectionID=0 error="Server error: Reached maximum retry 5: dial tcp 198.41.248.96:9100: connect: connection timed out" > hera | time="2020-04-15T17:08:13Z" level=warning msg="Tunnel disconnected due to error" error="Server error: Reached maximum retry 5: dial tcp 198.41.248.96:9100: connect: connection timed out" > hera | time="2020-04-15T17:08:19Z" level=error msg="Unable to dial edge" error="Handshake with edge error: read tcp 172.18.0.2:51974->198.41.192.107:7844: i/o timeout"

rkwasny 7y ago

What's worse is that a status page is making it look like we are down and cloudflare is up...

deleted 7y ago
[deleted]

inapis 7y ago

Does Argo help much with performance? How much of a difference are we talking about here?

robertcope 7y ago
Argo is kind of an overloaded term... Argo (not tunneling) is better routing from the edge, which can have a measurable impact on performance. Argo (tunneling) can also impact performance in a positive way but it is also a nice way to secure things, provide access to secure/internal sites, provide ssh/rdp access into a datacenter, and other things.
buildbuildbuild 7y ago
Argo Tunnels are most useful for security: you can serve HTTP from a server that allows no inbound connections. Or, you can use it to reliably serve a public site from behind NAT. Argo routing’s ability to improve page load times depends on how international your user base is, and how poor your origin’s transit quality is. It’s great at improving the latency and reliability of a cheap host.

buildbuildbuild 7y ago

Confirmed, and an interesting opportunity to spot who is using Argo Tunnels based on their current downtime. Tunnels are one of Cloudflare’s best features for developers, instant NAT traversal for home-hosted demos and prototypes. It’s a shame you have to pay for Argo on your entire domain in order to use Argo Tunnels even on one subdomain. Cloudflare, please offer origin tunnels as a separate service rather than bundling it with Argo routing on the client side.

jbergstroem 7y ago
I believe they are separate; its just naming confusion. One is called "tiered routing" and is a dropdown in settings whereas the "nat" solution nowadays is implemented as cloudflared.

robertcope 7y ago

Yup, I am emailed my account rep about Argo tunnels being down and the status page not really reflecting that issue... which is much larger than the dashboard being offline or APIs not working, IMHO.

rohansingh 7y ago

Dashboard must have updated, because it now says that Argo Tunnels is offline.