Logs help identify what’s breaking your website, emails, or applications. They are essential for troubleshooting errors, performance issues, and security problems.

📄 Error Logs in Plesk

Error logs record server-side issues such as PHP errors, permission problems, and failed scripts.

How to Access Error Logs in Plesk

1. Log in to Plesk

2. Go to Websites & Domains

3. Select your domain

4. Click Logs

Common Errors You’ll See

• PHP fatal errors

• File permission issues (403, 500 errors)

• Missing files or incorrect paths

• Plugin or theme conflicts

📌 Tip: Always check the latest timestamp to find the most recent issue.

🐞 WordPress Debug Mode

WordPress debug mode helps identify errors caused by themes, plugins, or custom code.

How to Enable Debug Mode

1. Open wp-config.php

2. Add or update the following lines:

Where Debug Logs Are Stored

• /wp-content/debug.log

When to Use

• White screen of death

• Plugin/theme errors

• Admin panel issues

⚠️ Important: Disable debug mode after troubleshooting to avoid exposing sensitive information.

📊 Access Logs Explained

Access logs record every request made to your website.

What Access Logs Show

• Visitor IP addresses

• Requested URLs

• HTTP status codes (200, 404, 403)

• User agents (browser/device)

• Request time and load duration

Why Access Logs Matter

• Identify broken links (404 errors)

• Detect unusual or malicious traffic

• Analyze traffic patterns

• Debug redirect issues

📌 Example Use Case:
If users report missing pages, access logs can confirm whether the page exists or returns a 404 error.

✅ Best Practices for Log Analysis

• Always check logs immediately after an error occurs

• Clear logs periodically to avoid clutter

• Share error logs with support when opening a ticket

• Avoid editing files directly without checking logs first

The post 🔹 Logs & Debugging appeared first on ecHOST.

🐢 Common Causes of Slow Loading

Website-Level Issues

• Large, unoptimized images

• Too many plugins or heavy themes (especially WordPress)

• No caching enabled

• Excessive JavaScript & CSS files

• Poorly optimized database

Server-Level Issues

• Low CPU / RAM limits (shared hosting)

• High server load from other users

• Slow disk I/O

• No server-side caching

• Outdated PHP version

🖥️ Server Optimization vs 🌐 Website Optimization

🖥️ Server Optimization (Hosting Side)

• Upgrade PHP version (8.0 / 8.1 recommended)

• Enable OPcache

• Use SSD/NVMe storage

• Increase CloudLinux resources (CPU, RAM, IO)

• Enable server-level caching (LiteSpeed / Redis)

• Use HTTP/2 or HTTP/3

📌 Best for: High-traffic sites, eCommerce, dynamic websites

🌐 Website Optimization (Developer Side)

• Enable caching plugin (LiteSpeed Cache, WP Rocket, W3 Total Cache)

• Optimize images (WebP format)

• Minify CSS, JS, HTML

• Reduce unused plugins & scripts

• Clean the database regularly

📌 Best for: WordPress, CMS-based websites

🔍 Performance Testing Tools

Speed Testing

• Google PageSpeed Insights

• GTmetrix

• Pingdom Tools

Server & Real-Time Monitoring

• cPanel → Resource Usage

• CloudLinux LVE Stats

• New Relic / Query Monitor (advanced)

What to Check

• Time to First Byte (TTFB)

• Largest Contentful Paint (LCP)

• Fully Loaded Time

• Server response time

✅ Best Practices to Improve Speed

• Use CDN (Cloudflare)

• Enable browser & server caching

• Optimize images before upload

• Upgrade hosting if resources are consistently maxed

• Keep themes, plugins & PHP updated

The post 🔹 Website Speed Issues appeared first on ecHOST.

📩 Email Not Receiving

Common Causes

• Incorrect email account setup (wrong username/password)

• Mailbox storage is full

• MX records are not pointing correctly

• Emails going to Spam/Junk

• Server IP temporarily blocked by the recipient’s mail provider

How to Fix

• Verify mailbox exists in cPanel → Email Accounts

• Check storage usage → increase quota if full

• Confirm MX records in the DNS zone

• Ask the recipient to check the Spam folder & whitelist the domain

• Test email using Webmail (Roundcube/Horde)

🔐 Authentication Failures

What It Means
Email clients are unable to authenticate with the mail server.

Common Reasons

• Wrong outgoing mail server (SMTP)

• SSL/TLS settings mismatch

• Incorrect port number

• The recent password change was not updated in the email client

Correct Settings (Standard)

• Incoming Server: mail.yourdomain.com

• Outgoing Server (SMTP): mail.yourdomain.com

• Port:

  • SSL: 465

  • TLS: 587

• Authentication: Required

• Username: Full email address

Fix

• Re-enter email password

• Enable SMTP authentication

• Match port + encryption correctly

🚫 Blacklist Issues

What Happens
Emails bounce or go to spam because the server IP or domain is blacklisted.

Causes

• Spam emails sent from compromised accounts

• Weak email passwords

• No SPF / DKIM / DMARC records

• Shared hosting IP reputation issues

How to Check

• Use tools like MX blacklist checkers

• Check bounce-back messages for blacklist names

How to Fix

• Change all email passwords immediately

• Scan the website for malware

• Enable SPF, DKIM & DMARC

• Request delisting from the blacklist provider

• Consider a dedicated IP or upgrading hosting

✅ Best Practices (Prevention)

• Use strong email passwords

• Enable SPF + DKIM + DMARC (VERY important)

• Avoid sending bulk emails from shared hosting

• Monitor email logs regularly

• Use professional email clients (Outlook, Gmail)

The post 🔹 Email Problems (Troubleshooting Guide) appeared first on ecHOST.

Website errors can be frustrating, but most are easy to fix once you know the cause. Below are the most common website errors and their quick resolutions.

🔴 500 Internal Server Error

This error means something went wrong on the server while loading your website.

Common causes:

• Incorrect .htaccess configuration

• PHP version incompatibility

• Faulty WordPress plugins or themes

• Corrupt files or wrong permissions

How to fix:

1. Check Error Logs in Plesk

2. Rename .htaccess and refresh the site

3. Change PHP version in Plesk

4. Disable plugins one by one

5. Set correct permissions

   • Folders: 755

   • Files: 644

📌 Always take a backup before making changes.

🔴 403 Forbidden Error

This error means access to the page is blocked.

Common causes:

• Incorrect file or folder permissions

• Missing index file (index.php or index.html)

• Security rules are blocking access

• IP blocked by firewall

How to fix:

1. Verify file permissions

2. Ensure an index file exists

3. Temporarily disable security plugins

4. Ask ecHOST support to check firewall rules

📌 Most 403 errors are permission-related.

🔴 DNS_PROBE Errors

DNS errors indicate your domain is not properly connected.

Common DNS errors:

• DNS_PROBE_FINISHED_NXDOMAIN

• DNS_PROBE_FINISHED_NO_INTERNET

Common causes:

• Incorrect nameservers

• DNS changes are not propagated

• Expired domain

How to fix:

1. Confirm nameservers are correct

2. Wait up to 24–48 hours after DNS changes

3. Clear the browser and DNS cache

4. Renew expired domain

📌 DNS issues often resolve automatically after propagation.

✅ Quick Troubleshooting Tips

• Check logs before changing settings

• Make one change at a time

• Clear browser and server cache

• Contact ecHOST support if unsure

The post 🔹 Common Website Errors appeared first on ecHOST.