If you're seeing a 404 error or experiencing issues with LogSpot not working as expected, this guide covers the most common causes and how to fix them.
1. Install Required Packages
LogSpot depends on two packages: goaccess and logtail. If they are missing, LogSpot will fail to load or show a 404 error.
sudo apt install goaccess
sudo apt install logtail2. Restart LogSpot Service
After installing the required packages, restart the LogSpot service:
sudo systemctl restart cpflogspot.service3. Check the LogSpot Service Logs
If the issue persists, check the service logs for more details:
sudo journalctl -u cpflogspot.serviceLook for any errors or warnings that might point to missing dependencies, permissions, or misconfigurations.
4. Check for Custom Document Root
LogSpot writes reports to /public_html/traffic-reports or /httpdocs/traffic-reports by default. If your site uses a custom document root, you need to create a symlink to make the reports accessible.
Example: If your document root is a custom folder, run the following inside that folder:
ln -s ../traffic-reports traffic-reportsThis will expose the traffic reports in the correct path for your custom configuration.
Once the required packages are installed, the service is running, and the correct symlink is in place, LogSpot should start displaying logs as expected.
Need Further Assistance?
Visit our Knowledgebase or contact our support team for help.
