Troubleshooting

Fix a website that is not loading

A step-by-step checklist for a FoxFolio Cloud website that is down, slow, blank or showing an error, from service status to error logs.

Last updated
Last reviewed
For
Customers whose FoxFolio Cloud website is down or showing an error
Time needed
About 20 minutes

Quick answer

Check in this order: the service status page, your service’s status in your account, the domain’s DNS, then the error logs in the control panel. Most outages that affect one site are caused by a PHP or plugin error, an expired domain, an unpaid service or a DNS change. The error message and the log usually point to the cause.

Before you start

  • Access to your FoxFolio Cloud account and control panel

Applies to: Cloud Hosting, WordPress Cloud, Managed WordPress.

Steps

  1. Check for a platform incident

    Open the service status page (opens in a new tab). If there is an incident or maintenance, wait for it to be resolved. See Check FoxFolio Cloud service status.

  2. Check the service in your account

    In your account (opens in a new tab), open Services → My Services. A service that is not Active, or an overdue invoice, explains an outage. Also check Domains if the domain is registered with us.

  3. Read the exact error

    The message tells you where to look:

    • “Server IP address could not be found”: a DNS problem — see Fix a domain that is not resolving.
    • 500 error, blank page or “critical error”: usually PHP code, a plugin or a theme.
    • 403 Forbidden: file permissions, or the web application firewall blocking a request.
    • A browser check page before your site loads is bot protection; completing it lets you through.
  4. Check the error log

    In the control panel, open Access/Error Logs. Look for “Fatal error” lines near the time the problem started; they name the file and line at fault.

  5. Undo the most recent change

    If the problem began after an update or edit, reverse it: disable the plugin or theme, restore the previous file, or restore a backup — see Restore files or a database from a backup. For WordPress, see Fix common WordPress errors.

What you should see

The website loads normally and the error log shows no new fatal errors.

Troubleshooting and common mistakes

Only one form or admin page returns 403.
The web application firewall may be blocking that request. Note the exact URL and time and open a ticket; firewall exceptions are handled by support.
The site works for you but not for others.
Your browser may be showing a cached copy. Test in a private window and on mobile data.
The site is slow rather than down.
Check for large uncompressed images, too many plugins or disabled caching before assuming a platform problem.

When to contact FoxFolio support

Open a ticket from your account if the status page is clear, the service is active and paid, DNS is correct and the log shows no clear cause. Include the URL, the exact error, when it started and what changed. Support covers the platform; fixing your own code, themes or plugins is outside scope, but we will tell you what we can see.

Sign in to open a ticket What to include in a ticket

Sources

Adapted from the platform vendor’s website troubleshooting documentation.