Repository navigation
fix(platform): make fresh self-hosted installs complete - #353
Merged
Merged
Conversation
A live install into a new Cloudflare account failed at four points: - Hyperdrive rejected verify-ca/verify-full URLs because those modes need an uploaded CA id that a connection URL cannot carry. Void-created Hyperdrives now use require (TLS with public CA validation) while Void's own connection keeps full verification. The URL is checked before the database claim, and a private sslrootcert is rejected there with guidance to use a separately managed Hyperdrive. - The conditional Worker create proxy blocked the asset upload session and uploads that precede the guarded create for Workers with assets. - node-postgres read sslrootcert=system as a file path. - The enabling pass reused the unchanged tail Worker version without a staged checkpoint, so every fresh install failed the pre-traffic cutover check. The enabling pass now always uploads a new version. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Uninstall retains the platform Workers but still deleted the Queues they bind, which Cloudflare refuses, so every uninstall of a deployed installation failed after platform traffic was already disabled. Uninstall now keeps the Queues while one of the installation's Workers exists, and a rerun finishes an uninstall that stopped this way. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Cloudflare refuses to delete a Worker that consumes a Queue, a Queue or dispatch namespace that a Worker still binds. List the retained resources in an order that succeeds. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Brooooooklyn
force-pushed
the
fix/platform-fresh-install
branch
from
October 1, 2026 04:44
85fb780 to
46cbef5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A live self-hosted install into a new Cloudflare account (Workers for Platforms, adopted zone, PlanetScale Postgres) failed at four points. All four are on
main.Invalid Hyperdrive config: mtls: (ca_certificate_id: cannot be blank when 'sslmode' is 'verify-full')sslmodewas forwarded to Hyperdrive. Hyperdrive's verify modes need an uploaded CA id, which a URL cannot carry. The DB was already claimed, so resume could not recover.require(TLS, public CA validation; the same aswrangler hyperdrive create --connection-string). Void's own connection still verifies withverify-full. The URL is checked before the claim. A privatesslrootcertpath is rejected before the claim, with guidance to use a separately managed Hyperdrive.attempted unexpected mutation POST .../assets-upload-session while conditionally creating new WorkerIf-None-Match: *create, but the uploader starts the asset session and uploads assets before the script PUT.ENOENT: no such file or directory, open 'system'sslrootcertas a path; libpq'ssystemmeans "system trust store".platformDatabaseClientUrlmapssslrootcert=systemtoverify-fullwith Node's default CAs.Worker cutover generation 2 is missing a complete immutable-version checkpointThe live install finished after these fixes (resume from the failed state, no manual Cloudflare edits).
Decisions
verify-ca/verify-full→ Hyperdriverequireinstead of rejecting those URLs: rejecting would make every PlanetScale/Neon URL fail as pasted. Operators who need CA pinning can adopt a separately managed Hyperdrive; Void never changes its TLS settings.Not in this PR (already on
main)sslmode(?sslmode=require&sslmode=disable) is read first-wins by the Hyperdrive parser and last-wins by node-postgres.platform/packages/apihas its own copy of the Hyperdrive URL parser with defect A (project database connect). Mapping there can reset a hand-configured CA mode on update, so it needs a product decision.Test plan
sslrootcert=system, the real uploader request sequence through the proxy, and a realinstallPlatformrun for a fresh install, a resume after a blocked first create, and a retry after a failed enabling passvp test runplatform unit tests: 42 files, 660 tests passvp run --filter ./packages/void typecheck🤖 Generated with Claude Code