Network errors (net::ERR_CONNECTION_RESET, net::ERR_QUIC_PROTOCOL_ERROR, "The network connection kept dropping")
Connection drops between your computer and Microsoft 365 or Google. The app retries by itself; if a few files still fail, retry the failed items.
What it means
The connection to SharePoint or Google broke in the middle of a request:
net::ERR_CONNECTION_RESET,ECONNRESET,socket hang up,terminated,fetch failed– the other side or something in between (VPN, proxy, firewall, Wi-Fi) closed the connection.net::ERR_QUIC_PROTOCOL_ERROR– QUIC (HTTP/3), which some firewalls and proxies don't handle. Current versions turn QUIC off, so traffic uses ordinary HTTPS.Transient failure– SharePoint itself asked to try again later.
What the app does
- Every SharePoint request that drops is tried again, with a pause that grows each time (more attempts for dropped connections than for other errors). An interrupted upload restarts from the beginning.
- A Google Drive download that drops while the file is being read is fetched again, up to 4 times (version 1.0.48 and later).
- Only when every attempt fails is the item logged as an error: "The network connection kept dropping (…) – tried N times. Check the VPN, proxy or Wi-Fi, then use Retry failed items."
How to fix it
- Update the app to the latest version.
- Click Retry N failed items in the task's report – only the failed files are copied. See Retry failed items.
- If many files fail:
- Use a wired connection, or pause the VPN if your policy allows.
- Ask your network team to allow
*.sharepoint.com,login.microsoftonline.com,graph.microsoft.com,*.googleapis.comand*.googleusercontent.comwithout TLS inspection. - Lower the Run … at a time number on the Tasks page so fewer copies share the connection.
Was this article helpful?
Updated 2026-11-21