View access and error logs

Consult the logs on web hosting

The server logs (Apache/LiteSpeed, PHP, e-mail) are essential to diagnose 500 errors, intrusions and performance problems on your web hosting Anthony IT Solutions.

This guide locates log files in the panel, interprets current messages and activates WordPress debug securely.

What you need

• Access panel
• Repeated or timed incident
• Context error 500
• Optional SFTP for debug.log

Types of logs available

Access via panel

1. Logs Section

   Panel → Logs or Statistics → Errors.

2. Domain selection

   Logs by vhost if multi-domain.

3. Download

   Archive for local analysis.

4. Rotation

   Old Logs archived automatically.

Read PHP Error

1. Fatal error

   File and line, correct syntax or Update plugin.

2. Memory enhanced

   Increase memory_limit, PHP.

3. Maximum execution time

   Script long, cron or optimization.

4. Undefined function

   PHP extension missing.

WordPress Debug

1. wp-config

   WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY False.

2. debug.log

   File wp-content/debug.log via SFTP.

3. Disable

   Make false after diagnosis.

4. Security

   Do not leave debug visible to visitors.

Analyze access.log

• Repeated 404 codes, broken links or scan
• 403, permissions or WAF
• POST wp-login, crude-force
• User-agent bots, optional filtering
• **Escalade**, see detailed procedures.

Troubleshooting

• Empty logs, Sync delay or bad domain.
• debug.log huge, Disable deprecated records.
• Permission denied, Protected log path, panel only.
• No PHP error, Check .htaccess or disk quota.

Frequently Asked Questions

Logs how long?
7 to 30 days depending on offer, download if needed.

SSH tail -f ?
Rare on mutualised, panel or SFTP download.

Logs visitors GDPR?
IP anonymization possible via CMS.

LiteSpeed debug ?
Support temporarily activated if necessary.

Related guides

• Error 500
• Panel
• Cron
• WP security

See also our web hosting offer and all the procedures on wiki web hosting.