PDS account visible on regional 1.1 + 3rd party relays but not in AppView/bsky api

[BrettM86]

My did:web account is correctly synced to regional 1.1 relays (relay1.us-east/west.bsky.network) and third party relays but bsky.network returns 404, causing the AppView to show "Profile not found".

Account: did:web:coves.social
PDS: https://pds.coves.me (previously coves.me, I tried changing hostname to work around potential relay race condition per discussion #4258)

Current State

Endpoint	Method	Status	Updated understanding
pds.coves.me	getRepo	✅ 200
pds.coves.me	describeRepo	✅ handleIsCorrect: true
relay1.us-east.bsky.network	getRepoStatus	✅ active: true, rev: 3m6gtetzx3s2a
relay1.us-west.bsky.network	getHostStatus	✅ active, seq: 28
bsky.network	getRepoStatus	❌ Not Found	--- NOT EXPECTED
bsky.network	getRepo	❌ 404	--- NOT EXPECTED
api.bsky.app	getProfile	❌ Profile not found

1. Originally hosted at coves.me - relays showed describeRepo but AppView never indexed
2. Changed PDS hostname to pds.coves.me per Self-hosted PDS not being picked up by relay #4258 suggestion about relay race conditions
3. Updated .well-known/did.json to point to new hostname
4. Requested crawl via requestCrawl on all relays - accepted
5. 1.1 bsky + 3rd party relays now show account as active with events synced (seq: 28)
6. bsky.network still returns 404

Running Relay Hound

Oddly enough different from discussion #4258 my relayhound is working properly?

Hosts: [wss://bsky.network wss://relay1.us-west.bsky.network wss://relay1.us-east.bsky.network wss://atproto.africa wss://coves.me wss://relay.upcloud.world wss://relay.fire.hose.cam]
Target: did:web:coves.social
Timeout: 1m0s

✅  wss://bsky.network
✅  wss://relay1.us-west.bsky.network
✅  wss://relay1.us-east.bsky.network
✅  wss://atproto.africa
✅  wss://coves.me
✅  wss://relay.fire.hose.cam

Curl results for the DID, it's also fine if I curl the PDS directly

# Regional relay has the account ✅
curl -s 'https://relay1.us-east.bsky.network/xrpc/com.atproto.sync.getRepoStatus?did=did:web:coves.social'
# {"active":true,"did":"did:web:coves.social","rev":"3m6gtetzx3s2a"}


# AppView can't find profile ❌
curl -s 'https://api.bsky.app/xrpc/app.bsky.actor.getProfile?actor=did:web:coves.social'
# {"error":"InvalidRequest","message":"Profile not found"}

Is there any recommendations on where to go from here? Starting a fresh PDS is definitely a last resort as the DID:WEB migration will likely be a headache of it's own.

[BrettM86]

Digging into this more... I've confirmed that bsky.network is receiving my events - I believe the issue is that the AppView isn't processing them some. Using goat on relay1 and bsky.network fanout, both are accurately indexing likes / profile updates etc.. this makes sense since Relayhound also works. Willing to bet it's not necessarily a relay specific issue.

bretton@pop-os:~$ goat firehose --relay-host wss://relay1.us-west.bsky.network 2>&1 | grep "coves.social"
{"payload":{"blobs":null,"commit":{"$link":"bafyreicgctb6b63fzmb4f34v3sfisp5xtxwdfmh4pyy3vzx5mlgzzi7ny4"},"ops":[{"action":"create","cid":{"$link":"bafyreibnsdpg5vknbpiwgqdqcfo2yjh7bj5ckuit5ppmuuw2a6gxx4xqfm"},"path":"app.bsky.feed.like/3m6ijeogt622a"}],"prevData":{"$link":"bafyreidmq7emnyw5f7dzyppjjji5rioqhqxemipbdpfby7btgq7hlkklaq"},"rebase":false,"repo":"did:web:coves.social","rev":"3m6ijeoheqk2a","seq":6933385625,"since":"3m6ijdteij22a","time":"2025-11-25T23:42:30.381Z","tooBig":false},"type":"commit"}
{"payload":{"blobs":null,"commit":{"$link":"bafyreideysgfhu3vn5fvfrqs7bv6br7caudxsr4szziqjrmfrfhd5zqp5e"},"ops":[{"action":"delete","cid":null,"path":"app.bsky.feed.like/3m6ijeogt622a","prev":{"$link":"bafyreibnsdpg5vknbpiwgqdqcfo2yjh7bj5ckuit5ppmuuw2a6gxx4xqfm"}}],"prevData":{"$link":"bafyreib7zutomh6qnkv7ugcmbd36qlxymcer7tbpdmbbozupx4ugaqfbdq"},"rebase":false,"repo":"did:web:coves.social","rev":"3m6ijepykxk2a","seq":6933386027,"since":"3m6ijeoheqk2a","time":"2025-11-25T23:42:31.992Z","tooBig":false},"type":"commit"}
^C
bretton@pop-os:~$ goat firehose --relay-host wss://bsky.network 2>&1 | grep "coves.social"
{"payload":{"blobs":null,"commit":{"$link":"bafyreicueodhq47t3xrqkn6vcxurcpm6ffzt3ymdspg23d4wnifjpwavrm"},"ops":[{"action":"create","cid":{"$link":"bafyreidimzdebssievfyxpz5inmentayxeeb5pkq72i7y2lhibtxzq6jpa"},"path":"app.bsky.feed.like/3m6ijgfdovc2a"}],"rebase":false,"repo":"did:web:coves.social","rev":"3m6ijgfebh22a","seq":15650344546,"since":"3m6ijepykxk2a","time":"2025-11-25T23:43:28.236Z","tooBig":false},"type":"commit"}
{"payload":{"blobs":null,"commit":{"$link":"bafyreib5gc7pr73dktf27z5e2ontz2v3wbfxmme5ct6fa2klvnk3mkuplq"},"ops":[{"action":"delete","cid":null,"path":"app.bsky.feed.like/3m6ijgfdovc2a"}],"rebase":false,"repo":"did:web:coves.social","rev":"3m6ijgh3rss2a","seq":15650345266,"since":"3m6ijgfebh22a","time":"2025-11-25T23:43:30.274Z","tooBig":false},"type":"commit"}
^C
bretton@pop-os:~$ goat firehose --relay-host wss://bsky.network 2>&1 | grep -E "coves.social"
{"payload":{"blobs":null,"commit":{"$link":"bafyreiboqwbqf7nprcfuwxnuraodclqakoflgkzqn2bsmumo2qafeusgjm"},"ops":[{"action":"create","cid":{"$link":"bafyreidx4hpfyciyk7jxpbi6d4p5jy3tjbmdan54wpkwhev4uiupdq5jxu"},"path":"app.bsky.feed.like/3m6ijiouqqk2a"}],"rebase":false,"repo":"did:web:coves.social","rev":"3m6ijiovebk2a","seq":15650373978,"since":"3m6ijgh3rss2a","time":"2025-11-25T23:44:45.406Z","tooBig":false},"type":"commit"}
{"payload":{"blobs":null,"commit":{"$link":"bafyreigg5i5wmcyjfr76jpn5qbsgh4mrcbl4n2xafcjxzccqptpcxk7ug4"},"ops":[{"action":"delete","cid":null,"path":"app.bsky.feed.like/3m6ijiouqqk2a"}],"rebase":false,"repo":"did:web:coves.social","rev":"3m6ijiqdbys2a","seq":15650374751,"since":"3m6ijiovebk2a","time":"2025-11-25T23:44:47.445Z","tooBig":false},"type":"commit"}
{"payload":{"blobs":null,"commit":{"$link":"bafyreih6tutwgs626lv7c7qki5obnruhokshaiavrmhcrjvy4yz4pfoqvq"},"ops":[{"action":"update","cid":{"$link":"bafyreicefbspfl366rwqaxjez3isg6mdvgp7ovxp7cijmkkm44goljddgy"},"path":"app.bsky.actor.profile/self"}],"rebase":false,"repo":"did:web:coves.social","rev":"3m6ijj5eark2a","seq":15650379574,"since":"3m6ijiqdbys2a","time":"2025-11-25T23:45:00.492Z","tooBig":false},"type":"commit"}

The problem possibly seems to be somewhere with how the Appview indexes these events? Likes are processed in app fine, but the profile not found leads me to believe something is not processing profile updates with the DID?

The DID is also available and valid according to PDSLS, just not Bluesky.

Additional context, I was running into some issues with handle validation due to some CORS errors, I would say my invalid handle was cached but it's been resolved for 48+ hours and should update properly.

[BrettM86]

I think I've possibly identified the root problem here, the actor row for did:web:coves.social was never created in the AppView database and or is stuck in a misconfigured state. This happened because the initial identity event failed during DID resolution (likely due to my misconfigured did.json at account creation time), and the error was silently swallowed.

The flow here of what likely happened:

1. Account created on PDS when did.json was misconfigured
2. Identity event emitted → indexHandle() called with force=true
3. resolveAtprotoData("did:web:coves.social") failed (malformed DID doc)
4. Error caught by Firehose, logged, event skipped
5. Actor row never created or created in a misconfigured null state

Although identity events should fix this right? Pushed a few identity events and nothing successful.

Request
Could someone check AppView logs for errors related to did:web:coves.social? And or check the Appview DB to see if this record has been properly created. Right now my handle is basically useless for Bluesky and would like to market my atproto platform :)

