Interpreting Startup Logs, Stack Traces, and Error Messages // NodeFlux Docs

Learn how to read application log files, diagnose fatal stack traces, and isolate application crash roots. ## Steps 1. Open your service in the manager panel and navigate to the Console / Logs tab. 2. Scroll to the top o NodeFlux documentation for free Minecraft, Node.js and application hosting.

Learn how to read application log files, diagnose fatal stack traces, and isolate application crash roots. ## Steps 1. Open your service in the manager panel and navigate to the Console / Logs tab. 2. Scroll to the top o

Learn how to read application log files, diagnose fatal stack traces, and isolate application crash roots. ## Steps 1. Open your service in the manager panel and navigate to the Console / Logs tab. 2. Scroll to the top of an error trace to locate the initial root cause exception line. 3. Identify error types: java.lang.ClassNotFoundException (missing plugin dependency), SyntaxError (JavaScript code typo), or ModuleNotFoundError (missing Python package). 4. Check port binding errors: EADDRINUSE indicates another process is holding the port, or wrong port was configured. 5. Check path errors: ENOENT indicates a missing file or incorrect relative directory path. 6. Correct the underlying configuration or code issue before attempting to restart the service. ## Notes - Always focus on the first error line in a stack trace; subsequent errors are often secondary side-effects. - Copy clean error trace snippets when requesting assistance in support tickets.