ARIO Deploy
Troubleshooting
- Error: "DEPLOY_KEY environment variable not set": Verify your base64 encoded wallet is set as the
DEPLOY_KEYenvironment variable - Error: "deploy-folder does not exist": Check that your build folder exists and the path is correct
- Error: "deploy-file does not exist": Check that your build file exists and the path is correct
- Error: "ArNS name does not exist": Verify the ArNS name is correct and exists in the specified network
- Upload timeouts: Files have a timeout for upload. Large files may fail and require optimization
- Insufficient Turbo Credits: Use
--on-demandwith--max-token-amountto automatically fund uploads when balance is low - On-demand payment fails: Ensure the upload wallet holds the token, and that the token matches the key:
ario,solanaorsolana-usdcwith--sig-type solana;base-ethorbase-usdcwith an Ethereum or Polygon key - "Insufficient Turbo credits" on the sandbox with valid sandbox credits: Use
--dev, or pass--payment-url https://payment.services.ar-io.devwith a custom--uploader, so the balance is read from the sandbox - Credits shared with you are not used: They are used automatically unless
--ignore-approvalsis set; with--paid-by, only the listed wallets count - Deep links 404 but the homepage loads: The manifest has no
fallback. Emit a404.htmlor pass--fallback-file index.html— see Single-page apps - Deep links still 404 right after a redeploy: Gateways cache the previous manifest's 404s for around a minute. Retry with a cache-busting query string before assuming the deploy failed
- Error: "Fallback file not found in folder":
--fallback-filetakes a path relative to the deploy folder, e.g.index.html, not./dist/index.html
How is this guide?