Logs and deployment controls

Your project workspace shows the website’s status, deployment stages, and logs. Stopping, restarting, and rolling back are owner actions.

Reading logs

1. 1

   Open the deployment log

   In “Deploy”, open the deployment log after a deployment attempt exists. Check its source: runtime output when available, otherwise the build log or an early failure message.

2. 2

   Wait for updates or refresh

   While displayed during preparation and build, this log refreshes about every 5 seconds. Click “Refresh” for the latest output. “No log yet” does not mean deployment succeeded.

3. 3

   Follow runtime output in “Log”

   Open “Log”, using “+” if needed. It reads the same deployment logs and refreshes about every 10 seconds while open. If loading fails, wait briefly and click “Refresh”.

4. 4

   Check preview output in “Terminal”

   Open “Terminal” from “+” to read the preview server log. It refreshes about every 3 seconds. This is a read-only view and does not run commands you type.

Stopping and restarting the website

1. 1

   Open the deployment status

   Wait for any active deployment to finish. In “Deploy”, click “Stop deployment” for a running website. Visitors lose access to it; project data and the database are retained.

2. 2

   Wait for the stopped status

   Wait for the request to finish and the status to change. Review the stop reason and hosting coverage. On an error, reload the status before trying again.

3. 3

   Restart

   Click “Restart” when you want the website available again. Wait for the request to finish and open the link. If it was stopped because of your balance or a deletion request, address the displayed reason first.

Returning to an earlier deployment

1. 1

   Choose a previous version

   Open “Deploy”, then version history. Review the date and status. Eligible earlier successful deployments show a rollback button.

2. 2

   Start the rollback

   Click the rollback button for that version. It starts immediately. Wait for the result and follow the status; do not start another rollback while it runs.

3. 3

   Verify the website

   Open the link after rollback succeeds. If the message says rollback did not complete and the previous live version was kept, review the log. On a connection error, retry the same action as directed.