Home › Knowledgebase › KB-1515

Why Is My Childcare Centre Website Showing 404 Or 500 Errors?

Summary

This guide helps you troubleshoot and resolve: Why Is My Childcare Centre Website Showing 404 Or 500 Errors?. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Why your childcare centre website is showing 404 or 500 errors

When parents visit your childcare centre website to check enrolment details, download forms, or submit an enquiry, they expect the page to load immediately. A 404 Not Found error means the server cannot locate the requested page, while a 500 Internal Server Error indicates something has gone wrong on the server itself. You may also see database connection errors or blank white screens when trying to log into your administrative dashboard. These issues can interrupt critical parent enquiries and create doubt about your centre's professionalism. This guide walks through the steps to identify and resolve common website errors before you need to escalate to your hosting provider or digital agency.

Quick fix steps

  1. Refresh the page in your browser to see if the error is temporary. Press F5 or Ctrl + R on Windows, or Cmd + R on macOS.
  2. Try accessing the website from a different device or network, such as your mobile phone using mobile data instead of your centre's Wi-Fi. This helps determine whether the issue is isolated to one device or affects all users.
  3. Clear your browser cache and cookies. In most browsers, press Ctrl + Shift + Delete on Windows or Cmd + Shift + Delete on macOS to open the clear browsing data window.
  4. Check whether the error affects every page or only specific pages, such as the enrolment portal, parent handbook, or contact form.
  5. Note the exact error message and any error code displayed, as this will help your hosting provider or website developer diagnose the issue faster.

Check your domain name and DNS settings

  1. Log in to your domain registrar account where your childcare centre's domain name is registered.
  2. Verify that your domain registration is current and has not expired. If the domain has expired, your website and email services will stop working until it is renewed.
  3. If you cannot access your registrar account because you have lost the login details or the original staff member who set it up has left the centre, contact the registrar's support team to recover access.
  4. Check your DNS records to ensure the A record or CNAME points to the correct IP address for your hosting account.
  5. Confirm that your nameservers are set correctly for your hosting provider.
  6. Allow up to 24–48 hours for DNS changes to propagate across the internet if you have recently updated them.

Review recent website changes

  1. Log in to your website's administrative dashboard or content management system.
  2. Check whether any plugins, themes, or extensions were recently installed or updated.
  3. If the error started after an update, temporarily deactivate the most recently updated plugin or theme.
  4. Refresh your website to see if the error disappears.
  5. If you cannot access the dashboard, connect to your hosting account using an FTP client or the file manager in your control panel.
  6. Navigate to the /wp-content/plugins/ directory for WordPress sites, /components/ or /modules/ for Joomla, or /modules/ for Drupal.
  7. Rename the folder of the suspected plugin or extension to disable it, then refresh your website.

Check database connection settings

Back up your files and database before editing any configuration files. Incorrect changes to wp-config.php, .htaccess, or plugin folders can make your website completely inaccessible.
  1. Open your website's configuration file using your hosting control panel's file manager or an FTP client.
  2. For WordPress, locate the wp-config.php file in your root directory.
  3. Verify that the database name, username, password, and host match the details provided by your hosting provider.
  4. Check that your database user has the correct permissions assigned to the database.
  5. Save any changes and refresh your website.
If you edit files via FTP or SFTP, ensure you have the correct credentials from your hosting welcome email. Avoid changing file permissions unless instructed by your developer, as incorrect permissions can block access to your site.

Check server resources and error logs

  1. Log in to your hosting control panel.
  2. For cPanel, navigate to Metrics > Visitors or Resource Usage to check CPU, memory, and disk space usage.
  3. For Plesk, navigate to Websites & Domains > Statistics to review resource usage.
  4. If your account is using shared hosting, high traffic from another site on the same server can occasionally affect your website's performance.
  5. Open the error logs section in your control panel. In cPanel, this is under Metrics > Errors. In Plesk, it is under Logs.
  6. Look for entries that match the time when the 500 error or database connection error occurred.
  7. Note any specific file paths or script errors mentioned in the log entries.
Error logs often reveal the exact line of code or plugin causing a 500 error, which can save significant time when working with your developer or hosting provider.

Verify script and software versions

  1. Check that your content management system, such as WordPress, Joomla, or Drupal, is running a currently supported version.
  2. Ensure your server's PHP version is compatible with your website's theme and plugins. In cPanel, go to Software > Select PHP Version. In Plesk, go to Websites & Domains > PHP Settings.
  3. Review the requirements for each installed plugin or extension and compare them against your server environment.
  4. If a plugin requires a newer PHP version than your server provides, contact your hosting provider to request an upgrade.

Troubleshooting specific errors

404 Not Found errors

500 Internal Server Errors

Database connection errors

Check your SSL certificate

An expired or incorrectly installed SSL certificate can cause browsers to block access to your website or display security warnings instead of your enrolment portal.

Non-WordPress and custom-built websites

If your childcare centre website was built by a digital agency or website developer, or if it is a custom-built site rather than a WordPress, Joomla, or Drupal installation, the troubleshooting steps above may not apply. Custom integrations with systems such as Qikkids, Office 365, or third-party enrolment portals often require developer-level access to fix.

In these cases, contact your website developer or digital agency directly. Provide them with the exact error message, the affected URL, and when the issue first started. If you do not know who manages your website, check your domain registrar account or hosting control panel for the original setup details.

When to escalate

If you have completed the steps above and your website is still displaying 404, 500, or database errors, the issue may require access to server-level settings that are not available on shared hosting. Contact your hosting provider or web developer with the following information:

If you need further assistance from our support team, Open a Ticket.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket