lfg2025
released this
2026-05-18 15:55:20 +00:00
| 382 commits to main since this release
- Home dashboard status cards now keep the last known good system, VPN, Bitcoin, and FIPS values while route changes or transient RPC failures are in flight, avoiding false "not configured" or "not running" flashes.
- Home, Web5 Monitoring, and the Monitoring page headline cards now share the same live system-stat snapshot for CPU, memory, disk, uptime, and load so the visible numbers agree across the UI.
- Settings What's New is filled through
v1.7.67-alpha, including the missing historical v1.7.44-alpha through v1.7.66-alpha entries.
- Bitcoin/Knots/Core shell lifecycle specs now match the Rust app config memory policy: 8 GiB on normal hosts, 4 GiB on low-memory hosts, and pruned Knots uses a larger dbcache on hosts with enough RAM to improve IBD throughput.
- ElectrumX/electrs shell lifecycle specs now match the 4 GiB memory policy used by the Rust app config, reducing drift between first boot, reconcile, and app lifecycle paths.
- Live assessment of
100.70.96.88 identified the current IBD bottlenecks as CPU/thermal/I/O pressure rather than RAM exhaustion, with follow-up work planned for existing-node swap repair, kiosk Chromium CPU reduction, and reconcile failure cleanup.
Downloads
lfg2025
released this
2026-05-18 14:17:20 +00:00
| 385 commits to main since this release
v1.7.66-alpha (2026-05-18)
- Nginx Proxy Manager stale-port repair now detects stopped or
Created Podman records by inspecting podman ps -a port metadata, covering records where podman port nginx-proxy-manager returns no mapping until start.
- Live recovery on
100.70.96.88 removed only the stale Nginx Proxy Manager container record and recreated it with 8081:81, 8084:80, and 8444:443, preserving /var/lib/archipelago/nginx-proxy-manager data.
- Validation confirmed Nginx Proxy Manager recovered as healthy and responds through direct admin port
8081, host compatibility port 81, and /app/nginx-proxy-manager/.
Downloads
lfg2025
released this
2026-05-18 13:31:57 +00:00
| 388 commits to main since this release
v1.7.65-alpha (2026-05-18)
- Orchestrator-backed app starts now run the same pre-start repairs as the legacy Podman path, so Nginx Proxy Manager stale
81:81 container metadata is removed and recreated before the orchestrator tries to start it.
- Live diagnostics on
100.70.96.88 confirmed host nginx is healthy while Nginx Proxy Manager has no listeners on 8081, 8084, or 8444, causing host nginx 502 responses for NPM proxy paths.
Downloads
lfg2025
released this
2026-05-18 03:25:16 +00:00
| 391 commits to main since this release
v1.7.64-alpha (2026-05-18)
- Update apply rate limiting is relaxed for authenticated admins from 2 attempts per 10 minutes to 10 attempts per minute, preventing the System Update page from getting stuck behind
429 Too Many Requests during legitimate OTA retry/troubleshooting flows.
- The corrected backend artifact rebuild protection from
v1.7.63-alpha remains in place, so this release is built from a fresh Rust backend binary before publishing.
Downloads
lfg2025
released this
2026-05-18 03:03:44 +00:00
| 394 commits to main since this release
v1.7.63-alpha (2026-05-18)
- Release automation now rebuilds the Rust backend after bumping the version and before hashing release artifacts, preventing OTA manifests from pointing at a stale backend binary.
- This corrected release carries the Nginx Proxy Manager stale-port repair in an updated backend binary, so nodes running
1.7.61-alpha can actually receive and execute the fix.
- Validation confirmed the previously published
v1.7.62-alpha backend artifact still contained 1.7.61-alpha, explaining why nodes did not advance after applying that update.
Downloads
lfg2025
released this
2026-05-18 02:40:36 +00:00
| 397 commits to main since this release
v1.7.62-alpha (2026-05-18)
- Nginx Proxy Manager start and restart now repair stale Podman containers that still publish the admin UI on host port
81, which conflicts with host nginx on updated nodes.
- The repair recreates only the stale Nginx Proxy Manager container metadata while preserving
/var/lib/archipelago/nginx-proxy-manager data and using the current 8081:81, 8084:80, and 8444:443 mappings.
- Runtime stale-listener cleanup for Nginx Proxy Manager is shared across start and restart paths so rootless port helper leftovers are still cleared before lifecycle retries.
- Validation passed with
cargo fmt --all --check --manifest-path core/Cargo.toml and cargo check -p archipelago --manifest-path core/Cargo.toml.
Downloads
lfg2025
released this
2026-05-18 02:13:22 +00:00
| 399 commits to main since this release
- Multi-container stack installs now keep their app card in the
Installing state for up to 20 minutes while dependency containers are being pulled and prepared.
- BTCPay Server installs no longer appear to vanish or fail after two minutes while Postgres and NBXplorer are still being created before the primary
btcpay-server container exists.
- The stale-transition escape hatch remains short for start, stop, restart, update, and removal operations, so genuinely wedged lifecycle actions still recover quickly.
- Live validation on
100.70.96.88 confirmed BTCPay Server completed installation and responds on port 23000 with the expected HTTP redirect.
Downloads
lfg2025
released this
2026-05-18 00:45:56 +00:00
| 400 commits to main since this release
- Meshtastic serial detection now rejects malformed or incomplete handshakes instead of accepting unrelated serial devices as a fallback Meshtastic radio.
- Mesh radio auto-detection now skips known non-mesh serial devices such as Sierra Wireless LTE modems and Zooz/Z-Wave sticks, avoiding interference with production peripherals.
- Meshtastic config sync now sends
want_config_id with the correct protobuf wire type, fixing radio-side ignore malformed toradio errors and allowing node-info/contact ingestion.
- The stable
/dev/mesh-radio udev rule no longer claims every ttyACM* device; it only matches known mesh USB serial adapters and known USB CDC ACM radio vendors.
- Live validation on
100.70.96.88 confirmed Archipelago selects /dev/ttyUSB0, identifies the Meshtastic node, and refreshes 103 mesh contacts.
Downloads
lfg2025
released this
2026-05-17 23:44:54 +00:00
| 401 commits to main since this release
- Mobile app launching now keeps known container apps inside Archipelago's app-session flow instead of forcing desktop-only new-tab behavior on phones.
- App sessions on mobile now respect the status-bar safe area so foreground iframe content starts below the device chrome while the fullscreen backdrop remains edge-to-edge.
- Prepackaged website launch buttons now resolve their curated website URLs before website-container fallback logic, restoring launches for the L484 sites and adding the Arch Presentation bookmark.
- Meshtastic contact discovery now drains the radio config stream through completion and retries config sync when the contact cache is empty, so nearby nodes already known by the radio are more likely to appear in Archipelago.
- The Apps page now includes a compact sideload button and modal for installing trusted Docker images with optional title, description, and port mapping metadata.
- Sideloaded app title and description metadata now persist through the backend app-config file so refreshed package scans do not collapse custom apps back to generic IDs.
- Validation passed with
npm test -- appLauncher, npm run build, cargo check -p archipelago, and cargo fmt --all --check.
Downloads
lfg2025
released this
2026-05-17 22:40:50 +00:00
| 404 commits to main since this release
Release notes\n\n- Mesh networking now supports Meshtastic radios over the Meshtastic serial API in addition to existing MeshCore Companion USB radios.\n- The mesh listener now probes preferred and auto-detected serial paths for both MeshCore and Meshtastic firmware, preserving the existing reconnect loop so unplug/replug and firmware hot-swap behavior stays consistent.\n- Meshtastic text packets are translated into the existing Archipelago mesh frame pipeline, so current RPC handlers, transport routing, message storage, typed-message decoding, and UI state continue to work without a separate frontend path.\n- Meshtastic node information is surfaced as normal mesh contacts using stable synthetic public keys derived from Meshtastic node numbers, allowing peer refresh and message attribution to reuse existing MeshCore contact handling.\n- Outbound Archipelago mesh messages can now be sent through Meshtastic as channel text packets using the same command path used by MeshCore channel broadcasts.\n- Device status now reports the detected firmware family as meshcore or meshtastic from the shared listener abstraction.\n- Radio udev rules now include USB CDC ACM serial devices (ttyACM*) alongside CP2102, CH340, and FTDI adapters so Meshtastic boards are more likely to appear through the stable /dev/mesh-radio symlink.\n- Host nginx now serves /assets/* hashed frontend chunks as immutable static files with a hard 404 on misses instead of falling back to index.html, preventing strict MIME errors when a browser has a stale pre-update HTML shell.\n- The SPA HTML shell and service-worker files now revalidate on every load, reducing stale frontend references after OTA updates.\n- OTA runtime promotion now installs the bundled nginx-archipelago.conf into /etc/nginx/sites-available/archipelago and reloads nginx after a successful config test, so frontend cache/fallback fixes reach existing nodes without a manual deploy.\n\n## Validation\n\n- cargo check -p archipelago\n- cargo build -p archipelago --bin archipelago --release\n- npm run build\n- scripts/check-release-manifest.sh\n\n## Known limitation\n\n- Live SSH testing against 100.70.96.88 was not completed because temporary public-key authentication was rejected on the target.\n
Downloads