27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
# Local ARR Web launcher compatibility recovery
|
|
|
|
## Metadata
|
|
|
|
- Date: 2026-08-06
|
|
- Status: Restored locally; reboot-persistent supervision remains open
|
|
- Scope: owner-local `arr2-web-8766` launcher and local Web listener only
|
|
- Last verified: 2026-08-06
|
|
|
|
## Evidence
|
|
|
|
- No process listened on local ARR ports and `screen -ls` reported no Web session, so the page could not establish a
|
|
connection.
|
|
- The Keychain-backed launcher configuration check passed, but its command still supplied `--node-binary` and
|
|
`--artifact-tool-module`. The current `arr_web.run --help` shows neither option, and its argument parser rejects both
|
|
before application startup.
|
|
- Removing only those two retired launch arguments and starting one detached `arr2-web-8766` session restored the
|
|
service. Local `/healthz` returned HTTP 200; root redirected to the login page, whose browser console had no warnings
|
|
or errors. At verification, both `127.0.0.1:8766` and the current LAN address `192.168.3.48:8766` returned root
|
|
redirect HTTP 303.
|
|
|
|
## Boundary
|
|
|
|
No login, form submission, upload, Finance/object-store/database write, processor run or monthly-worker action was
|
|
performed. The detached Screen process is still not reboot-persistent; the existing supervision maintenance item
|
|
continues to apply.
|