10 Aug

How to Secure Your Computer: A Practical Security Guide for Website Developers and Hosting Users

If you manage websites, hosting accounts, domains, email accounts, databases, or servers, your computer is more than just a personal device.

It is a key to your digital infrastructure.

If your computer becomes compromised, an attacker may not need to “hack” your hosting server directly. They may simply steal the credentials, cookies, SSH keys, API tokens, FTP passwords, cPanel credentials, or session information already available on your computer.

This is why securing your own computer is just as important as securing the server you manage.

Modern attacks increasingly focus on stealing identities rather than breaking into systems. Infostealer malware, phishing, malicious browser extensions, fake software installers, stolen session cookies, and credential leaks can give attackers everything they need to log in as you.

For website developers and hosting users, one compromised workstation can potentially lead to multiple compromised websites or hosting accounts.

Here is a practical security checklist for keeping your everyday computer safer.


1. Understand the Most Important Rule: Your Computer Is Part of Your Security Infrastructure

Many people think:

“My server is secure, so my websites are secure.”

That isn’t necessarily true.

Consider this situation:

You have access to:

  • WHM
  • cPanel
  • SSH
  • FTP/SFTP
  • Git repositories
  • Cloudflare
  • Domain registrars
  • DNS management
  • Email
  • Database servers
  • Hosting billing systems
  • Backup systems

Now imagine that malware running on your computer steals your browser cookies, saved credentials, or SSH keys.

The attacker may not need to exploit your server at all.

They can simply use the credentials you already have.

For administrators and developers, endpoint security is therefore part of server security.


2. Keep Your Operating System Updated

Operating system updates are one of the simplest and most effective security measures.

Enable automatic security updates whenever possible.

Keep updated:

  • Windows
  • macOS
  • Linux desktop distributions
  • Device drivers
  • System components
  • Security software

Do not continuously postpone security updates because they are inconvenient.

Security vulnerabilities are regularly discovered in operating systems and applications. Attackers actively look for machines that have not received available security fixes.

CISA recommends keeping software and operating systems up to date and enabling automatic updates where possible.

For Windows users

Make sure:

Windows Update ? Automatic Updates

is enabled.

Also make sure Microsoft Defender and its security intelligence updates are current.


3. Keep Your Browser Updated

Your browser is one of the most frequently used applications on your computer—and one of the most important security boundaries.

Keep Chrome, Edge, Firefox, Safari, or whichever browser you use updated.

Do not ignore:

“Restart to update”

for weeks.

Modern browsers contain security protections against malicious websites, phishing, dangerous downloads, exploit attempts, and other attacks.

A browser that is several versions behind can expose you to vulnerabilities that have already been fixed.


4. Be Careful About Browser Extensions

Browser extensions can have enormous access to your browsing environment.

A malicious or compromised extension may potentially access sensitive information depending on the permissions it receives.

For a developer or hosting administrator, this can be particularly dangerous.

You may be logged into:

  • WHM
  • cPanel
  • Cloudflare
  • GitHub
  • Google Workspace
  • Email
  • Domain registrar
  • Payment systems

Ask yourself:

Does this extension really need access to my websites and browsing data?

Remove extensions that you:

  • Don’t use
  • Don’t remember installing
  • No longer trust
  • Don’t recognize
  • Installed only temporarily

Install extensions only from reputable sources and periodically review your installed extensions.


5. Password Managers Are Not the Enemy

There is a common belief that:

“Never save passwords in your browser.”

That advice is understandable, but it is too simplistic for modern security.

A reputable password manager can be significantly safer than using the same password—or variations of the same password—across dozens of websites.

CISA recommends using long, random, unique passwords and a password manager to generate and store them.

The important question is not:

“Are my passwords stored?”

The more important question is:

“How are they protected?”

A good password manager should allow you to use:

  • Unique passwords for every service
  • Long randomly generated passwords
  • Strong encryption
  • MFA
  • Biometric or device authentication
  • Password breach detection
  • Secure synchronization

