← Back to Documentation Home | API Documentation →

Troubleshooting Guide

Disclaimer DISCLAIMER

Important IMPORTANT: This tool is for educational purposes and authorized testing only.
Use only on systems you own or have explicit permission to test.

Troubleshooting Common Issues and Solutions

1. Apache2 Issues

Apache Won't Start

Symptoms:

  • "Apache2 failed to start" error
  • Dashboard shows "Apache2 is not running"

Solutions:

# Check Apache status
sudo systemctl status apache2

# Check for port conflicts
sudo netstat -tlnp | grep :80

# Check Apache configuration
sudo apache2ctl configtest

# Restart Apache
sudo systemctl restart apache2

# Check error logs
sudo tail -f /var/log/apache2/error.log

Permission Denied Errors

Symptoms:

  • "Permission denied" when deploying templates
  • Files not accessible in browser

Solutions:

# Fix Apache directory permissions
sudo chown -R www-data:www-data /var/www/html/
sudo chmod -R 755 /var/www/html/

# Check current permissions
ls -la /var/www/html/

# Fix specific template permissions
sudo chown -R www-data:www-data /var/www/html/facebook/

Port 80 Already in Use

Symptoms:

  • "Address already in use" error
  • Apache fails to bind to port 80

Solutions:

# Find process using port 80
sudo lsof -i :80

# Kill the process
sudo kill -9 PID

# Or change Apache port
sudo nano /etc/apache2/ports.conf
# Change: Listen 80 to Listen 8080

2. Node.js Issues

Port 5000 Already in Use

Symptoms:

  • "EADDRINUSE: address already in use :::5000"
  • Server won't start

Solutions:

# Find process using port 5000
sudo lsof -i :5000

# Kill the process
sudo kill -9 PID

# Or change port in server.js
const PORT = process.env.PORT || 8080;

Permission Denied for Node.js

Symptoms:

  • "EACCES: permission denied" errors
  • Cannot access files

Solutions:

# Run with sudo
sudo node server.js

# Or fix file permissions
sudo chown -R $USER:$USER /path/to/project
chmod -R 755 /path/to/project

Module Not Found Errors

Symptoms:

  • "Cannot find module" errors
  • Missing dependencies

Solutions:

# Reinstall dependencies
rm -rf node_modules package-lock.json
npm install

# Install missing modules
npm install express fs-extra axios

# Check package.json
cat package.json

3. Template Deployment Issues

Template Not Deploying

Symptoms:

  • "Failed to build scam" error
  • Template not accessible after deployment

Solutions:

# Check if server is running with sudo
ps aux | grep "node server.js"

# Verify Apache is running
sudo systemctl status apache2

# Check deployment directory
ls -la /var/www/html/

# Check server logs
sudo tail -f /var/log/apache2/error.log

Template Not Switching

Symptoms:

  • Old template still shows after deploying new one
  • "Clear Apache Directory" doesn't work

Solutions:

