fix(config): stop routing prod uploads to v.monophonic.digital - #1035
Merged
Conversation
Resumable (tus) uploads cannot complete through the Cloudflare zone in front of v.monophonic.digital: HEAD /files/:id reaches tusd as GET and returns 405, so a client can never learn its offset to resume after an interrupted PATCH, and PATCH requests lasting longer than ~100s are cut off with a 524. /uploads/:id responses are also served from cache. Roughly half of album uploads have been landing there by rendezvous and stalling at a few percent before failing. Route prod uploads to creatornode.audius.co only until the zone is fixed. The node stays in StoreAllNodes and the reward sender list, which do not depend on the upload path. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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
Removes
https://v.monophonic.digitalfromProdUploadNodes, leavingcreatornode.audius.coas the only upload target the API advertises in/health_check.Why
Album uploads have been stalling at a few percent and then failing for users whose SDK rendezvous picked monophonic. Over the last 24h, 100 of the 112 audio uploads stuck in
newwith no CID were created on monophonic, and the same WAV files that failed there repeatedly succeeded first try on creatornode.Probing both nodes with real tus uploads shows the difference is the Cloudflare zone in front of monophonic, not the node software (both run the same build):
HEAD /files/:idarrives at tusd asGETand returns 405, so tus-js-client can never read its offset to resume after an interruption. Progress freezes where the first attempt stopped, then the upload fails once retries are exhausted.PATCHwhose body takes longer than ~100s is cut off with a 524. Album tracks upload concurrently, so a 150–200MB album on a home connection routinely exceeds that per request./uploads/:idis served from cache (cf-cache-status: HITon the second poll).creatornode passes all three checks.
The node remains in
StoreAllNodesand the artist coin reward sender list, which do not depend on the upload path. It can be re-added once the zone bypasses cache on/files/*and/uploads/*and stops rewriting HEAD.Test plan
go build ./...andgo vet ./config/pass.curl https://api.audius.co/health_check | jq .data.network.content_nodesshould list only creatornode.🤖 Generated with Claude Code