Modern browsers also protect stored credentials using operating-system security mechanisms. For example, Microsoft documents encryption protections for passwords stored in Edge.

But there is an important warning

A password manager does not protect you from an infected computer.

Infostealer malware can target browser credentials, cookies, session information and other sensitive data. Microsoft has documented malware campaigns specifically designed to steal browser credentials and session cookies.

Therefore:

Password manager + secure computer + MFA

is much stronger than simply refusing to save passwords.


6. Use Passkeys Whenever They Are Available

Passkeys are becoming an important replacement for traditional passwords.

Instead of typing a password, you authenticate using your device’s security mechanism, such as:

  • Fingerprint
  • Face recognition
  • Device PIN
  • Hardware security key

Passkeys are designed to resist many forms of phishing because the authentication credential is cryptographically tied to the legitimate website.

Google supports passkeys through Google Password Manager across major desktop and mobile platforms.

For important accounts, prefer:

Passkey > phishing-resistant MFA > traditional password alone

where supported.


7. Enable Multi-Factor Authentication Everywhere Possible

If an account supports MFA, enable it.

This is particularly important for:

  • Email
  • WHM
  • cPanel
  • Cloudflare
  • Domain registrar
  • GitHub/GitLab
  • Google Workspace
  • Microsoft accounts
  • Hosting billing systems
  • Server management systems
  • Banking and payment accounts

But not all MFA methods provide the same level of protection.

Where available, prefer:

  1. Passkeys
  2. Hardware security keys
  3. Authenticator applications
  4. SMS-based authentication

SMS is better than having no second factor, but it is generally not the strongest option.

Microsoft has reported that phishing-resistant MFA can prevent the overwhelming majority of password-based identity attacks, even when an attacker knows the username and password.


8. Never Reuse Your Hosting Password

This deserves its own section.

Your hosting password should not be the same password you use for:

  • Gmail
  • Facebook
  • WordPress
  • Your domain registrar
  • Another hosting company
  • Your personal email
  • Your computer

If another website suffers a data breach and your password is reused there, attackers may try the same credentials against your hosting account.

This is called credential stuffing.

Your WHM/cPanel/hosting password should be:

Unique and used nowhere else.

The same principle applies to your email and domain registrar accounts.


9. Protect Your Email Account Like a Master Key

Your primary email account is often more important than your hosting account.

Why?

Because an attacker who gains access to your email may be able to reset passwords for:

  • Hosting
  • Domain registrar
  • Cloudflare
  • GitHub
  • Social media
  • Payment services
  • Other email accounts

Your primary email should therefore have:

  • A unique password
  • MFA or a passkey
  • Recovery information
  • Security alerts enabled
  • Regular login/activity monitoring

Think of your email account as the master key to your digital life.


10. Do Not Trust Emails Just Because They Look Professional

Modern phishing emails can look extremely convincing.

An email can contain:

  • Company logos
  • Correct branding
  • Professional formatting
  • Realistic signatures
  • Fake support tickets
  • Fake invoices
  • Security warnings
  • Password expiration notices
  • Domain renewal notices
  • “Your account has been suspended” messages

Never assume:

“It has a company logo, therefore it is legitimate.”

Instead, verify the request independently.

For example, if you receive:

“Your Cloudflare account has been suspended. Click here to restore access.”

Do not immediately click the link.

Open your browser and manually visit the official website.

The same applies to:

  • Hosting companies
  • Domain registrars
  • Banks
  • Google
  • Microsoft
  • GitHub
  • Payment providers

11. Check the Website Address Before Logging In

Phishing websites can look almost identical to legitimate websites.

Before entering credentials, check the domain carefully.

For example:

example.com

is completely different from:

example-login.com

or:

example.com.some-random-domain.com

or:

examp1e.com

Attackers frequently use domains that visually resemble legitimate websites.

