Troubleshoot a Node.js Deployment
When a Node.js process exits, use the first meaningful error in the console rather than changing several settings at once. Work through the runtime, files, start command, environment and resource limits in that order.
The consolex1 custom egg
The Node.js Universal egg is developed by the consolex1 hosting provider. Its source code is public on GitHub.
1. Confirm the runtime and entry point
Check that the selected Node.js version is compatible with the project and that the configured entry file exists with the same capitalization. Older runtimes may be available for compatibility but are no longer maintained upstream.
2. Check the package manifest
Verify that package.json is present and contains the production start script used by the instance. Keep the lockfile with the manifest so dependency versions remain reproducible.
3. Read dependency errors first
For a missing-module error, confirm that the package is declared in the project manifest and that installation completed successfully. Do not upload node_modules from a different operating system as a first fix.
4. Validate configuration and ports
Check required environment variables in the panel and confirm that the application reads the port supplied by its hosting environment. Keep credentials out of source code and logs.
5. Check memory and logs
Look for repeated restarts, memory exhaustion or large log output. Reduce unnecessary dependencies and test with a small workload; the Free plan has 256 MB RAM and 512 MB storage.