Skip to content

fix(readnovelfull): mark Novel Bin down and fail with an actionable error - #2551

Closed
RibatTRW wants to merge 2 commits into
lnreader:masterfrom
RibatTRW:fm/lnreader-novelbin-fetch-fix
Closed

RibatTRW wants to merge 2 commits into
lnreader:masterfrom
RibatTRW:fm/lnreader-novelbin-fetch-fix

Conversation

@RibatTRW

@RibatTRW RibatTRW commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Change

Closes #2549 ("Plugin fetching failed" — Novel Bin). One-file diff: the novelbin entry in plugins/multisrc/readnovelfull/sources.json is marked down per the repo's down-marker convention ("down": true + "downSince"), with versionIncrements 1 → 2 (generated plugin 2.2.2 → 2.2.3). An earlier revision also reworked template.ts to fail fast; that was dropped at review scope-narrowing, so template.ts is byte-identical to base and no runtime behavior ships — this records the outage, it does not restore it. Readers after a working catalogue should use the Novel Arrow plugin, already shipped here.

Diagnosis: novelbin.com no longer resolves — local resolver failure plus SERVFAIL/REFUSED (lame delegation) on Google and Cloudflare DoH — so every plugin request dies as a network error. The sibling ReadNovelFull source on the same template passes all four live checks, so the template is healthy; only novelbin's dead domain diverges. No surviving domain can restore it: novelbin.xyz is a different stack (identical 11,976-byte SPA shell on every route, zero list markup, HTTP 429 / error code: 1027 on chapter detail), .biz/.lat are parked pages, .co is a redirect lander, and .cc no longer resolves.

Verification

build:multisrc regenerates cleanly with the down marker and v2.2.3 carried through; build:compile exits 0; prettier clean; lint identical to base. check:plugin on NovelBin reports INCONCLUSIVE on the dead domain (honest, not forced); ReadNovelFull passes all four steps as the shared-template regression run (20 popular, 1 search, 3816-chapter novel, 13147-char chapter).

Caveat: Novel Bin novels still cannot load — the site is gone and nothing in this repository changes that. AI-authored change, no human review.

…rror

novelbin.com and novelbin.me no longer resolve: every authoritative resolver
(Google DoH, Cloudflare DoH, local) gets SERVFAIL from lame delegation - all
six Cloudflare nameservers for the zones REFUSE queries - so the Novel Bin
plugin died as an opaque 'fetch failed' for every user (issue lnreader#2549). The
site went dark in mid-2026 and no domain serving this CMS's markup remains;
verified candidates are parked pages or a JS SPA that the template cannot
parse, while sibling ReadNovelFull on the same template passes all four
live checks.

- flag the novelbin source down/downSince in sources.json, following the
  multisrc down convention from chore: Source Cleanup (lnreader#1977)
- add an optional downNote carrying the successor pointer
- make the readnovelfull template fail fast with the recorded reason (and
  note) from popularNovels/parseNovel/parseChapter/searchNovels instead of
  letting each call die as an unactionable network error; sources without
  the flag are untouched
- bump versionIncrements so installed copies update to 2.2.3

AI-authored change (pi coding agent). Not human-reviewed.

Closes lnreader#2549
…r only

Review scope narrowing: novelbin.xyz (the candidate successor) was verified
incompatible with this template (SPA shell, no server-rendered list/detail/
chapter markup, novel pages walled with HTTP 429), so the earlier template
fails-fast/downNote machinery is dropped and the change is now only the
established multisrc down marker plus the required version increment.

AI-authored change (pi coding agent). Not human-reviewed.
@RibatTRW
RibatTRW changed the base branch from main to master September 22, 2026 09:08
@RibatTRW

Copy link
Copy Markdown
Contributor Author

Superseded by #2793, which replaces the dead novelbin.com entry with a working novelbin.xyz plugin (same id), so marking Novel Bin as down is no longer needed.

@RibatTRW RibatTRW closed this Oct 27, 2026
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Oct 30, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Plugin fetching failed

1 participant