For highly sensitive services, consider using bookmarks or manually entering the known official address rather than following login links from emails.


12. Do Not Install Random “Tools” From the Internet

This is one of the biggest risks for developers.

You may search for:

  • PDF converters
  • Video converters
  • Cracked software
  • Windows activators
  • Drivers
  • WordPress tools
  • SEO software
  • FTP clients
  • SSH utilities
  • “Free” premium plugins
  • Theme generators
  • AI tools
  • Browser utilities

and download software from an unknown website.

This is dangerous.

A program can appear to work normally while silently installing an infostealer or remote-access malware.

Download software from:

  • The vendor’s official website
  • Microsoft Store
  • Apple App Store
  • Trusted package repositories
  • Official GitHub/GitLab repositories when appropriate

Be particularly suspicious of:

“Disable antivirus before installing.”

That is an enormous red flag.


13. Avoid Pirated and Cracked Software

Cracked software is one of the easiest ways for attackers to distribute malware.

A “free” application may contain:

  • Password stealers
  • Remote access trojans
  • Cryptominers
  • Ransomware
  • Browser stealers
  • Keyloggers

For someone who manages hosting accounts, the risk is much greater because the computer may contain highly valuable credentials.

Saving money on a software license is not worth losing control of your hosting infrastructure.


14. Treat Unexpected Browser Pop-ups as Suspicious

If a website suddenly displays:

“Your computer is infected!”

or:

“Your Windows license has expired!”

or:

“Your browser is outdated!”

or:

“Click Allow to verify you are human.”

Stop.

Do not panic.

Do not install anything.

Do not call a phone number displayed by the website.

Do not grant remote access.

Close the tab/window and investigate using a trusted source.

Websites cannot normally determine that your computer has a virus simply because a pop-up says so.


15. Be Careful With “Allow Notifications”

Many websites ask:

“Allow notifications?”

Users often click Allow without thinking.

A malicious website can abuse browser notifications to display fake:

  • Antivirus warnings
  • Security alerts
  • Cryptocurrency scams
  • Fake Microsoft warnings
  • Fake Google warnings
  • Fake update notifications

Only allow notifications for websites that genuinely need them.

Periodically review browser notification permissions and remove suspicious sites.


16. Do Not Install Unknown Remote-Access Software

Applications such as remote-support tools can be legitimate and useful.

But if someone contacts you unexpectedly and says:

“Please install this software so I can fix your computer.”

be extremely careful.

Never provide remote access to an unknown person simply because they claim to be:

  • Microsoft support
  • Google support
  • Your hosting provider
  • Your bank
  • Your ISP
  • Your antivirus company

If remote access is genuinely required, initiate the support request yourself and verify the support provider independently.


17. Use Antivirus and Endpoint Protection

Modern operating systems already include security protection.

For Windows users, Microsoft Defender provides built-in protection against many common threats.

Keep it enabled and updated.

Do not install multiple antivirus products simply because you think:

“More antivirus = more security.”

Multiple security products can conflict with each other and do not necessarily provide better protection.

More importantly, antivirus is only one layer.

You still need:

  • Updated software
  • MFA
  • Safe browsing
  • Secure passwords
  • Good download habits
  • Regular monitoring

18. Use a Separate Computer for High-Value Administration

If you manage significant hosting infrastructure, consider separating everyday activities from administrative activities.

For example:

Everyday computer

Used for:

  • Social media
  • YouTube
  • General browsing
  • Downloads
  • Personal email
  • Entertainment

Administrative computer

Used primarily for:

  • WHM
  • SSH
  • Server administration
  • Domain management
  • Cloudflare
  • Git repositories
  • Production systems

The idea is simple:

The fewer risky activities performed on your administrative computer, the smaller the attack surface.

Microsoft also recommends dedicated PCs for users with access to high-value assets as part of its credential-protection guidance.

For larger organizations, dedicated privileged-access workstations can be an extremely effective security measure.


