-
Morphit v1.15.2 Stable
released this
2026-09-02 00:59:05 +00:00 | 108 commits to main since this releaseMorphit v1.15.2
Installer robustness + quieter output. Every failure is now diagnosable in one shot instead of a wall of raw Ansible.
Added / Changed
A failed install now tells you exactly what broke and how to fix it. The whole Ansible run is captured to a log, and if it fails the wizard prints a plain-English summary — the failed step, what Ansible said, and a likely fix — instead of a generic "exit code N, check the messages above." Recognised failures (Postgres unreachable, apt lock held, Docker permission, missing sudo, disk full, old ansible-core, DNS/network, port in use) come with the specific remedy. An unrecognised failure points you at the full log and support — so even a brand-new edge case is a captured, actionable artifact, not a dead end.
Quieter, calmer install output.
- npm's "New major version available!" and funding banners are suppressed during install/upgrade — we vendor a pinned npm, so those were noise you couldn't act on.
- The "stopping leftover process(es)" step during an upgrade is now a single calm line ("Superseding N stale worker process(es) from the previous version…"). It only prints the detail — PIDs and a manual-kill command — in the rare case it can't stop them, which is the only case worth your attention.
Notes
- Builds on the v1.15.x installer hardening: the ansible-core ≥ 2.15 pre-check, the port/subnet/localhost pre-checks, and the automatic
localhost→127.0.0.1database-host fix all remain. - No database migration beyond v1.15.0's additive
orders.lang(schema v56). Upgrade in place; everything from v1.15.1 is included.
Robustness: the installer never dead-ends now
A full end-to-end audit of the install path closed every place a failure could still surface as a raw stack trace or a cryptic one-liner:
- A global error backstop. Any error anywhere in the wizard — a system call, a prompt, a file write, an apt/collections step, even a bug in our own code — is now turned into a plain-English message that names the likely cause, gives the fix, points to the run log, and (only when we don't recognise it) hands you support (
agorise@pm.me/@agorise:matrix.org). Node system errors (permission, port-in-use, disk-full, missing command, DNS/network) are mapped to their fixes. - Process-level crash handlers catch any async rejection that escapes the normal flow, so the worst case is still a clean sanitized line — never a V8 stack dump.
- A non-interactive-terminal guard: running the wizard through a pipe or a non-interactive SSH command now fails fast with "run it in a real terminal" instead of looping forever on empty input.
- Censored/limited networks: a blocked Ansible Galaxy fetch (a missing-collection failure) now maps to a clear "the release bundles these — just re-run" message.
- Dependency hygiene: patched a build-time
browserslistadvisory (dev/build only, never in the shipped bundle).
More pre-flight checks (catch the environment, not just the code)
A second audit — this time of the server's real-world state, not the wizard's control flow — added up-front checks for the conditions that silently break a fresh install:
- PostgreSQL version gate. Morphit needs PostgreSQL 15+, but Ubuntu 22.04's
apt install postgresqlis 14 — the same distro-too-old trap as the Ansible one. The wizard now flags it before the migrations run, with the PGDG-repo upgrade path. - DNS-points-here. Right after you enter your domain, the wizard resolves it and checks it points at this server — the single most common reason a self-hosted HTTPS install fails (the cert can't be issued if DNS isn't pointed/propagated). It distinguishes not-resolving-yet, behind-NAT (with port-forward guidance), and a plain mismatch, and reminds you that a cloud firewall must also allow inbound 80 + 443. Non-blocking — you can point DNS while the install runs.
- Locale. Warns on a non-UTF-8 locale (
LANG=C/POSIX on minimal images), which would otherwise make Postgres default a new database to SQL_ASCII and garble multilingual + RTL content.
Hand-holding: a grandma can hit Enter all the way through
A usability pass so the install is smooth for any experience level, on any topology (Tor-only or clearnet, home box or VPS):
- Press Enter = the recommended answer, everywhere. An up-front tip says so, every yes/no question has a safe default, and the offered auto-fixes (add swap, install Docker, add the localhost hosts entry) now default to yes and say "recommended — just press Enter", so an operator who doesn't understand a question can keep pressing Enter and end up with a working node. The only things they must type are their own domain, account names, and key.
- The braille spinner now runs during every silent step — the system checks, the on-chain account lookup, and the DNS check — so a slow network moment never looks frozen. (It degrades to a one-line label when there's no terminal to animate.)
- Tor-only nodes skip the domain + DNS + certificate questions entirely; home boxes behind NAT get port-forwarding guidance from the DNS check; VPS boxes get the public-IP comparison. Each topology only sees the questions that apply to it.
- A no-output watchdog on the long install run. The setup step streams Ansible's progress live, and if the run goes quiet for a few minutes (a big download, a first database migration, or issuing the HTTPS certificate) it prints a calm reassurance with the recommendation — just wait, it will continue, and a re-run is always safe. A slow step never looks like a dead hang, and the operator never has to make a decision to keep going.
Downloads
-
Source code (ZIP)
2 downloads
-
Source code (TAR.GZ)
5 downloads
-
Morphit v1.15.1 Stable
released this
2026-09-01 08:16:59 +00:00 | 109 commits to main since this releaseMorphit v1.15.1
A fix release on top of v1.15.0: the release build is fixed, and the installer now catches an old-Ansible trap that was silently failing fresh installs. Includes all of v1.15.0 (the orderbook language feature + the v1.14.3 rollup).
Fixed
The release build no longer fails. v1.15.0's web bundle pulled the server-only
@morphit/operator-configmodule (with itsnode:fs/node:path/node:utilimports) into the browser build, which brokevite build. The web now derives its order-language codes from its ownSUPPORTED_LOCALES(a smoke keeps them in lockstep with the indexer's list), so nothing Node-only reaches the browser bundle.Old Ansible no longer fails a fresh install with a misleading error. Ubuntu 22.04's
apt install ansibleinstalls the EOL 2.10, which can't load the modern collections the playbook needs — and the old installer misreported that as "the installer found no machine to configure (0 hosts)." Two changes address it:- The setup wizard's system check now verifies ansible-core ≥ 2.15 up front. If it's too old (or the legacy pre-core 2.10), it fails the check with a clear explanation and offers a one-keystroke upgrade (via pipx), instead of letting the playbook fail cryptically later.
- Combined with v1.15.0's honest pre-flight (which already replaced the phantom "0 hosts" with the real Ansible error), an operator on old Ansible now gets told exactly what to do before anything runs.
The bundled
morphit-node-doctor.shdiagnostic was likewise updated to flag Ansible below the floor instead of marking it OK.Notes
- Upgrade in place; everything from v1.15.0 is included. No database migration beyond v1.15.0's additive
orders.lang(schema v56). - New operators on Ubuntu 22.04 should either install this version's wizard-guided setup (which will prompt to upgrade Ansible) or upgrade Ansible to core ≥ 2.15 first.
Downloads
-
Source code (ZIP)
2 downloads
-
Source code (TAR.GZ)
8 downloads
-
Morphit v1.15.0 Stable
released this
2026-09-01 05:37:53 +00:00 | 110 commits to main since this releaseMorphit v1.15.0
Headline: the orderbook now speaks your language. Plus a rollup of installer, UX, and hardening fixes.
Added
Per-order language + an orderbook language filter. A first visit to a busy instance no longer means scrolling past orders in languages you don't read. You tell Morphit which languages you understand, and the orderbook shows you orders written in those — nothing is translated, it's simply filtered.
- Tag your post's language. The order form (new and edit) has a "This post is in …" selector under "Listing expires," defaulted to your last-used post language → your primary preferred language → the language the site is set to. The choice rides along in the order's on-chain broadcast.
- Set your preferred languages. A new "Preferred languages" card in Settings lets you pick a primary (the default for your own posts) plus any other languages you read. It's saved to your on-chain profile, so it follows you across devices.
- Filter the orderbook. A searchable "Language" field (green removable pills, next to "Payment methods accepted") defaults to your preferred set — or, for a first-time visitor, just the language the site is in. Clear it to see every language.
- Nothing disappears. Orders posted before this release carry no language tag, and the filter never hides an untagged order — it only ever hides orders that declared a different language. The orderbook fills in over time as new orders carry a language.
Changed / Fixed (rollup)
morphit-opsmenu order restored — "Upgrade to the latest version" is option 2 again (a fast-sync entry had shifted it to 3), matching the release ceremony and muscle memory.- Account names accept dots — the setup wizard now allows Blurt-valid names like
my.relay(it had been stricter than the rest of the software). - No more "morphit" in name suggestions — the wizard, its fallbacks, and the docs now suggest brand-your-own names for relay/fees accounts and addresses instead of the reserved
morphitnamespace. - Single-domain nginx reality — the manual (non-BunkerWeb) install path installs one
web.confthat path-routes everything on one domain; Morphit deploys cleanly on a subdomain. - RPC endpoints card tells the truth on refresh — a node you shut down now shows "offline at the moment" instead of a stale latency (a failed probe is retried once; only a genuine double-miss reads as down).
- A self-healing installer — pre-flight checks for port/subnet/localhost conflicts, honest errors when Ansible can't run (instead of a misleading "0 hosts"), consented one-keystroke fixes for what's safely fixable, and a final report of everything fixed/skipped.
agorise@pm.me/@agorise:matrix.orgappear only as a genuine last resort. - fail2ban
ignoreipbaked into the standard hardening so an admin can't lock themselves out mid-release.
Notes
- No database migration is required beyond the automatic additive
orders.langcolumn (schema v56); no breaking on-chain changes — the new order/profile fields are optional and backward-compatible. - Everything from v1.14.2 and earlier is included.
Downloads
-
Source code (ZIP)
3 downloads
-
Source code (TAR.GZ)
9 downloads
-
Morphit v1.14.2 Stable
released this
2026-08-30 22:33:56 +00:00 | 112 commits to main since this releaseMorphit v1.14.2
A bugfix + polish release. No new features, no database migration, no on-chain changes. Includes everything from v1.14.1.
Fixed
The
morphit-opsmenu no longer moves "Upgrade" out from under your muscle memory. In v1.14.0/v1.14.1 the new fast-sync entry was inserted as menu item 2, shifting "Upgrade to the latest version" to item 3 — so selecting option 2 during a release landed on fast-sync (which then refused, because the indexer was running). The order is restored to Install (1) → Upgrade (2) → Fast-sync (3), matching the release ceremony's "choose option 2" and everyone's habit.The setup wizard now accepts dots in relay/fees account names. Blurt account names can contain dots (e.g.
my.relay), but the wizard's validation rejected them — it used a stricter rule than the rest of the software. It now matches Blurt's real account-name rules (lowercase letters, digits, dots, and dashes; each dot-separated part starting with a letter), so valid names likemy.relayare accepted while malformed ones are still caught with a clear message.Changed
Account and domain name suggestions no longer use "morphit". The setup wizard, its fallback examples, and the docs previously suggested names like
my-morphit-relay,morphit.eth, andmorphit.mydomain.orgfor an operator's own relay/fees accounts and addresses. Those are now neutral, brand-your-own examples — operators should name their accounts and domains after their own instance, not the reserved "morphit" namespace. (The canonical protocol accounts@morphit-fees/@morphit-relayare unchanged — those are factual references, not suggestions.)The manual (non-BunkerWeb) nginx instructions match the single-domain reality. The wizard's manual-nginx path used to hand operators three server blocks for a split relay/indexer/frontend subdomain layout that is no longer the design. It now installs a single
web.confthat serves the frontend and reverse-proxies/relay/,/v1/,/rss/, and/mcpon one domain — which also means Morphit deploys cleanly on a subdomain (e.g.trade.yourdomain.com), verified end to end. The optional split-service configs remain for advanced operators, with neutral example hostnames instead of stale ones.Notes
- Upgrade in place; everything from v1.14.1 and earlier is included.
Downloads
-
Source code (ZIP)
2 downloads
-
Source code (TAR.GZ)
4 downloads
-
Morphit v1.14.1 Stable
released this
2026-08-30 17:58:34 +00:00 | 113 commits to main since this releaseMorphit v1.14.1
A UX + hardening follow-up to v1.14.0. No new features, no database migration, no on-chain changes.
Changed
Fast-sync is now the default when setting up a new node. The guided install wizard (
morphit-ops install) now offers fast-sync as a default-yes step: a new operator just presses Enter to restore the newest signed federation snapshot and be live in minutes, and has to actively decline to fall back to a full replay. This is what v1.14.0's release notes described; in v1.14.0 fast-sync existed only as a separate command, so this closes that gap.Fixed
The stats-page RPC endpoints card now tells the truth on refresh. Clicking the card's refresh button (or reloading the page) fires a live re-probe of every node — but a node that had just been shut down kept showing its stale last-known latency instead of going offline. The card's anti-flicker rule (which correctly ignores a single jittery Tor/I2P miss on a node that's actually up) was suppressing every fresh miss, because a failed probe always reported exactly one failure. Now a missed probe is retried once, and only a genuine double-miss is reported as a real outage — so a node you shut down shows as "offline at the moment" on the next refresh, while a merely-flaky-but-alive node still doesn't false-alarm.
fail2ban can no longer lock out your admin machine. The standard node hardening (both the Ansible role and the manual OPERATIONS.md §34 steps) now writes an
ignoreipwhitelist into fail2ban'sjail.local, with afail2ban_ignoreipvariable for your admin IP. This prevents the failure mode where a noisy release ceremony (repeated SSH passphrase prompts → failed auths) got the operator's own IP banned mid-release.Notes
- Upgrade in place; everything from v1.14.0 and earlier is included.
Downloads
-
Source code (ZIP)
4 downloads
-
Source code (TAR.GZ)
5 downloads
-
Morphit v1.14.0 Stable
released this
2026-08-30 03:51:06 +00:00 | 114 commits to main since this releaseMorphit v1.14.0
Theme: a brand-new node reaches a live orderbook in minutes instead of days — and while it catches up, its operator sees exactly what's happening.
Added
Fast-sync a fresh node from a signed, verifiable snapshot. Standing up a new instance no longer means replaying millions of blocks over (often slow or censored) RPC for days. A caught-up federation node now publishes a snapshot of its indexed state to IPFS and anchors a signed pointer to it on-chain; a fresh node fetches it, verifies it three independent ways, restores it, and only catches up the short remaining tail. Days become minutes.
- New operator command:
sudo morphit-ops fast-sync(offered as the recommended path when setting up a new node). It reads the newest snapshot pointer published by a signer you trust, downloads it (with an HTTPS mirror fallback), and proves the download against the on-chain hash — the manifest, the file, and the signed pointer must all agree — before anything is restored. - The trust surface is explicit and layered: you trust the publisher only for the older, settled state; the recent tail is re-verified by normal indexing, and a built-in spot-check confirms the snapshot's records genuinely match the chain before the node serves. Prefer zero trust? A full trustless replay is always one setting away.
- Publishing side: a daily auto-publish timer keeps a fresh snapshot available, and only ever publishes from a node that is itself fully caught up and healthy.
The orderbook now explains itself while an instance is still catching up. Instead of an empty or broken-looking orderbook on a node that hasn't finished syncing, visitors see a clear banner — how far along the sync is, and roughly when orders should be available (in UTC) — in all ten languages. The estimate is derived from the node's actual catch-up rate and shown as "estimating" until there's enough signal to be meaningful.
Changed
- The public censorship-resistant RPC roster carried by every node now includes the newly-online hidden-service nodes alongside the existing ones, so a fresh install reaches the whole set immediately.
- The RPC-endpoints status card now reads "offline at the moment" rather than "unreachable" for a node that didn't answer on its last check — clearer, and less alarming for a node that's merely re-establishing.
Notes
- No database migration and no on-chain changes are required to upgrade.
- Everything from v1.13.2 and earlier is included.
Downloads
-
Source code (ZIP)
2 downloads
-
Source code (TAR.GZ)
8 downloads
- New operator command:
-
Morphit v1.13.2 Stable
released this
2026-08-29 22:05:48 +00:00 | 115 commits to main since this releaseMorphit v1.13.2
Theme: a node can never come up with a broken or missing web frontend again — online or from a USB stick with no internet at all.
Fixed
An incomplete frontend build can no longer take a whole node dark. If the web build ever finished without its root entry point (
index.html) — every per-locale page present but the root missing — the site returned HTTP 500 on every request: nginx's fallback rewrote/index.html → /index.htmlin an endless loop. A real operator's node went completely dark this way while the box itself was perfectly healthy. Three independent guards now make that impossible:- The build guard verifies
index.htmlis actually present before trusting a shipped frontend, and rebuilds rather than serving an incomplete one; after any fresh build it fails loudly ifindex.htmldidn't appear, so an incomplete build can never pass as success. - The install now stops with a clear message (and a memory hint) if the frontend is missing its entry point, instead of deploying a dark site.
- The frontend web server now degrades to a clean error instead of an infinite redirect loop if the entry point is ever absent.
Offline / USB installs now carry the prebuilt frontend. The offline "appliance" bundle — the one you can hand someone on a USB stick for a node with no internet — was shipping everything except the built frontend, forcing the air-gapped machine to build it on-target. That on-target build is memory-heavy, isn't byte-for-byte reproducible with the canonical release, and (as above) could fail silently. The bundle now builds the canonical frontend once and ships it, so an air-gapped node serves the exact same bytes as an online one, with no build required on the target. The bundle refuses to ship if that frontend didn't make it in.
Notes
- Display-and-packaging release: no database migration and no on-chain changes.
- Operators on a node whose site is currently returning 500 or was hand-patched will have it made permanent by upgrading to this release.
- Everything from v1.13.1 and earlier is included.
Downloads
-
Source code (ZIP)
4 downloads
-
Source code (TAR.GZ)
8 downloads
- The build guard verifies
-
Morphit v1.13.1 Stable
released this
2026-08-29 04:06:29 +00:00 | 116 commits to main since this releaseMorphit v1.13.1
Theme: the node-status display finally tells the truth about a slow or reconnecting RPC node — a healthy-but-onion-routed node no longer looks dead.
Improved
A reconnecting hidden node is no longer mislabelled "unreachable." In the RPC-endpoint list, a Tor or I2P transport that's momentarily down but whose same node is answering on its other transport is now shown as amber "re-establishing" instead of a red "unreachable." The reasoning is honest: if a node answers over I2P, the box is clearly up, so its quiet Tor onion is just re-publishing its descriptor (which takes a few minutes after any reconnect) — not gone. A node that's genuinely down on every transport still shows red. This is inferred purely from what the pool already measures, with no cooperation needed from the node.
RPC latency is now colour-coded to what it actually means. Endpoint round-trip time reads green under 5 seconds, amber from 5–10 seconds, and red at 10 seconds or more. Tor and I2P legitimately take a few seconds, so onion-routed nodes running 1–5 s now read as the healthy green they are, instead of a washed-out "slow" grey — and only a genuinely sluggish node turns amber or red.
Both changes apply consistently to the in-app RPC-endpoints card and to
morphit-ops healthon the server, so the browser and the CLI agree.Notes
- Display-only release: no database migration, no on-chain changes, no behaviour change to how the pool selects nodes.
- Everything from v1.13.0 and earlier is included.
Downloads
-
Source code (ZIP)
4 downloads
-
Source code (TAR.GZ)
7 downloads
-
Morphit v1.13.0 Stable
released this
2026-08-28 21:16:37 +00:00 | 117 commits to main since this releaseMorphit v1.13.0
Theme: a rock-solid first install on any network — including heavily censored ones — and a config mistake that took a node down is now impossible to ship.
Fixed
The indexer and relay no longer crash-loop when you set a fee recipient. The setup wizard writes your fee-recipient account into
morphit.config.env, but the config loader's allowlist didn't recognise that key and aborted on every boot — so both services crash-looped from the first start, pinning the CPU and taking the whole node offline (the database never migrated, backups skipped, the canary couldn't publish, and the site returned 500/403).MORPHIT_INDEXER_FEE_RECIPIENTis now allowlisted where it always belonged, alongside the other fee-tuning keys. A new CI guard (config-env-allowlist-parity) cross-checks every key the installer writes intomorphit.config.envagainst the allowlist and fails the build if they ever drift again, so this class of mistake can never reach an operator.Your contact URL now actually reaches the federated directory. The operator registration broadcasts your contact link (e.g. a Matrix DM) on-chain so users on other instances can reach you — but the value was read from the wrong file (
indexer.env) instead of the file it's written to (morphit.config.env), so the registration went out with an empty contact even when you'd set one. It now reads from the correct file, and a new guard asserts every instance-branding field (name, origin, operator tag, contact) is read from the same place, so this can't regress. Re-running the registration (or your next upgrade) puts your contact on your directory card.A tor-only instance that's up no longer flaps to a false "Unreachable." The federated directory probes hidden-service peers over Tor/I2P, and a single slow or dropped circuit — routine for onion routing — would flip a perfectly healthy onion-only node straight to a red "Unreachable," the same badge a genuinely dead node wears. Hidden-service peers now get hysteresis: they must miss several probes in a row before being marked unreachable, mirroring the benefit-of-the-doubt already given when our own proxy is down. Clearnet peers are unchanged (a clearnet timeout is a reliable signal).
Improved
A first install now survives a stale, partial, or filtered package cache. On a fresh server image — or a slow, filtered, or censored connection — apt can hold an outdated index and try to fetch point-release
.debs the mirror has already superseded, giving a wall of "404 Not Found" that stopped the install cold. Base-package installation now self-heals exactly the way an operator would by hand (rm -rf /var/lib/apt/lists/* && apt clean && apt update) and retries automatically, so a first-time operator never sees a scary failure or has to touch apt.I2P installs cleanly on networks that block Launchpad and keyservers. The i2pd install used to add a PPA, which fetches a signing key from a keyserver via deprecated tooling — both commonly blocked in censored countries, where it failed outright. When the offline bundle is present (which carries the maintained i2pd build), i2pd is now installed straight from that bundled package — no PPA, no keyserver, no Launchpad. On an online box with no bundle, the PPA step now retries a few times and, if it still can't be reached, falls back to the distribution's i2pd rather than halting the whole install.
The offline bundle now proves its runtime-critical source survived packaging. The bundle's build-time completeness check verified the vendored apt/docker/kubo/node payloads; it now also asserts the indexer and relay entrypoints, the
tsxlauncher, and every workspace package's source are actually in the shipped tarball — so a future packaging change can never quietly ship a bundle that installs but then can't start.The "run a node" page speaks plainly about what you earn and links where you'd go next. It now states you earn 90% of the BLURT paid listing fees, links "your own instance" straight to the instance directory, and gives realistic hardware guidance (2+ CPU cores, 4+ GB RAM, 60+ GB drive space). A new paragraph explains how your included Tor and I2P addresses — plus encouraging a VPN — let users reach you from jurisdictions where clearnet access is blocked, with no SSL certificate needed.
The instances directory page explains federation up front. The intro now describes how independent operators run instances and earn 90% of the listing fees on their sites, with links to the FAQ, the download, and the run-a-node page. The intro and the bookmark tip span the full content width, the live "LIVE" indicator sits on the same row as the status filter, and the "directory last updated" line now appears just below the instance cards.
Assorted accuracy and polish. The homepage/SEO descriptions and the public comparison image were refreshed and brought in line with the current feature set, and the operator brag-list figures were audited against the live counts.
Notes
- No database migration in this release.
- Everything from v1.12.21 and earlier is included.
Downloads
-
Source code (ZIP)
2 downloads
-
Source code (TAR.GZ)
5 downloads
-
Morphit v1.12.21 Stable
released this
2026-08-27 06:33:15 +00:00 | 119 commits to main since this releaseMorphit v1.12.21
Theme: a faster, calmer, self-tidying upgrade — and a status label that tells the truth.
Improved
Upgrading no longer downloads the same release twice. After an upgrade, the box re-seeds the release to IPFS so it becomes an origin host. That seeding step used to re-fetch the ~13 MB release tarball over the network — the very tarball the upgrade had just downloaded seconds earlier — which was painfully slow on a Tor-only node. The upgrade now hands the seed the tarball it already has (a local copy, no second download), and cleans up the download scratch afterward so nothing is left on disk.
A braille spinner now runs during any slow step. The seed's
ipfs addand DHT announce, and the stager's download, previously printed a line and then sat silent for minutes with no sign of life. They now show an animated spinner with a message whenever the terminal is interactive, so an operator is never left wondering whether the process hung. (Piped or logged runs stay clean — the spinner only shows on a real terminal.)Leftover processes from the previous install are stopped automatically. When a process was still running with its working directory inside the old install (now the
.bakbackup), the upgrade used to only print a warning and leave it running stale code alongside the new services. It now stops those superseded processes automatically — a graceful signal first, then a forced stop for any straggler — touching only processes rooted in the backup directory.The install summary now checks the IPNS keep-alive timer. The health roll-up already checked the hourly IPFS pin timer; it now also checks
morphit-ipns-rebroadcast.timer, the 4-hourly job that re-publishes the signed IPNS record to the DHT soipns://<name>stays resolvable (DHT records expire in ~48h). A box that seeds content but silently isn't keeping its name alive now gets surfaced.Fixed
An RPC endpoint no longer reads as "cooling down" one moment and "unreachable" the next. A failing hidden node showed a gray "cooling down" label from the passive health snapshot, then flipped to a red "unreachable" from the live probe — the same node described two contradictory ways. The status now shows the actual failure reason ("timed out", "connection refused", …) consistently, and treats cooldown as the internal backoff detail it is. A node that isn't answering inside its probe window (12s for Tor, 20s for I2P) now reads coherently as what it is, pointing the operator at the real problem instead of a vague one.
Notes
- No database migration in this release.
- Everything from v1.12.20 and earlier is included.
Downloads
-
Source code (ZIP)
4 downloads
-
Source code (TAR.GZ)
10 downloads