• My Faaaster site is down — what should I do?

  Open the site from your Projects and look at the status shown in the header at the top: it almost always tells you the cause. A site that is paused, starting up or in error isn't handled the same way.Few readers

• My Faaaster site is slow — how do I diagnose it?

  Open the site's Monitoring tab: the Latest resource measurements show whether the site is maxing out its memory or CPU, and the graphs show whether the slowness is recent or long-standing. The Performance tab then lets you check the cache.Few readers

• My Faaaster site shows a blank page or a 500 error

  A blank page or a 500 error almost always signals a fatal PHP error. Open the site's Logs tab and filter on Errors: the message will point you to the file or plugin at fault.Few readers

• My WordPress site is stuck on "Briefly unavailable for scheduled maintenance"

  This message means WordPress got stuck in maintenance mode after an interrupted update. All you need to do is delete the .maintenance file at the site root to unblock it.Few readers

• My Faaaster site shows as "not secure"

  First check the certificate status in the site's Domains tab, HTTPS column. If it's active but the browser reports a problem, the most frequent cause is mixed content: resources still loaded over http:// on a site served over https://.Few readers

• My Faaaster site has been hacked — what should I do?

  Act in this order: isolate the site, restore a backup from before the compromise, then fix the vulnerability before putting it back online. Restoring without fixing the vulnerability means getting compromised again.Few readers

• I'm not receiving emails from my Faaaster site

  Start by identifying which emails are involved: those sent by your WordPress site, those from a Faaaster mailbox, or those sent by Faaaster itself. The three don't have the same cause or the same fix.Few readers

• I can't log in to Faaaster

  First check which access is involved: your Faaaster account or your site's WordPress admin. The two are separate and aren't troubleshot the same way.Few readers