19. Do Not Use an Administrator Account for Everything

On your everyday computer, avoid running everything with administrator privileges.

Use a standard user account for normal activities where practical.

When administrator privileges are genuinely required, elevate the operation.

This makes it harder for certain types of malware to immediately obtain system-level privileges.


20. Secure Your Computer’s Login

Your Windows/macOS login itself should be protected.

Use:

  • Strong device password/PIN
  • Fingerprint
  • Face authentication
  • Automatic screen locking

Never leave your workstation unlocked when you walk away.

This is especially important in offices.

Someone does not need sophisticated malware if they can simply sit at your unlocked computer and access your browser, email, hosting panel, or password manager.


21. Secure Your SSH Keys

Developers and server administrators frequently use SSH keys.

Treat SSH private keys like passwords—but potentially even more carefully.

Never:

  • Send private keys through chat
  • Upload them to public repositories
  • Put them inside website files
  • Store them in publicly accessible directories
  • Commit them to Git
  • Share them with customers

Use encrypted key storage and strong passphrases.

Remember:

Private key = authentication credential.

If someone steals it, they may be able to authenticate without knowing your traditional password.


22. Never Put Production Credentials in Source Code

This is extremely important for developers.

Do not put credentials directly inside:

config.php
.env
database.php
settings.php
Git repositories
JavaScript files
public HTML

depending on the application and deployment architecture.

Never commit:

  • Database passwords
  • API keys
  • SMTP passwords
  • Cloud credentials
  • SSH private keys
  • Hosting passwords

to a public Git repository.

Microsoft specifically warns developers not to hardcode passwords, API keys, connection strings, or other secrets in source code.

Use appropriate secret-management and environment/configuration mechanisms instead.


23. Be Careful With Git Repositories

Before pushing a project to GitHub or another Git server, check what you are committing.

A common mistake is accidentally committing:

.env
config.php
backup.sql
database credentials
SSH keys
API keys

Once a secret has been pushed to a repository, simply deleting the file may not be enough because the secret may remain in Git history.

If a secret is exposed:

Treat it as compromised and rotate it immediately.

Do not merely delete the file.


24. Be Careful With FTP

If you manage websites, avoid plain FTP whenever possible.

Prefer:

  • SFTP
  • SSH
  • FTPS where appropriate

Plain FTP transmits credentials without the protection provided by encrypted transport.

Also avoid storing FTP passwords unnecessarily in multiple applications.


25. Be Careful With cPanel and WHM Sessions

For hosting administrators and resellers, browser sessions themselves can be valuable to attackers.

Do not assume:

“I have MFA, therefore I’m completely protected.”

If malware steals an active session cookie, the attacker may potentially use the existing authenticated session without needing the password.

This is one reason endpoint security is so important.

Log out of sensitive systems when they are no longer needed, particularly on shared or untrusted computers.


26. Monitor Your Important Accounts

Security isn’t only about prevention.

Monitor for unusual activity.

Look for:

  • Unknown login locations
  • Unknown devices
  • Password reset emails you did not request
  • New MFA devices
  • New SSH keys
  • New API tokens
  • Unexpected forwarding rules
  • New email filters
  • Unknown administrators
  • Unexpected hosting account changes
  • New FTP accounts
  • New cPanel users
  • Unexpected DNS changes

If something looks suspicious, investigate immediately.


27. Never Ignore Security Notifications

If Google, Microsoft, Cloudflare, GitHub, your hosting provider, or another service tells you:

“A new login was detected.”

Do not simply dismiss it.

Ask:

Was this me?

If the answer is no:

  1. Change the password.
  2. Revoke active sessions.
  3. Remove unknown devices.
  4. Review MFA settings.
  5. Review recovery information.
  6. Check API keys/tokens.
  7. Investigate the computer from which you normally log in.

28. If You Suspect Your Computer Is Infected, Stop Using It for Administration

