ThisCalculator

Everyday

How to Troubleshoot Shared Hosting Problems

Updated · Standard formula, shown below

How to Troubleshoot Shared Hosting Problems

Shared hosting can slow down, throw errors, or go offline for many reasons, but most issues are fixable without leaving your plan. This guide walks you through the most common problems—slow loading, 500 errors, email failures, and more—and shows you the exact steps to diagnose and resolve them. You’ll need your hosting control panel login (cPanel, Plesk, or your provider’s custom panel) and FTP or File Manager access.

What You’ll Need

  • Your hosting account login credentials (username and password).
  • Access to your hosting control panel (cPanel, Plesk, or similar).
  • FTP credentials or the File Manager tool in your control panel.
  • A web browser and a text editor (like Notepad or VS Code) for editing files.
  • Your domain name registrar login, in case DNS is involved.

Step-by-Step

  1. Identify the exact symptom. Write down what you’re seeing: a specific error code (e.g., 500, 503, 404), a blank page, slow loading, or email not sending. This determines your next steps.
  2. Check if the problem is on your end. Try loading your site from a different device or network. If it works there, the issue may be your local connection, cache, or DNS.
  3. Clear your browser cache and DNS. In your browser, clear cached images and files. Then flush your local DNS: on Windows, open Command Prompt and run ipconfig /flushdns; on macOS, use sudo dscacheutil -flushcache.
  4. Log into your hosting control panel. Go to your provider’s login page, enter your credentials, and open the control panel (usually cPanel or Plesk).
  5. Check server status. Many providers have a status page or show server load in the control panel. If the server is down, wait a few minutes and refresh. If it’s a provider-wide outage, you may need to contact support.
  6. Review error logs. In cPanel, look for “Errors� or “Error Logs� under the “Metrics� section. In Plesk, go to “Logs� in your domain’s settings. Look for entries around the time of the problem. Common entries include PHP fatal errors, file permission issues, or database connection failures.
  7. Check file permissions. Files should be 644 (read/write for owner, read for others) and directories 755. In File Manager, select your files, click “Permissions,� and set them correctly. Incorrect permissions often cause 500 errors.
  8. Test a simple PHP file. Create a file named test.php with the content <?php phpinfo(); ?> and upload it to your public_html folder. Access it via your domain (e.g., yourdomain.com/test.php). If it shows PHP info, PHP is working. If it downloads or shows an error, PHP is misconfigured.
  9. Disable plugins/themes (if using WordPress). Rename the plugins folder to plugins_old via File Manager. If the site loads, a plugin is the culprit. Then rename it back and deactivate plugins one by one. Do the same with the active theme folder.
  10. Check database connections. If you use a CMS, ensure your database credentials in the config file (e.g., wp-config.php) are correct. In cPanel, use “MySQL Databases� to verify the database and user exist and the user has all privileges.
  11. Monitor resource usage. In cPanel, check “Resource Usage� or “CPU and Concurrent Connection Usage.� If you’re hitting limits, you may see 503 errors. Reduce resource use by enabling caching, optimizing images, or upgrading your plan.
  12. Test email sending. If email fails, check your mail settings in the control panel. Ensure your domain’s MX records point to your hosting provider’s mail server. Try sending a test email from the control panel’s email manager.
  13. Run a DNS check. Use an online DNS lookup tool to see if your domain resolves correctly. If DNS was recently changed, wait up to 48 hours for propagation.
  14. Contact your host’s support. If nothing works, provide them with your error logs, the steps you’ve taken, and the exact error message. They can check server-side issues you can’t see.

Common Mistakes

  • Skipping the basics: Restarting your router or clearing your cache often fixes “site downâ€� issues that are actually local.
  • Editing files without backups: Always download a copy of any file before changing it. One wrong line can break your site.
  • Ignoring error logs: The logs tell you exactly what’s wrong. Guessing without them wastes time.
  • Setting permissions to 777: This is insecure and can cause errors. Use 644 for files and 755 for directories.
  • Changing DNS without waiting: DNS changes can take up to 48 hours. Don’t panic if it doesn’t update immediately.

Tips

  • Keep your CMS, plugins, and themes updated to avoid compatibility issues.
  • Use a caching plugin or enable server-side caching to reduce load.
  • Regularly back up your website files and database—most hosts offer automated backups.
  • If you’re on a very cheap plan, consider upgrading if you consistently hit resource limits.
  • Use a CDN to offload traffic and improve speed.

Troubleshooting

If the steps above don’t resolve your issue, try these additional checks:

  • If your site is still down: Check if your domain has expired. Log into your registrar and verify the renewal date.
  • If you get a 403 error: This often means a file permission issue or an .htaccess rule. Temporarily rename .htaccess to .htaccess_old and see if the site loads. If it does, the file is the problem.
  • If you see a “database connection errorâ€�: In cPanel, go to “MySQL Databasesâ€� and check that the database exists and the user has all privileges. You can also try repairing the database via phpMyAdmin.
  • If emails bounce: Check your mail queue in the control panel. Also verify that your domain’s SPF and DKIM records are set correctly—most hosts provide these in the email section.
  • If the site is slow: Use your hosting’s resource usage tool to see if you’re hitting CPU or memory limits. If so, disable heavy plugins, enable caching, or consider a VPS.
  • If you can’t log into your control panel: Try resetting your password via the “Forgot Passwordâ€� link. If that fails, contact support—they can verify your identity and restore access.

Frequently Asked Questions

Why does my shared hosting site keep going down?

Most likely, you’re exceeding your plan’s resource limits (CPU, memory, or entry processes). Check your resource usage in the control panel. If you’re consistently near the limit, consider upgrading or optimizing your site with caching and image compression.

What is the most common cause of a 500 Internal Server Error?

Incorrect file permissions, a corrupted .htaccess file, or a PHP fatal error are the top culprits. Check your error logs first, then fix permissions to 644/755, and rename .htaccess to test.

How do I check my error logs in cPanel?

In cPanel, scroll to the “Metrics� section and click “Errors.� You’ll see a list of recent errors with timestamps. Alternatively, you can access the raw log via the “Raw Log Manager.�

Can I upgrade my shared hosting if I keep hitting limits?

Yes. Most providers offer higher-tier shared plans or VPS. Before upgrading, try optimizing your site—enable caching, use a CDN, and remove unused plugins. If you still hit limits, upgrading is the next step.

Why is my email not sending from my shared hosting account?

Check your SMTP settings (usually mail.yourdomain.com, port 465 or 587). Also verify your domain’s MX records point to your host. If you’re using a third-party email client, ensure your password is correct and you’re using the right authentication method.

How long does DNS propagation take after I change nameservers?

Typically 24-48 hours, but it can be faster. During this time, some users may see your old site, others the new one. Use an online DNS checker to see if your changes have propagated globally.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.