> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.faaaster.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# 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.

## 1. Check the site's status

| Status | What it means | What to do |
| --- | --- | --- |
| **Starting up…** | The infrastructure is getting ready. | Wait a few minutes. |
| **Paused** | The server is stopped — on the Dev plan, after 5 days without activity. | Restart the site with the **Restart** button on its screen. |
| **Online** but site not working | The server is responding; the problem is in WordPress. | See below. |
| **down** | The server is running, but our monitoring can't reach the site. | See below. |
| **Error** | The site isn't responding correctly. | Check the logs. |

## 2. The site is "Online" but doesn't display

- Open the **Logs** tab and filter on **Errors**.
- Check the **PHP errors** counter in the **Overview**.
- If the problem follows a plugin update, **restore a backup** from the **Backups** tab.

## 3. The site is in private mode

If the **Private** toggle in the header is on, the site isn't publicly accessible: that's intentional, and the **Preview and collaboration link** is the way in to share.

## 4. Restart

The header's **Actions** menu lets you restart the processes (**Restart PHP / Nginx**) or the server (**Restart server**). It's the move to try when nothing else explains the outage.

## 5. Find the cause in the log

When Faaaster stops a site on its own, the reason appears in the site's **Events** tab: in the details of the **Site stopped** event, or in the alert that preceded it:

| What the log shows | What to do |
| --- | --- |
| **Unpaid invoice**, then **Site paused** | Pay the invoice from **Account** → **Billing**. The site then starts again. |
| **Subscription cancelled** | Subscribe again from the site's **Subscription** tab. |
| **Trial ended** | Subscribe to a paid plan. |
| **Branch archived** | Opening the environment in Faaaster postpones its archiving. If it's already archived, reactivate it from the **Trash** tab in **Environments**. |
| **Payment method missing** | Save a card in **Account settings**. |

> **Start there.** A "down" site is far more often a site paused for an administrative reason than a technical outage — and the log tells you so in one line.

👉 [What do a site's statuses mean?](https://help.faaaster.io/en-us/article/understand-site-statuses-110l09n/) · [How do I view the event log?](https://help.faaaster.io/en-us/article/event-log-192p146/)