convex deploy fails on 1.29.2/1.29.3 with 404 on /api/deploy2/evaluate_push (self-hosted backend)

Not specified by the original author.

TL;DR

The fix was backend-side, so updating the CLI alone (1.29.3) did not help. What actually fixes it (verified in the thread): Update your self-hosted backend , Convex shipped a new backend release that resolves this; both reporters confirmed deploys succeed against the updated backend.

Steps

1. With convex 1.29.2 (and 1.29.3), convex deploy against a self-hosted backend fails with Error: Unable to start push to YOUR_THE_HOST loopback address:3210 / Error fetching POST YOUR_THE_HOST loopback address:3210/api/deploy2/evaluate_push 404 Not Found. The identical command works with 1.29.1.
2. What actually fixes it (verified in the thread):
3. Update your self-hosted backend , Convex shipped a new backend release that resolves this; both reporters confirmed deploys succeed against the updated backend. The fix was backend-side, so updating the CLI alone (1.29.3) did not help. Immediate workaround: pin convex to 1.29.1. Source: https://github.com/get-convex/convex-js/issues/105

When to use

You are seeing this: The situation: With convex 1.29.2 (and 1.29.3), convex deploy against a self-hosted backend fails with Error: Unable to start push to YOURTHEHOST loopback address:3210 / Error fetching POST YOURTHEHOST loopback address:3210/api/deploy2/evaluate\push 404 Not... Use this skill when you run into "convex deploy fails on 1.29.2/1.29.3 with 404 on /api/deploy2/evaluatepush (self-hosted backend)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: convex 1.29.2, 1.29.3, 1.29.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• YOURTHEHOST
• https://github.com/get-convex/convex-js/issues/105

Someone asked: With convex 1.29.2 (and 1.29.3), convex deploy against a self-hosted backend fails with Error: Unable to start push to YOUR_THE_HOST loopback address:3210 / Error fetching POST YOUR_THE_HOST loopback address:3210/api/deploy2/evaluate_push 404 Not Found. The identical command works with 1.29.1. The verified answer: Update your self-hosted backend , Convex shipped a new backend release that resolves this; both reporters confirmed deploys succeed against the updated backend. The fix was backend-side, so updating the CLI alone (1.29.3) did not help. Immediate workaround: pin convex to 1.29.1. Source: https://github.com/get-convex/convex-js/issues/105 Full thread: https://vectle.com/threads/thr_16noRGFsvTP9DSx3DQvsAQ

Not specified by the original author.

TL;DR

If convex deploy fails on Node 20+ with fetch failed and retry loops while older Node versions work, upgrade the convex npm package to 1.25.2 or later, which works around the Node network-family autoselection race.

Steps

1. If convex deploy fails on Node 20+ with fetch failed and retry loops while older Node versions work, upgrade the convex npm package to 1.25.2 or later, which works around the Node network-family autoselection race. On versions before that, run deploys with NODE_OPTIONS=--no-network-family-autoselection. In CI, pin both the Node major version and the convex package version together so a base-image bump cannot silently reintroduce the failure.

Expected: The fix shipped in convex@1.25.2, and the reporter confirmed it resolved the deploy on Node 22 and in GitHub Actions.

When to use

You are seeing this: In CI, pin both the Node major version and the convex package version together so a base-image bump cannot silently reintroduce the failure. Use this skill when you run into "Convex deploy fails on Node 20+ Linux: upgrade convex past 1.25.2".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 1.25.2. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: GitHub issue get-convex/convex-js#52 (closed, 13 comments): convex deploy failed on Linux with Node 20+ with fetch failed and repeated request retries during schema validation, while Node 18/19 worked. The maintainer traced it to a Node.js 20 regression in network family autoselection (Happy Eyeballs): if the connection took longer than about 250ms it was dropped. The fix shipped in convex@1.25.2, and the reporter confirmed it resolved the deploy on Node 22 and in GitHub Actions. Immediate workaround on affected versions: NODE_OPTIONS=--no-network-family-autoselection npx convex deploy.

Verified resolution: If convex deploy fails on Node 20+ with fetch failed and retry loops while older Node versions work, upgrade the convex npm package to 1.25.2 or later, which works around the Node network-family autoselection race. On versions before that, run deploys with NODE_OPTIONS=--no-network-family-autoselection. In CI, pin both the Node major version and the convex package version together so a base-image bump cannot silently reintroduce the failure.

Source URL: https://github.com/get-convex/convex-js/issues/52

Not specified by the original author.

TL;DR

If a Convex preview deploy key minted through an OAuth app 401s at claimpreviewdeployment, this was a known server-side validation gap that Convex fixed in July 2026: the OAuth token pass-through key is now accepted.

Steps

1. If a Convex preview deploy key minted through an OAuth app 401s at claimpreviewdeployment, this was a known server-side validation gap that Convex fixed in July 2026: the OAuth token pass-through key is now accepted. Retry against current Convex; if it still fails, check that the credential carries the preview prefix the endpoint expects, and fall back to minting the key with a personal access token, which always minted a real fresh secret.

Expected: The maintainer confirmed the pass-through behavior and shipped a server-side fix so claimpreviewdeployment accepts the OAuth-backed credential; the reporter tested and confirmed it works.

When to use

You are seeing this: Minting the same key with a personal access token worked fine, which made the OAuth path look broken. Use this skill when you run into "Convex OAuth-minted preview deploy keys 401: server-side fix shipped".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: GitHub issue get-convex/convex-js#172 (closed, 5 comments): when an OAuth application token was used to mint a preview deploy key via the Management API, the endpoint did not mint a fresh key, it returned the OAuth access token itself with only the prefix swapped, and claimpreviewdeployment then rejected it with 401 Invalid Convex preview deploy key. Minting the same key with a personal access token worked fine, which made the OAuth path look broken. The maintainer confirmed the pass-through behavior and shipped a server-side fix so claimpreviewdeployment accepts the OAuth-backed credential; the reporter tested and confirmed it works.

Verified resolution: If a Convex preview deploy key minted through an OAuth app 401s at claimpreviewdeployment, this was a known server-side validation gap that Convex fixed in July 2026: the OAuth token pass-through key is now accepted. Retry against current Convex; if it still fails, check that the credential carries the preview prefix the endpoint expects, and fall back to minting the key with a personal access token, which always minted a real fresh secret.

Source URL: https://github.com/get-convex/convex-js/issues/172