Hi @gaunt laurel. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#Fetch failed
vital stormBOT
The "Fetch failed" error when trying to connect to your Convex deployment (e.g., https://uncommon-dodo-478.convex.cloud) can be caused by several factors, based on the knowledge sources:
-
Node.js Version: Convex local development and CLI tools currently require Node.js 18. Users have reported that using Node 20, 22, or 23 (especially on Linux) can cause fetch failures, while Node 18 works reliably. Try downgrading to Node 18 and see if the issue resolves Discord thread: ✖ TypeError: fetch failed Discord thread: Convex Local Dev Deployments failing.
-
Network Issues: This error can also be due to local network problems, VPNs, or firewalls blocking access to Convex domains. Try switching networks, disabling VPNs, or testing on a different device to rule out connectivity issues Discord thread: Unable to run schema Validation.
-
Convex Service Outage: Occasionally, Convex may experience temporary service interruptions. These are rare and usually resolved quickly. If the issue persists across multiple networks and Node versions, check the Convex Discord Community for outage reports Discord thread: Unable to connect to convex.
Recommended Steps:
- Ensure you are using Node.js 18.
- Try a different network or disable VPN/firewall.
- Wait a few minutes and try again in case of a temporary service issue.
- If the problem persists, reach out on the Convex Discord Community or email [email protected].
If you need to run local deployments, Node 18 is required for now. The Convex team is aware of this limitation and is working on improvements Discord thread: Convex Local Dev Deployments failing.