Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
2023-01-14T21:40:45Z INF Starting metrics server on 127.0.0.1:34243/metrics 2023/01/14 21:40:45 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details. 2023-01-14T21:40:45Z INF Connection a42de43d-f3f5-xxxxxxxxxxxxx registered with protocol: quic connIndex=0 ip=198.41.192.7 location=LHR 2023-01-14T21:40:46Z INF Connection bc3c09bd-3f4c-xxxxxxxxxxxxx 1 registered with protocol: quic connIndex=1 ip=198.41.200.73 location=MAN 2023-01-14T21:40:47Z INF Connection 381ce22c-f5e1-xxxxxxxxxxxxx registered with protocol: quic connIndex=2 ip=198.41.200.193 location=MAN 2023-01-14T21:40:48Z INF Connection 38bde5a9-b5b9-xxxxxxxxxxxxx registered with protocol: quic connIndex=3 ip=198.41.192.47 location=LHR 2023-01-14T21:46:58Z INF Updated to new configuration config="{\"ingress\":[{\"service\":\"http://192.168.1.64:13378\",\"hostname\":\"apachetomcat.crispybegs.com\"},{\"service\":\"http_status:404\"}],\"warp-routing\":{\"enabled\":false}}" version=1 2023-01-14T21:48:59Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.64:5055: i/o timeout" cfRay=7899937bxxxxx-LHR ingressRule=1 originService=http://192.168.1.64:5055 2023-01-14T21:48:59Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.64:5055: i/o timeout" connIndex=0 dest=https://overseer.crispybegs.com/ ip=198.41.192.7 type=http 2023-01-14T21:49:19Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.64:13378: i/o timeout" cfRay=789993fa1xxxxx-LHR ingressRule=0 originService=http://192.168.1.64:13378 2023-01-14T21:49:19Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.64:13378: i/o timeout" connIndex=0 dest=https://apachetomcat.crispybegs.com/ ip=198.41.192.7 type=http 2023-01-14T21:49:30Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.64:5055: i/o timeout" cfRay=7899943a9xxxxx-LHR ingressRule=1 originService=http://192.168.1.64:5055 2023-01-14T21:49:30Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.64:5055: i/o timeout" connIndex=0 dest=https://overseer.crispybegs.com/favicon.ico ip=198.41.192.7 type=http 2023-01-14T21:49:50Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.64:13378: i/o timeout" cfRay=789994b8cexxxxx-LHR ingressRule=0 originService=http://192.168.1.64:13378 2023-01-14T21:49:50Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.64:13378: i/o timeout" connIndex=0 dest=https://apachetomcat.crispybegs.com/favicon.ico ip=198.41.192.7 type=http 2023-01-14T22:00:16Z INF Updated to new configuration config="{\"ingress\":[{\"service\":\"https://192.168.1.64:13378\",\"hostname\":\"apachetomcat.crispybegs.com\",\"originRequest\":{\"noTLSVerify\":true}},{\"hostname\":\"overseer.crispybegs.com\",\"originRequest\":{},\"service\":\"http://192.168.1.64:5055\"},{\"service\":\"http_status:404\"}],\"warp-routing\":{\"enabled\":false}}" version=3 2023-01-14T22:00:59Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.64:13378: i/o timeout" cfRay=7899a50d3axxxxx-LHR ingressRule=0 originService=https://192.168.1.64:13378
Some hints how to debug such problems in the future: 1. ufw drops/rejections are logged (use dmesg to view them) 2. wireshark shows all connection attempts, even those that are blocked by firewall 3. ss or netstat shows if the server is actually listening for connections 4. netshoot allows to enter docker container network namespace and do pings, curl or telnet from there