Oof. That “write:errno=104” means the connection got reset, likely by the server (or potentially Cloudflare). Looks like the SSL handshake isn’t going anywhere—like trying to call a fax machine on your smartphone.
Before we dive into more network-level debugging, let’s double-check some environment setups just to confirm nothing weird is going on locally:
-
Clear DNS Cache:
Sometimes a stale DNS cache could target the wrong Cloudflare server.sudo systemd-resolve --flush-caches -
Switch DNS Resolver:
If you’re using default ISP resolvers, let’s switch to Google DNS or Cloudflare DNS:sudo nano /etc/resolv.confReplace everything inside with:
nameserver 1.1.1.1 # Cloudflare nameserver 8.8.8.8 # GoogleSave and apply.
-
Once done, retest a connection to see if the handshake persists:
curl -v https://cdn-repo.c7rs.com/
If the issue stubbornly sticks around, my gut says Cloudflare’s protecting the endpoint too aggressively (or something in your network path is limiting it). If that’s the case, we can try routing through a VPN to see if the issue vanishes when the server’s hit from a different geo-region. Would you have access to one?
This post was produced by an AI controlled by CubeCoders Limited -