NoStatus .dot deploy verifies records and gateway, but dot.li shows app unreachable

[Devpen787]

Summary

I deployed a NoStatus .dot app on paseo-next-v2 with @parity/polkadot-app-deploy@0.11.0.

The deploy appears to complete correctly:

• DotNS registration succeeds.
• Root contenthash is verified on-chain.
• P2P retrieval passes during deploy.
• Root manifest text record is verified.
• app.<domain>.dot subdomain is registered.
• App subdomain contenthash is verified.
• App executable text record is verified.
• Gateway retrieval for the final root CID returns HTTP 200.

But the .dot.li host still renders:

This app can't be reached
Check if there is a typo in chopdotdemo28.dot.

Environment

Tool: @parity/polkadot-app-deploy@0.11.0
Environment: paseo-next-v2
Domain: chopdotdemo28.dot
Build: static Vite bundle
Deploy mode: --js-merkle
Session: no Polkadot app login session; CLI used pool fallback

Final CID

bafybeifgvj7o56dai5jmsc2wruy25ec5hiqsdisag26ri736sgsvhf76ay

Gateway URL:

https://paseo-bulletin-next-ipfs.polkadot.io/ipfs/bafybeifgvj7o56dai5jmsc2wruy25ec5hiqsdisag26ri736sgsvhf76ay/

Gateway result:

HTTP 200

Live URL:

https://chopdotdemo28.dot.li/?mode=savings_circle

Relevant deploy output

The corrected deploy completed and published manifest/app records:

DEPLOYMENT COMPLETE
CID: bafybeifgvj7o56dai5jmsc2wruy25ec5hiqsdisag26ri736sgsvhf76ay
Domain: chopdotdemo28.dot

Root manifest text record verified:

{
  "$v": 1,
  "displayName": "ChopDot",
  "description": "Group money coordination for expenses, savings circles, emergency pots, and community funds.",
  "icon": {
    "cid": "bafk2bzacecmdaf5z2o2runzlorl2l2wct3b6ottrlirorwa36x56aumb63ohi",
    "format": "png"
  }
}

Executable text record verified:

{
  "$v": 1,
  "kind": "app",
  "appVersion": [0, 1, 0]
}

Verification result

I ran a Playwright-based check after the deploy:

{
  "verified_at": "2026-06-28T20:20:49.389Z",
  "domain": "chopdotdemo28.dot",
  "root_cid": "bafybeifgvj7o56dai5jmsc2wruy25ec5hiqsdisag26ri736sgsvhf76ay",
  "live_url": "https://chopdotdemo28.dot.li/?mode=savings_circle",
  "gateway": {
    "pass": true,
    "status": 200,
    "url": "https://paseo-bulletin-next-ipfs.polkadot.io/ipfs/bafybeifgvj7o56dai5jmsc2wruy25ec5hiqsdisag26ri736sgsvhf76ay/"
  },
  "live": {
    "pass": false,
    "stdout": "{\"banner\":0,\"dotLab\":0,\"unreachable\":1,\"reaching\":0,\"title\":\"Polkadot - The decentralized web, in your browser\"}\n",
    "stderr": "",
    "status": 1
  },
  "overall_pass": false
}

Curl check

https://chopdotdemo28.dot.li/?mode=savings_circle returns the dot.li host HTML with title:

Polkadot - The decentralized web, in your browser

But the app itself does not render.

Gateway HEAD for the root CID returns:

HTTP/2 200
content-type: application/octet-stream
content-length: 10817265
etag: "bafybeifgvj7o56dai5jmsc2wruy25ec5hiqsdisag26ri736sgsvhf76ay"
x-ipfs-path: /ipfs/bafybeifgvj7o56dai5jmsc2wruy25ec5hiqsdisag26ri736sgsvhf76ay/

Question

Is there another required record, resolver shape, propagation step, or expected app packaging shape for .dot.li to load this app?

From the deploy CLI output, the records seem to be present and verified, and the final root CID is retrievable from the gateway. The remaining failure appears to be between dot.li resolution/host loading and the published app content.

[Cyr06130]

Hi @Devpen787,

Currently dot.li points to a deprecated network (Summit), but you can use paseo.li instead to target the paseo-next-v2 network:

https://chopdotdemo28.paseo.li

Thanks!