Deployment Troubleshooting

Each repository has one active deployment provider. Check the active provider first, then use that provider's dashboard for logs and detailed status.

Provider Selection

If Vercel and Cloudflare Workers are both connected and the repository has not been deployed yet, choose a provider explicitly. Switching providers is also explicit.

Token Or Permission Errors

Reconnect the provider with a fresh token. Vercel tokens must belong to the account or team that owns the project. Cloudflare tokens need Account Settings read, Workers Scripts edit, and Workers KV Storage edit access.

GitHub Access Errors

Provider API tokens let PhantomWP call provider APIs. Cloudflare Workers deploys also require GitHub Actions to be enabled for the repository.

Build Failures

Open the provider dashboard and inspect the failed build logs. The generated Astro project expects:

• Install command: npm install
• Build command: npm run build
• Cloudflare Workers deploy command: npx wrangler deploy

Git Push Rejected After Cloudflare Setup

Cloudflare deployment writes wrangler.jsonc, the Astro adapter config, package dependencies, and a GitHub Actions workflow directly to GitHub. Pull from GitHub before pushing local changes if your editor was open before the deployment setup commit.

Environment Variables

WordPress and WooCommerce settings sync environment variables to the active provider. After changing env vars, redeploy the site so the static build uses the new values.

WooCommerce sync includes WordPress, WooCommerce, Stripe, PayPal, BACS, Turnstile, and public store currency keys.

Domains

Use the DNS records shown in the domain panel. Vercel may show A, CNAME, or nameserver options. For Cloudflare Workers, add a Worker custom domain or route in the Cloudflare dashboard.