This is especially important for hosting users.

Suppose several websites suddenly become compromised and you suspect your hosting credentials were stolen.

Do not immediately log into WHM from the same computer and start changing every password.

If the computer is infected, the attacker may simply capture the new passwords as you type them.

Instead:

Use a known-clean device to change critical credentials.

Then:

  1. Change the hosting/reseller password.
  2. Revoke active sessions where possible.
  3. Enable MFA.
  4. Rotate SSH keys if necessary.
  5. Rotate API tokens.
  6. Change email credentials.
  7. Review account activity.
  8. Scan and investigate the original computer.
  9. Check all websites for backdoors and unauthorized accounts.
  10. Re-secure the workstation before using it for administration again.

29. Remember: Malware Can Steal More Than Passwords

This is one of the most important security lessons today.

People often think:

“I don’t save my passwords, so malware can’t steal them.”

Unfortunately, that’s not necessarily true.

Modern infostealers may target:

  • Browser passwords
  • Cookies
  • Session tokens
  • Autofill information
  • Cryptocurrency wallets
  • Browser profiles
  • Email credentials
  • Authentication data
  • Files
  • Application data

Microsoft has documented attacks where malware specifically targeted browser profile data and session cookies, allowing attackers to impersonate users without necessarily needing their password.

Therefore:

Typing your password manually is not a substitute for having a clean computer.


30. Keep Your Browser Profile Clean

Periodically review:

  • Saved passwords
  • Saved payment methods
  • Extensions
  • Notification permissions
  • Download history
  • Unknown browser profiles
  • Signed-in devices
  • Synced data

Remove anything you don’t recognize.

If you suddenly discover an extension you don’t remember installing, don’t simply ignore it.

Investigate how it got there.


31. Be Suspicious of Urgency

Attackers love urgency.

Messages such as:

“Your account will be deleted in 30 minutes.”

“Your domain expires today.”

“Your server has been suspended.”

“Payment failed—click immediately.”

“Your mailbox is full.”

“Your SSL certificate has expired.”

are designed to make you act before thinking.

Slow down.

Verify independently.

A few extra seconds can prevent a major security incident.


32. Back Up Your Important Data

Security is not only about preventing unauthorized access.

You also need to be able to recover from:

  • Ransomware
  • Hardware failure
  • Accidental deletion
  • Malware
  • Lost devices

Keep important files backed up.

For critical business data, maintain backups that cannot simply be deleted by the same account that is compromised.

And periodically test whether your backups can actually be restored.

A backup that has never been tested is only a backup in theory.


33. Secure Your Wi-Fi and Home/Office Network

Your computer is not the only thing that needs protection.

Secure your router:

  • Change the default administrator password.
  • Keep router firmware updated.
  • Use WPA2/WPA3.
  • Disable unnecessary remote administration.
  • Use a strong Wi-Fi password.
  • Review connected devices.
  • Replace old routers that no longer receive security updates.

If you work from public Wi-Fi, be particularly careful with administrative activities.


34. Don’t Trust USB Devices

Avoid connecting unknown USB drives to your computer.

A USB device can contain malicious files or exploit vulnerabilities.

If someone gives you a USB drive containing:

“Important website backup”

don’t automatically plug it into the computer you use to administer your servers.

Use appropriate security controls and scan files before opening them.


35. Security Is About Layers

There is no single magic security setting.

Good security looks more like this:

Secure device

?

Updated OS

?

Updated browser

?

Endpoint protection

?

Strong unique credentials

?

Password manager/passkeys

?

MFA

?

Safe browsing habits

?

Limited privileges

?

Secure server access

?

Monitoring

?

Backups

Each layer reduces the chance that one mistake becomes a disaster.


A Practical Security Checklist for Website Developers

If you develop websites or manage hosting accounts, your minimum checklist should look something like this:

