Troubleshooting guide
Nextcloud Sync Error 503 After an Update: When the Desktop Client Can't Reach the Server
Category: File Sync
You updated your self-hosted Nextcloud server, and now the Windows desktop client reports the server is unreachable even though the web interface still loads.
Confirm the Failure Scope
First, separate client from server. On the Windows machine, open a browser and load your Nextcloud URL. If the login page appears, the web tier is up. Next, open Command Prompt and run curl -I https://your-nextcloud-domain/status.php. A 200 OK with JSON means the server is healthy; a 503 confirms the service is genuinely unavailable to clients. If the browser works but curl returns 503, the web server is likely serving a cached or static page while the PHP backend is down.
Check the Update Leftovers
On the server, verify the Nextcloud service and PHP-FPM are running: systemctl status nginx php8.2-fpm (adjust the PHP version). A stopped PHP-FPM pool returns 503 to the desktop client while static pages may still load. Also check occ status from the Nextcloud directory; if it reports maintenance mode, run occ maintenance:mode --off. Review the web server error log for upstream timed out or connect() failed entries, which point to a backend that did not restart after the update.
Verification Test
Restart PHP-FPM and your web server, then rerun curl -I https://your-nextcloud-domain/status.php. A 200 response means the backend is reachable. In the desktop client, pause and resume sync; the red error should clear. If the client still logs a nextcloud sync error 503, the server is returning it, not the network.
Rollback Note
If the update corrupted the backend, restore the previous Nextcloud version and database snapshot before retrying. Keep maintenance mode on during rollback to prevent partial syncs.
If these checks do not isolate the cause,

Ask for help with your logs and update version.