![big ip edge client internet connection lost big ip edge client internet connection lost](https://www.windowslatest.com/wp-content/uploads/2020/07/EnableActiveProbing.jpg)
The first thought is about Internet stability. The SYN packets went off over loopback to localhost but were never answered. Well, we called connect() to localhost and it timed out. This takes a long time and eventually fails with ETIMEDOUT error. Netcat calls connect() to establish a connection to localhost. The view from strace: socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 3Ĭonnect(3,, 16) = -110 ETIMEDOUT Nc: connect to 127.0.0.1 port 5000 (tcp) failed: Connection timed out After a couple of dozen of runs this is what we saw: $ nc 127.0.0.1 5000 -v Once we knew what to look for we were able to reproduce this with good old netcat. To be precise, an NGINX instance was trying to establish a TCP connection to our internal acceleration service on localhost. After a lot of debugging we identified an important symptom: sometimes, once in thousands of runs, our test program failed to establish a connection between two daemons on the same machine.
![big ip edge client internet connection lost big ip edge client internet connection lost](https://cdn.windowsreport.com/wp-content/uploads/2020/03/No-Internet-connection-after-installing-Windows-updates.jpg)
The root cause of this issue was pretty complex. The internet connectivity between CloudFlare and origin was perfect. In the case I was debugging it was neither.
#Big ip edge client internet connection lost Offline
Most often the blame is on the origin server side - the origin server is slow, offline or encountering high packet loss. Apparently every now and then a connection going through CloudFlare would time out with 522 HTTP error.ĥ22 error on CloudFlare indicates a connection issue between our edge server and the origin server. I was asked to debug another weird issue on our network.