Cannot access from remote machines The server was likely configured using 127.0.0.1 (localhost) as the IP address during installation. This restricts access to the local machine only. Reconfigure the server using its actual IP address or domain name.

SMTP not working Email/alert delivery settings can be reconfigured after installation by editing the configuration files in the installation directory. You do not need to reinstall.

Port conflicts If a required port is already in use by another application, the service will fail to start. Confirm all required ports are free before installation. Use the following to check for port conflicts:

On Linux:

sudo ss -tulnp | grep <port>

On Windows:

netstat -ano | findstr <port>

Service errors on startup Check the application logs for error details:

On Linux:

cd /opt/bluelance/lcollector/logs/general/

cd /opt/bluelance/web/server/logs/

On Windows:

\Program Files\Blue Lance 2-0\Web\Apps\Logs\

\Program Files\Blue Lance 2-0\Collector\Logs\General\

Services not starting automatically on reboot (Linux) If services do not restart after a system reboot, ensure they are enabled:

sudo systemctl enable lta-web

sudo systemctl enable lta-collector

PowerShell execution policy error (Windows) If the installation script fails to run, confirm the execution policy is set correctly before running the installer:

Set-ExecutionPolicy Unrestricted

Remember to reset it after installation completes:

Set-ExecutionPolicy Restricted

For additional support, refer to the Blue Lance documentation at https://www.bluelance.com/docs or contact your system administrator.

Check service status:

sc query LTA_Web

sc query LTA_Server

sc query LTA_DataCollector

All three services should show as running. If any service is not running, check the logs for errors before continuing.

Check logs for errors or warnings:

\Program Files\Blue Lance 2-0\Web\Apps\Logs\

\Program Files\Blue Lance 2-0\Collector\Logs\General\

[Your administrator should note any expected output or common first-run messages specific to your environment.]

/opt/bluelance/web/ecosystem.config.js

Start the application:

cd /opt/bluelance/web

npx pm2 start ecosystem.config.js

Check status:

npx pm2 list

npx pm2 status

npx pm2 logs

Restart the application:

npx pm2 restart ecosystem.config.js

# or restart by app name

npx pm2 restart lta-web

Stop the application:

npx pm2 stop ecosystem.config.js

# or stop by app name

npx pm2 stop lta-web

Save the PM2 process list:

npx pm2 save

Always save the process list after making changes to ensure services restart automatically on system reboot.

Monitor resource usage:

npx pm2 monit

Start a service:

sudo systemctl start lta-web

sudo systemctl start lta-collector

Restart a service:

sudo systemctl restart lta-web

sudo systemctl restart lta-collector

Stop a service:

sudo systemctl stop lta-web

sudo systemctl stop lta-collector

Check service status:

sudo systemctl status lta-web

sudo systemctl status lta-collector

Enable services to start automatically on boot:

sudo systemctl enable lta-web

sudo systemctl enable lta-collector

Check service status:

systemctl status lta-web

systemctl status lta-collector

Both services should show as active and running. If either service is not running, check the logs for errors before continuing.

Check logs for errors or warnings:

cd /opt/bluelance/lcollector/logs/general/

cd /opt/bluelance/web/server/logs/

[Your administrator should note any expected output or common first-run messages specific to your environment.]