Computer

  • Operating system automatically updated
  • Browser automatically updated
  • Antivirus/endpoint protection enabled
  • Firewall enabled
  • Screen automatically locks
  • Strong device authentication
  • Unnecessary applications removed
  • Unknown browser extensions removed
  • No pirated/cracked software

Accounts

  • Unique password for every important account
  • Password manager or secure credential management
  • Passkeys enabled where available
  • MFA enabled
  • Primary email strongly protected
  • Recovery options secured
  • Old sessions reviewed
  • Unknown devices removed

Hosting

  • WHM/cPanel MFA enabled
  • Unique reseller/hosting password
  • SSH keys protected
  • SFTP/SSH preferred over FTP
  • API keys protected
  • Hosting login activity monitored
  • Unused accounts removed
  • Unused FTP accounts removed
  • Backups available and tested

Development

  • No passwords inside source code
  • No API keys in Git repositories
  • .env and secret files excluded where appropriate
  • Production credentials separated from development credentials
  • Dependencies kept updated
  • Unused plugins/themes/scripts removed
  • Git repositories reviewed before publishing

Email

  • MFA/passkey enabled
  • Suspicious emails independently verified
  • Unexpected attachments avoided
  • Links checked before logging in
  • Security alerts monitored
  • Unknown forwarding rules investigated

The Most Important Lesson

You don’t need to become paranoid about every click on the internet.

But you should become deliberate about what you trust.

The modern attack isn’t always:

“A hacker broke through my server.”

Very often it is:

“Someone stole the administrator’s identity.”

The attacker may obtain that identity through phishing, credential reuse, malware, browser data theft, malicious software, leaked credentials, stolen session cookies, or compromised devices.

For website developers, hosting customers, system administrators, and resellers, the computer sitting on your desk can therefore be one of the most important security boundaries in your entire infrastructure.

Protect the computer. Protect the identity. Protect the accounts. Then protect the server.

Security is not a single product, browser setting, or antivirus application.

It is a habit.

And the best security habit is simple:

Stop assuming that something is safe until you have a reason to trust it.

20 May

How to Check Server Load and Resource Usage on a Windows VPS

Windows provides several easy ways to check CPU usage, RAM consumption, disk activity, and running processes. In this article, we will show you some simple methods to monitor your Windows server resources.


1. Using Task Manager

Task Manager is the easiest way to monitor server performance on Windows.

How to open:

Press:

Ctrl + Shift + Esc

What you can check:

  • CPU usage
  • Memory (RAM) usage
  • Disk usage
  • Network activity
  • Running applications and services

The Performance tab gives a live overview of your server resources.


2. Using Resource Monitor

Resource Monitor provides more detailed information compared to Task Manager.

How to open:

Press:

Windows + R

Then type:

resmon

Features:

  • Detailed CPU monitoring
  • Memory usage breakdown
  • Disk activity tracking
  • Network connection monitoring

This tool is very useful for identifying which application or service is consuming high resources.


3. Check CPU Usage from Command Prompt

Open Command Prompt and run:

wmic cpu get loadpercentage

This will show the current CPU load percentage of the server.


4. Check Memory Usage

Run the following command in Command Prompt:

systeminfo

You will find:

  • Total Physical Memory
  • Available Physical Memory

This is similar to checking RAM usage on Linux using free -m.


5. View Running Processes

To see all running processes, use:

tasklist

This command works similarly to the ps aux command on Linux servers.


6. Check Active Network Connections

To view active network connections and listening ports:

netstat -ano

This can help identify unusual connections or troubleshoot network-related issues.


Final Words

Monitoring your Windows VPS regularly helps maintain server stability and quickly identify resource-related problems. Tools like Task Manager and Resource Monitor make it easy even for beginners, while Command Prompt and PowerShell commands provide more advanced monitoring options for administrators.

If you need assistance managing your Windows VPS or Dedicated Server, feel free to contact our support team anytime.

20 Oct

How to Set Up a Google Workspace Email Account in Outlook

