Description

When attempting to deploy a PartyKit server to the managed platform using npx partykit deploy, the deployment consistently fails with a 504 Gateway Timeout error before the build process even starts.

Environment

• PartyKit version: 0.0.115
• Node.js version: v22.16.0
• OS: macOS 15.6.1
• Date of issue: 2025-10-09

Configuration Files

partykit.json:

{
  "name": "vibe-in-the-dark",
  "main": "partykit/server.ts",
  "compatibilityDate": "2024-10-09"
}

Server structure:

Server file: partykit/server.ts
Implements Party.Server with basic WebSocket relay functionality
Uses TypeScript

Steps to Reproduce

Run npx partykit whoami - confirms logged in successfully
Run npx partykit deploy
Error occurs immediately during "Deploying..." phase

Expected Behavior

Deployment should complete successfully and provide a deployed URL on the partykit.dev domain.

Actual Behavior

Deployment fails with:

🎈 PartyKit v0.0.115
---------------------
Loading environment variables from .env
Deploying...
Error: 504 Gateway Timeout
    at fetchResult (file:///.../node_modules/partykit/dist/bin.mjs:84998:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async deploy (file:///.../node_modules/partykit/dist/bin.mjs:95750:21)

Additional Context

Local development server works perfectly with npx partykit dev
Authentication is successful (logged in as verified user)
Issue appears to be with the deployment API endpoint timing out
api.partykit.io hostname does not resolve (DNS lookup fails)
Cloudflare Status shows no current Workers-related incidents
Attempted deployment with --with-env flag - same error
Configuration has been validated against official examples

Workaround Attempts

✅ Verified compatibility date is valid (set to past date)
✅ Confirmed authentication works
✅ Validated server code compiles locally
❌ Cannot deploy to managed PartyKit platform
⚠️ Deploying with wrangler deploy (cloud-prem) works but lacks proper PartyKit routing infrastructure

Impact

Unable to deploy to production on PartyKit's managed platform. This appears to be a platform/infrastructure issue rather than a project configuration issue.