From 384aa30da988190b9368515ed525a700447bc2d8 Mon Sep 17 00:00:00 2001 From: whoalin1 Date: Wed, 7 Oct 2026 05:02:45 +0300 Subject: [PATCH] docs(admin): document HTTP 503 to simulate maintenance for clients Assisted-by: Cursor:grok-4.7 Signed-off-by: whoalin1 --- admin_manual/maintenance/index.rst | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/admin_manual/maintenance/index.rst b/admin_manual/maintenance/index.rst index ac018dc6809..083b5f8002a 100644 --- a/admin_manual/maintenance/index.rst +++ b/admin_manual/maintenance/index.rst @@ -13,3 +13,22 @@ Maintenance package_upgrade migrating migrating_owncloud + + +Simulating maintenance mode for clients +--------------------------------------- + +When Nextcloud is fully stopped or taken offline for infrastructure work, it can +no longer serve its normal status payload that tells desktop and mobile clients +the instance is in maintenance mode. + +In that situation, configure the reverse proxy or load balancer to answer +client-facing Nextcloud endpoints with **HTTP 503 Service Unavailable**. Clients +treat a 503 the same way as Nextcloud's built-in maintenance mode and will back +off instead of surfacing hard sync errors. + +Examples of endpoints clients hit include ``status.php``, ``index.php``, and +WebDAV / OCS URLs under your Nextcloud base path. + +For application-level maintenance while PHP is still running, prefer +``occ maintenance:mode --on`` (see :doc:`../configuration_server/config_sample_php_parameters`).