ISSUES FOUND:
1. cPanel/Plesk had same "no logs found" issue as InterWorx
- No diagnostic output
- No fallback to analyze all logs
2. Plesk domain extraction missing
- Used cPanel filename extraction for all non-InterWorx
- Plesk has different path structure
PLESK LOG STRUCTURE:
- Logs at: /var/www/vhosts/system/domain.com/logs/
- Files: access_log, access_ssl_log, error_log
- Domain in PATH (like InterWorx), not filename (like cPanel)
FIXES APPLIED:
1. Enhanced Log Detection for cPanel/Plesk (lines 1869-1906):
- Check for ANY logs first (without time filter)
- If zero: Show diagnostics (directory, file count, samples, control panel)
- If some exist: Offer to analyze all logs
- Same pattern as InterWorx fix (commit 87e0ff7)
2. Added Plesk Domain Extraction (lines 325-331):
- Detect Plesk via $SYS_CONTROL_PANEL
- Extract domain from path: /var/www/vhosts/system/[domain]/logs/
- Uses sed pattern: 's|^/var/www/vhosts/system/\([^/]*\)/logs/.*|\1|p'
- Falls back to cPanel method for other panels
LOGIC FLOW:
```
if InterWorx:
domain from /home/user/var/[domain]/logs/
elif Plesk:
domain from /var/www/vhosts/system/[domain]/logs/
else (cPanel/other):
domain from filename
```
TESTING:
✅ Syntax validation passed
✅ Handles all three panel types correctly
✅ Provides helpful diagnostics when logs not found
IMPACT:
- Plesk servers can now use bot-analyzer properly
- Domain extraction works for Plesk log structure
- Better error messages for troubleshooting
- Consistent UX across all panel types
Related: commit 87e0ff7 (fixed InterWorx)
cschantz
6256d9f2f4