30 Sep

How to Check Website Speed and More Using Chrome’s Inspect Tool

If you’re looking for a quick way to check your website’s performance without installing any additional extensions, Chrome’s built-in Inspect tool is a great solution. This tool not only helps developers inspect the structure of a webpage but also provides powerful insights into website speed, performance, and more.

Here’s how you can use Chrome’s Inspect tool to analyze website speed and explore other features:

Checking Website Speed

  1. Open the Inspect Tool:
    • Right-click anywhere on your webpage and select Inspect, or use the shortcut Ctrl + Shift + I (Windows/Linux) or Cmd + Option + I (macOS).
  2. Use the Network Tab:
    • Click the Network tab in the Inspect window.
    • Reload the page (press F5) and Chrome will capture all the files that load during the page load process.
    • At the bottom of the panel, you’ll find useful metrics like:
      • DOMContentLoaded: Time it takes for the HTML content to be loaded and parsed.
      • Load Time: Total time for all elements (CSS, JS, images) to be fully loaded.
    • You can also see the waterfall view, showing the time taken by each individual resource.

More Features of Chrome’s Inspect Tool

Aside from checking website speed, here are other key features of the Inspect tool that can assist with website analysis:

  1. Elements Tab:
    • This tab shows the HTML structure and CSS styling of the page.
    • You can modify elements on the fly to see how changes affect the design without altering the actual code.
  2. Console Tab:
    • The Console logs JavaScript errors and warnings, allowing developers to troubleshoot problems.
    • You can also execute JavaScript code directly in the console.
  3. Performance Tab:
    • Provides a detailed analysis of your page’s performance.
    • Click Record or reload the page to capture an in-depth view of CPU usage, rendering, and the time spent on various tasks like scripting and painting.
  4. Lighthouse Tab:
    • Offers a comprehensive report on your site’s performance, accessibility, SEO, and best practices.
    • You can run an audit to get suggestions on how to improve your page speed and performance.
  5. Application Tab:
    • Gives you access to view and manage storage, service workers, cookies, and other application-level data.

Conclusion

The Chrome Inspect tool is a powerful all-in-one resource for checking website speed, reviewing code, and diagnosing problems. With just a few clicks, you can analyze load times, identify slow resources, and improve the overall performance of your website.

By leveraging these features, developers can quickly spot issues and optimize websites for better user experiences.

22 Sep

Resolving the “retry time not reached for any host” Error in cPanel Servers

As a server administrator, you might encounter the following error when your mail server attempts to send emails to certain domains:

retry time not reached for any host after a long failure period

This issue commonly arises due to a corruption in the Exim Retry Database. When the Retry Database is corrupted, Exim (the mail server) is unable to reattempt sending emails to the affected domains, leading to this error.

What Causes This?

The Exim Retry Database is responsible for managing email retries when the initial delivery attempt fails. If the database becomes corrupt or locked, your mail server may not attempt to deliver queued emails, resulting in delayed or undelivered messages to the affected domains.

How to Fix This

To resolve the issue, you need to clear and rebuild the Exim Retry Database. Below is the procedure for fixing this on a cPanel server running CentOS or other Linux distributions.

Step 1: Clear the Corrupt Database Files

Start by removing the corrupted retry and waiting files. SSH into your server as the root user and run the following commands:

cd /var/spool/exim/db
rm -f retry retry.lockfile
rm -f wait-remote_smtp wait-remote_smtp.lockfile

These commands delete the retry and wait-remote_smtp files, which contain the retry records for undelivered emails. Lock files are also deleted to ensure that no processes are currently using these databases.

Step 2: Restart the Exim Service

After removing the database files, restart Exim to allow it to recreate the necessary retry files and clear the issue:

service exim restart

For systems using systemd, you can alternatively use:

systemctl restart exim

Step 3: Clean Up the Exim Database

To ensure that old or invalid entries are cleared from the Exim database, you can use the exim_tidydb tool to remove retry records older than one day. Run the following commands:

/usr/sbin/exim_tidydb -t 1d /var/spool/exim retry > /dev/null
/usr/sbin/exim_tidydb -t 1d /var/spool/exim reject > /dev/null
/usr/sbin/exim_tidydb -t 1d /var/spool/exim wait-remote_smtp > /dev/null

This cleans out stale records in the retry, reject, and wait-remote_smtp databases that may still be causing issues.

Step 4: Update Exim and Courier Services

For an added layer of assurance, it’s advisable to force updates of Exim and Courier. This can resolve any lingering issues with the mail system:

/scripts/courierup --force
/scripts/eximup --force

These commands will recompile and update both Exim and Courier to their latest stable versions, ensuring that no underlying issues with these services are present.

Conclusion

Following these steps should resolve the “retry time not reached for any host” error by cleaning up the Exim Retry Database and allowing your server to properly attempt mail delivery again. While this error is often reported for popular domains like Gmail, it can occur with any domain if there’s an issue with the Exim database or network interruptions. If the problem persists after taking these steps, it may indicate a deeper issue such as network misconfiguration or external mail filters affecting delivery.

12 Sep

How to Create a Subdomain in cPanel

cPanel has streamlined its interface, combining the Subdomain, Addon Domain, and Parked Domain options into a single menu called Domains. Subdomains are useful for directing visitors to specific sections of your website or hosting separate projects while keeping your main domain intact.

Follow the steps below to create a subdomain in your cPanel account:

Steps to Create a Subdomain:

  1. Log into your cPanel Account
    Once logged in, navigate to the Domains section and click on the Domains menu.
  2. Click the ‘Create A New Domain’ Button
    This option allows you to create a new domain or subdomain.
  3. Enter the Subdomain Name
    In the Domain text box, type in the subdomain you want to create, such as test.tetrahostbd.com. The format will be subdomain.maindomain.com.
  4. Customize the Directory for Your Subdomain
    By default, cPanel will create a directory for the subdomain inside the public_html folder.
    • Deselect the option “Share document root (/home/username/public_html) with ‘domain.tld’” if you want the subdomain to have a unique directory.
    • Specify the directory path where you want the subdomain’s files to be stored, or use the auto-generated directory.
  5. Submit Your Changes
    After entering the required information, click Submit to create your subdomain.

Important Notes:

  • The subdomain will be live within 5–10 minutes, although DNS propagation may take up to 30–40 minutes for the changes to fully take effect worldwide.

By following these steps, you can easily set up subdomains for different sections of your website or individual projects, all under the same cPanel account.