Setting up your Google Workspace email account in Outlook allows you to manage your business emails from one central application, streamlining your communication. In this guide, we’ll walk you through the steps to get your Google Workspace account up and running in Outlook.

Step-by-Step Guide to Adding Your Google Workspace Email Account

  1. Open Outlook and Navigate to Account Settings
    Start by launching Outlook. Click on the File tab, and then select Account Settings under the Info section. This is where you’ll manage all your email accounts in Outlook.
  2. Add a New Email Account
    In the new Account Settings window, click on the New button. A dialog box will appear asking for your email.
  3. Manually Set Up Your Account
    Under Advanced options, select Let me set up my account manually and click Connect. This allows you to enter custom settings for your Google Workspace account.
  4. Select the Google Option
    On the next screen, choose Google as the account type.

Configuring Your Outlook Email Settings

  1. Enter Server Settings
    Now it’s time to configure your incoming and outgoing mail server settings. Enter the following details:
    • Incoming mail server: imap.gmail.com
      • Port: 993
      • Encryption method: SSL/TLS
    • Outgoing mail server: smtp.gmail.com
      • Port: 465
      • Encryption method: SSL/TLS
    Ensure that the account type is set to IMAP, and then click Next.
  2. Enter Your Google Workspace Password
    At this point, Outlook will prompt you to enter your Google Workspace account password. Type it in, and then click Connect.
  3. Sign In to Google
    A new window with the Google logo will appear. Enter your Google Workspace email address and click Next. You’ll then be asked to enter your password and click Sign in.
  4. Verify Your Connection (If Required)
    Depending on your Google account’s security settings, you might need to verify the connection using your phone or another verification method. This step ensures that the connection between Outlook and Google is secure.
  5. You’re All Set!
    After successfully signing in, Outlook will complete the configuration. Click Done, and your Google Workspace emails will start syncing in Outlook!

By following these steps, you can easily integrate your Google Workspace email with Outlook, ensuring you never miss an important message.

For more helpful guides and tips, stay tuned to our blog!

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.

18 Nov

Solving ‘421 Too Many Connections’ Error in FileZilla for Seamless FTP Transfers

FileZilla is a convenient tool for FTP file transfers in cPanel. However, encountering a ‘421 too many connections’ error can disrupt this process. To ensure smooth file transfers, let’s explore two methods to fix this issue.

Understanding the Error:
FileZilla throws this error when attempts exceed 8 connections from the same IP address without closing older ones. Incorrect settings might also trigger unsuccessful connection attempts.

Error Message:
“Response: 421 Too many connections (8) from this IP Error: Could not connect to the server.”

Method 1: Refresh Connections via cPanel

1. Log into your hosting account and access cPanel.
2. Look for “FTP Connections” under the “Files” section. If you can’t find it there, scroll down to locate it.

3. Open “FTP Connections” to see all active connections. Click “Reload” to refresh them.

Method 2: Increase FTP Connections from FileZilla

1. Open FileZilla and navigate to the File Manager option, which might vary based on your operating system. For instance, in iOS, you’ll find an icon, while Windows might display options like File, Edit, etc. Access the File Manager or Site Manager.

2. Click on “My Sites” from the left-sidebar and open the “Transfer Settings” tab.

If the settings area is accessible, select “Limit number of simultaneous connections,” and set the “Maximum number of connections” to more than 8. Click “Ok” to save the settings.

Please note: FileZilla doesn’t facilitate the disconnection of old connections; you’ll still need to use your cPanel account for that.

By following these steps, regardless of the presence of older connections with incorrect settings, you should be able to establish a successful connection between FileZilla and your hosting server.

These methods ensure a hassle-free experience with FileZilla for FTP transfers.

Explore our range of shared and reseller hosting plans!

25 May

Introducing Nagad as a New Payment Option – Convenient and Secure!

