Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
6 KiB
| name | description | metadata | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| publish-deeplink-404-2026-11-05 | Obsidian Publish mirror /zapret/<path> redirected to /404 on 2026-11-05 although site, files and subscription were fine; how it was diagnosed |
|
On 2026-11-05 every direct request to publish.obsidian.md/zapret/<path> (even nonexistent paths) answered 301 → /404, while bare /zapret loaded the SPA and in-app navigation worked. Other Publish sites (/hub/...) returned 200 for deep links.
Checked and healthy: publish:site, publish:list total (1042), the server index at publish-01.obsidian.md/cache/<siteId>, apiOptions(), account API publish/list and api/site (one site, id matches .obsidian/publish.json), and the owner's screenshot of the Publish plan (Active, renews 2027-10-07). Re-binding the slug via publish.obsidian.md/api/slug did nothing. The owner concluded it is a bug on Obsidian's side.
Why: a 404 on the mirror looks like the subscription-expiry failure in the vault-note skill, but here the site, files and plan were all intact, so recreating the site would have been wrong.
How to apply: if the mirror 404s, first compare deep link vs bare /zapret, check publish:site and the account API; recreate the site only when publish/list returns no sites. Do not run publish:add changed blindly: the working tree holds untracked gptimage/ and drafts. Task file: ~/.agent-todo/Privacy/2026-11-05-publish-mirror-deeplink-404.md. See vault-push-and-shared-dirs.
Update 2026-11-19: still 404 after 13 days; support ticket #155692 got only the auto-reply, and support's first answer was "check your local settings". curl from this host (Frankfurt exit), the US2-7 server (own IP, no VPN) and a Russian datacenter front all get the same 301 -> /404 (header variants, UA, language, Referer change nothing), and the same site under another slug (zapretwiki, tested for ~30 s, then reverted) answered 200 on deep links, so the fault follows the slug zapret. At 12:45 EST the owner's own browser opened /zapret/Zapret/home fine, but a private window gave the 404 (the normal browser was serving a cached copy), and a 25-minute watch showed no change, so the 404 is real for every fresh visitor: from the owner's own direct Russian connection too. Lesson: when checking the mirror in a browser, use a private window, because a tab that visited the page before can show it from cache. The four files that failed publish:add with Failed to fetch published fine on a later retry (transient, not an attachment). Deploy flow since 2026-11-07: push to Forgejo, then the wiki container's wiki-autopull (every minute) and wiki-rebuild.path rebuild the wiki; the Publish CLI (headless Obsidian) still runs on this host.
Update 2026-11-19 (later): the Publish setup changed on 2026-11-15, before the notes above were re-checked. On that day another session signed the headless Obsidian into a second account that the owner sent (the first account's login state is kept in localStorage obsidian-account.bak-20261115), created a NEW site there, bound the slug zapret to it, ran the plugin setup (.obsidian/publish.json siteId changed) and republished everything. Credentials are not stored here. Result: the slug zapret now belongs to the second account's site, and the deep links STILL answer 301 -> /404 for fresh visitors. So a new account, a new site and a fresh subscription state did not fix it, which points at the slug name zapret (or the content), not the first account or its site. The support ticket #155692 was filed for the first account and its old site, so any follow-up must mention that the slug was moved to a new site on a new account on 2026-11-15 and still fails. The account limit is one site: a second site needs a purchase or deleting the existing one.
Resolution 2026-11-19: the owner chose to move the slug. On the current site (second account) the slug was changed from zapret to zapretwiki through publish.obsidian.md/api/slug (same call as in the vault-note recovery steps). Direct deep links then work: in a fresh browser /zapretwiki/Zapret/download stays on its URL and the app loads with all navigation links under /zapretwiki/; the old /zapret/... addresses still 404 and the slug zapret is now free. The mirror URL in AGENTS.md and the vault-note skill is updated to https://publish.obsidian.md/zapretwiki. Support ticket #155692 (first account) no longer needs a nudge unless the owner wants the cause explained; the new slug must not go back to zapret.
2026-11-19, after the slug move: the owner asked to update the clone and publish the missing articles. The clone was fast-forwarded (other sessions' uncommitted edits in it were protected with a backup and a path-limited stash). Every tracked publishable note was already on the mirror; notes with publish: false (the Linux GUI draft, a scratch note) stay off on purpose. The gitignored notes that the old mirror had but the 2026-11-15 setup skipped (about 20, covering privacy topics, payments, mail, scams) were scanned for secrets and published on the owner's instruction; one payment note with an internal host address in a config example was held back and stays off the mirror (the owner closed the item without asking to publish it). Lesson: Publish uploads from the clone's disk, so bring the clone up to date before publish:add, and compare publish:list with git ls-files instead of trusting publish:status alone, because publish: false notes never show up there.
Security lesson 2026-11-19: never echo an API response before redacting by VALUE; a replace of the word token left the session token printed in the log. A session token minted by a test sign-in can be revoked with POST https://api.obsidian.md/user/signout {token}; compare sha256 prefixes first to make sure it is not the app's own token. Nothing in the vault, memory or Telegram channel is known to link the old mirror address; the vpnbot test only lists it as obsolete.