Troubleshooting & Diagnostics

Troubleshooting

Diagnostic guides, common exception resolutions, and system recovery procedures for XyPriss and the xfpm runtime engine.

Zero-Trust Error Model
XyPriss fails fast and loudly when execution invariants are violated. Most runtime startup crashes originate from unconfined process execution or missing libXESS supervision rather than application code bugs.

Common Issues & Security Violations

Critical Security Violation

libXESS Environment Confinement Violation

XessShieldRequiredError: Triggered when invoking servers directly via raw node, bun, or ts-node instead of the official xfpm CLI.

View diagnosis & fix
Tooling Sync

Outdated XFPM Tooling & Binary Mismatch

When XFPM CLI binaries fall out of sync with the project engine requirements, run xfpm upgrade -f or re-run the official installer.

Covered in the libXESS Violation Guide (Solution 2).

Diagnostic Checklist

1. Check Execution Wrapper

Verify that your package.json scripts use xfpm dev, xfpm run, or xfpm start instead of naked runtime binaries.

2. Verify Confinement State

Ensure libXESS supervisor is actively wrapping the process before network sockets attempt to bind.

3. Sync Engine Dependencies

Always install packages via xfpm install to maintain content-addressable dependency integrity and CAS signatures.

libXESS Environment Confinement Violation

Resolve XessShieldRequiredError and unconfined direct runtime crashes.