We are excited to announce that we have expanded our payment options to provide you with even more convenience and flexibility. As part of this effort, we are now accepting payments through Nagad, a trusted Digital Financial Service offered by the Bangladesh Post Office.

We understand that seamless and secure transactions are of utmost importance to our valued clients, and we believe that Nagad meets these expectations perfectly. With Nagad, you can now make payments directly from your Nagad account using our Nagad Merchant Account. To initiate the payment process, simply follow the steps outlined below:

Log in to your Nagad account.
Navigate to the “Merchant Pay” option.
Enter our Merchant Number: 01841377417.
Ensure that the payment amount matches the total stated on the invoice. There is no need to include any additional payment charges.
Use the invoice number as a reference while sending the payment.

using NAGAD APP

using NAGAD USSD Code

By introducing Nagad as a payment method, we aim to simplify the payment process for you and provide a seamless experience. This secure platform offers various benefits, including real-time transaction notifications, instant payment confirmations, and a user-friendly interface. With Nagad, you can enjoy peace of mind knowing that your payments are being handled securely and efficiently.

Should you encounter any issues or have any questions regarding payments through Nagad, please don’t hesitate to reach out to our dedicated support team. We are here to assist you and ensure a smooth transition to this new payment method.

We value your business and continuously strive to enhance our services to meet your evolving needs. We sincerely hope that the introduction of Nagad as a payment option will bring added convenience to your experience with us. We appreciate your trust and look forward to serving you with the utmost dedication.

Thank you for choosing our services!

26 Jan

Setup Node.js Application in cPanel

We have Cloudlinux installed on shared hosting server which comes with Python and Node JS support. In this tutorial, WE will learn how to easily set up Node.js applications from the cPanel interface.

In order to set up a Node.js application using cPanel interface, use the following steps.

Step #1: Create the application
First, you must create an application. To do this, follow these steps:

Log in to cPanel >> Software >> Setup Node.js App

 

 

On the Node.js selector page, click CREATE APPLICATION to start the application setup:

 

Fill in the fields on the application setup form:

 

 

 

 

 

 

 

 

 

  • Node.js version – select your preferred version from the drop down list
  • Application mode – choose Development or Production from the list. Development may be chosen initially and changed to production later.
  • Application root – the file system location for application files. The entry will be appended to /home/username to form the complete path to the application files in the cPanel home directory.
  • Application URL – the address of the application on the Internet.
  • Application startup file – the initial file that will be processed when launching the application.

Once all information is properly submitted, click CREATE:

 

The application starts automatically. To view a test page for the application, click OPEN:

 

You should see the “It Works!” message appears with the installed version.

Now that a working application is installed, you can enhance the environment with the package.json settings file and the npm package manager.

To do this, follow the next steps:

Step #2: Create the package.json file

To create the package.json file, follow these steps:

cPanel >> File Manager

 

 

In the left hand column of File Manager, click the text of the application root folder:

 

 

 

Click +File to create a new file:

 

In the New File dialog box, type the filename package.json, and then click Create New File:

 

 

 

 

 

 

 

 

Right-click or secondary click on the package.json file in the right-hand column of File Manager and then click Edit. An edit dialog box appears:

 

 

 

 

 

 

 

 

 

In the Edit dialog box, click OK.

Type the following text in the editor screen:

{
"name": "app",
"version": "1.0.0",
"description": "My App",
"main": "app.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "",
"license": "ISC"
}

Click Save Changes to save the file and Click Close to close the editor.

Step #3: Install npm

To install npm, follow these steps:

cPanel – Software – Setup Node.js App

 

 

In the Actions column of the Web Applications list, click the pencil icon of the application you want to edit >> Click Run NPM Install >> The NPM installation runs and displays a success indicator when complete.

 

 

 

To install packages with NPM and do other command line tasks related to the application, log in via SSH and enter the virtual environment for the application using the command shown in the information box at the top of the application setup page:

 

 

 

Great! Now you know how to install Node.js app using the cPanel interface.