Claude found the following troubleshooting if it's worth logging for the initial indexing bug:

Possible Appview Silent Error

When AppView processes firehose events, errors in indexHandle() are caught and logged but the event is skipped:

// packages/sync/src/firehose/index.ts:133-137
try {
  await this.opts.handleEvent(write)
} catch (err) {
  this.opts.onError(new FirehoseHandlerError(err, write))  // Only logs, continues
}

// packages/bsky/src/data-plane/server/subscription.ts:72
onError: (err) => log.error({ err }, 'error in subscription')

2. Actor Row Creation is Centralized The only way an actor row gets created is through indexHandle() which does an UPSERT:

// packages/bsky/src/data-plane/server/indexing/index.ts:159-165
await this.db.db
  .insertInto('actor')
  .values({ did, ...actorInfo })
  .onConflict((oc) => oc.column('did').doUpdateSet(actorInfo))

If resolveAtprotoData() throws (line 135), this UPSERT never executes.

4. Account Events Can't Fix It
   Account events call updateActorStatus() which is UPDATE-only:

// packages/bsky/src/data-plane/server/indexing/index.ts:264-278
await this.db.db
  .updateTable('actor')  // UPDATE, not INSERT!
  .set({ upstreamStatus })
  .where('did', '=', did)
  .execute()

If the actor row doesn't exist, this silently updates 0 rows.

---

Possible relay error?

Updating here another possibility:

bsky.network state for did:web:coves.social:
├─ getLatestCommit: 200 (rev: 3m6bgzka3mk2i) ← STALE metadata exists
├─ getRepoStatus: 404 "Not Found"
└─ getRepo: 500 "failed to read repo into buffer" ← Repo data missing

Regional relay (us-east) state:
└─ getRepoStatus: 200 (rev: 3md4ftuf7ck2x) ← CURRENT, working

[BrettM86]

@bnewbold Sorry for the ping here, but do you happen to know any way to get this account re-indexed properly by bluesky?