Service Issues (Systemd / Node.js)

This page covers issues related to the startup and execution of the CoreSight background process.

The service is "inactive (dead)" or "failed"

Check the logs with journalctl -u coresight -n 50.

Error: Cannot find module 'better-sqlite3-multiple-ciphers' or MODULE_NOT_FOUND

This error occurs if the Node.js native dependencies were not compiled for the correct target architecture during the release build, or if the node_modules folder is incomplete.

Solution:

1. Make sure you are using an official release archive generated by the build-release.sh script.
2. Reinstall the application to overwrite the defective files: run the install.sh or update.sh script again.

Error: Error: listen EADDRINUSE :::443

Port 443 is already occupied by another application (for example, an Apache or Nginx server already installed on the machine).

Solution:

1. Identify the process using the port:

   sudo fuser 443/tcp
   # or
   sudo lsof -i :443

2. If it is an unnecessary process, stop and disable it.
3. If you have an existing Apache (e.g. for wiki.coresightsec.com), ensure CoreSight listens on another port (e.g. 5174 via PORT=5174 in .env) and use Apache as a reverse proxy to CoreSight.

The service restarts in a loop

If the service constantly restarts, there is probably a critical error at startup that causes the server/index.js script to crash (for example, a syntax error in .env or a corrupted database). Carefully check the first lines of the error log after a restart.