Troubleshooting Center

Welcome to the CoreSight troubleshooting center. This section is dedicated to resolving common issues you might encounter while operating the platform.

Troubleshooting Flowchart

Diagnostic Methodology

Before looking for a specific solution, here are the basic diagnostic steps to systematically perform in case of malfunction.

1. Check Service Status

The main command to verify that the Node.js backend is running properly:

sudo systemctl status coresight

If the status is not active (running), the service has encountered an error.

2. Check the Logs

Application logs are managed by journald. This is the most valuable source of information to understand an error.

# View the last 50 lines of logs
sudo journalctl -u coresight -n 50 --no-pager

# Follow logs in real-time (useful during testing)
sudo journalctl -u coresight -f

3. Check API Health (Healthcheck)

If the service is running but the interface isn't loading, check if the API responds locally:

curl -k https://localhost/api/health

A normal response looks like: {"status":"ok","version":"1.1.0","uptime":3600}.

Problem Categories

Choose the category corresponding to your issue:

• Startup and Systemd Service: The service refuses to start, loops, or shows MODULE_NOT_FOUND errors.
• Database & Backups: SQL errors, file corruption, restoring a backup, or encryption key issues.
• Network and SSL Certificates: Port 443 is inaccessible, permission errors, or expired Let's Encrypt certificate.
• Accounts and Authentication: Total loss of admin access, command-line password reset, or 2FA lockout.