Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Sites in maintenance
Computers, terminal and Git

Sites in maintenance

Understand the maintenance page on an old file-published address, and put a running application behind it again.

What maintenance means

Sites that were published from files keep their addresses, certificates and saved files. After the upgrade they no longer serve those files.

Instead, their addresses return a temporary maintenance response, and the Sites list and the Site details show Maintenance. Administrators receive a warning. The retained files are read-only, no static server is installed, and nothing is copied automatically.

Note: Deleting the Site explicitly removes the retained files. It never removes the Project application or its source.

Restore an address

  1. Select the managed Project or paired computer that runs the replacement service, start its HTTP service there and note the port it listens on.
  2. In a conversation, choose that Project in the Project picker beside the conversation title, so Chetty works in it.
  3. Ask Chetty to publish the Site: SitePublish with the Site's slug or id and that port.
  4. Wait for the verification to pass. The address leaves maintenance only after the replacement service answers.

SitePublish takes the replacement Project from the conversation it runs in, so the request names only the Site and the port. Use SiteUpdate if the Site's title, summary or visibility also needs a change.

What happens during a restore

A restore runs one attempt at a time. Starting a new attempt cancels the earlier one, and an attempt that does not finish within five minutes expires.

Until the replacement service passes verification, the address and its retained files stay in maintenance. A failed attempt changes nothing and can be repeated.