Troubleshooting guide
Nextcloud Server Not Reachable After an Update: A Step-by-Step Diagnosis
Category: File Sync
You updated your self-hosted Nextcloud, and now the Windows desktop client says the server is unreachable even though the web interface still loads.
Confirm the failure and isolate the client
First, verify the web interface from the same Windows machine: open your Nextcloud URL in a browser. If it loads, the server is running and the problem is likely client-side or network-path-specific. Next, check the desktop client’s connection status by right-clicking its tray icon and opening Settings. Look at the account entry: a red status or repeated retry messages confirm the client cannot reach the server. Then test the exact URL the client uses. In the client settings, note the server address (for example, https://cloud.example.com). Open a Command Prompt and run: curl -I https://cloud.example.com/status.php. A 200 response means the endpoint is reachable; a timeout or SSL error points to DNS, firewall, or certificate issues.
Check the update-related causes
Updates often change TLS certificates or reverse-proxy rules. If curl returns a certificate error, compare the certificate dates and hostname with the client’s saved server address. If you use a reverse proxy, confirm it still forwards to the Nextcloud backend and that the trusted domains list includes your client’s URL. Also check that the client is not using an old address: remove and re-add the account only after noting the current URL. If the client still reports nextcloud server not reachable, restart the Nextcloud client service and retry.
Verification test
After corrections, run the curl check again, then in the client settings click the account and choose to retry the connection. A green status and a successful small-file sync confirm recovery.
Rollback note
If the update introduced the fault, restore the previous server snapshot or reverse-proxy configuration, then reapply changes one at a time. For guided diagnosis,