# Manually clear Apache directory
sudo rm -rf /var/www/html/*
sudo mkdir -p /var/www/html/

# Check index.html redirect
cat /var/www/html/index.html

# Restart Apache
sudo systemctl restart apache2

Static Assets Not Loading

Symptoms:

  • Images/logos not showing
  • CSS not loading

Solutions:

# Check static assets
ls -la /var/www/html/static/
ls -la /var/www/html/logos/

# Copy assets manually
sudo cp -r client/build/static/logos/ /var/www/html/
sudo chown -R www-data:www-data /var/www/html/logos/

4. Log Issues

No Logs Found

Symptoms:

  • Dashboard shows "No logs found"
  • Credentials not being captured

Solutions:

# Check if template is deployed
ls -la /var/www/html/facebook/

# Check log file exists
ls -la /var/www/html/facebook/usernames.txt

# Check file permissions
sudo chmod 666 /var/www/html/facebook/usernames.txt

# Test credential capture manually
echo "test:password" >> /var/www/html/facebook/usernames.txt

Logs Not Updating

Symptoms:

  • Logs show old data
  • New credentials not appearing

Solutions:

# Check file permissions
ls -la /var/www/html/facebook/usernames.txt

# Fix permissions
sudo chown www-data:www-data /var/www/html/facebook/usernames.txt
sudo chmod 666 /var/www/html/facebook/usernames.txt

# Check PHP execution
sudo nano /var/www/html/facebook/login.php
# Add:

5. Network Issues

Can't Access from Other Devices

Symptoms:

  • Dashboard only accessible from localhost
  • Public IP not working

Solutions:

# Check firewall
sudo ufw status

# Allow port 5000
sudo ufw allow 5000

# Check network interfaces
ip addr show

# Test connectivity
curl http://192.168.1.100:5000

IP Address Detection Issues

Symptoms:

  • Wrong IP addresses shown
  • "undefined" IP addresses

Solutions:

# Check network interfaces
ip addr show

# Test IP detection
node -e "console.log(require('os').networkInterfaces())"

# Manually set IP in server.js
const PUBLIC_IP = '192.168.1.100';

6. PHP Issues

PHP Not Working

Symptoms:

  • PHP files not executing
  • Credentials not being saved

Solutions:

# Install PHP
sudo apt install php libapache2-mod-php

# Enable PHP module
sudo a2enmod php

# Restart Apache
sudo systemctl restart apache2

# Test PHP
echo "" | sudo tee /var/www/html/test.php

PHP Permission Errors

Symptoms:

  • "Permission denied" in PHP
  • Cannot write to files

Solutions:

# Fix PHP file permissions
sudo chown -R www-data:www-data /var/www/html/
sudo chmod -R 755 /var/www/html/

# Make log files writable
sudo chmod 666 /var/www/html/*/usernames.txt

Debug Mode

Enable Debug Logging

File: server.js

// Add at the top
const DEBUG = true;

// Use throughout code
if (DEBUG) {
  console.log('Debug: Template deployment started');
  console.log('Debug: Command:', command);
}

Verbose Apache Logging

File: /etc/apache2/apache2.conf

# Change log level
LogLevel debug

# Enable detailed logging
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\" %D" detailed
CustomLog ${APACHE_LOG_DIR}/access.log detailed

Monitor Logs in Real-time

# Monitor Apache error log
sudo tail -f /var/log/apache2/error.log

# Monitor Apache access log
sudo tail -f /var/log/apache2/access.log

# Monitor application logs
tail -f /path/to/application.log

System Diagnostics

Check System Resources

# Check memory usage
free -h

# Check disk space
df -h

# Check CPU usage
top

# Check running processes
ps aux | grep -E "(apache|node)"

Check Network Configuration

# Check network interfaces
ip addr show

# Check routing table
ip route show

# Check DNS resolution
nslookup google.com

# Test connectivity
ping 8.8.8.8

Check Service Status

# Check all services
sudo systemctl status apache2
sudo systemctl status networking

# Check service logs
sudo journalctl -u apache2
sudo journalctl -u networking

Recovery Procedures

Complete Reset

# Stop all services
sudo systemctl stop apache2
sudo pkill -f "node server.js"

# Clear Apache directory
sudo rm -rf /var/www/html/*
sudo mkdir -p /var/www/html/

# Reset permissions
sudo chown -R www-data:www-data /var/www/html/
sudo chmod -R 755 /var/www/html/

# Restart services
sudo systemctl start apache2
sudo node server.js

Backup and Restore

# Create backup
sudo tar -czf backup_$(date +%Y%m%d).tar.gz /var/www/html/

# Restore from backup
sudo tar -xzf backup_20231201.tar.gz -C /

Getting Help

Log Collection

When reporting issues, collect these logs:

# System information
uname -a
lsb_release -a

# Service status
sudo systemctl status apache2
ps aux | grep node

# Error logs
sudo tail -50 /var/log/apache2/error.log
sudo tail -50 /var/log/apache2/access.log

# Network information
ip addr show
netstat -tlnp

Community Support

  • Discord: https://discord.gg/KcuMUUAP5T
  • GitHub Issues: Create an issue with collected logs
  • Documentation: Check the docs/ folder for detailed guides

Remember: Always test in isolated environments and follow legal guidelines!