Sample Nextcloud Health Check: Sample Customer

This is a sample

Sample Customer is a made-up business, and everything in this report is fictional. The issues are ones self-hosted Nextcloud servers commonly run into, so you can see exactly what our Nextcloud health check covers and what you get at the end.

πŸ“‹ At a Glance#

ItemDetail
BusinessSample Customer (fictional), a not-for-profit with 12 staff and volunteers
Nextcloud useShared files, calendars, contacts and a few online documents
ServerA cloud virtual server, set up three years ago by a volunteer
Storage380 GB used, with the disk 88% full
Review dateNovember 2026

Summary#

Nextcloud is well used and liked by the team, but the server has been left to run on its own since it was set up. It is several major versions behind and on a release that no longer gets security fixes, the disk is close to full, and backups stopped working five months ago without anyone noticing.

None of this is unusual for a server set up by a volunteer, and all of it can be fixed without the team losing any files.

🚦 Scorecard#

AreaRatingIn one line
BackupsπŸ”΄ Act nowThe backup job has failed silently for five months
Version and updatesπŸ”΄ Act nowOn a Nextcloud release that no longer gets security fixes
Disk spaceπŸ”΄ Act now88% full, growing about 8 GB a month
Security settings🟑 ImproveNo multi-factor sign-in; brute-force protection off
Sharing🟑 Improve46 public share links with no password or expiry
Performance🟑 ImproveNo memory caching; background jobs running on page load
Admin warnings🟑 Improve9 warnings on Nextcloud’s own security and setup check
Server operating system🟑 ImproveSecurity updates not applied automatically
SSL and domain🟒 GoodValid certificate, renewing automatically

πŸ” Key Findings#

1. Backups stopped five months ago πŸ”΄#

What we found: a nightly backup script exists, but it has been failing since the storage provider’s access key expired. Nobody was alerted. The last good backup is five months old.

Why it matters: if the server failed today, five months of files, calendars and contacts would be lost.

What to do: take a full backup immediately, then set up a new nightly backup to separate cloud storage (such as Wasabi), with alerts if it fails and a test restore. See storage and backups.

2. Nextcloud is out of date and unsupported πŸ”΄#

What we found: the server runs a Nextcloud release several major versions behind, which has reached end of life and no longer receives security fixes. Several apps are also out of date, and two are incompatible with current releases.

Why it matters: your organisation’s files are sitting on software that no longer gets security patches.

What to do: after a verified backup, upgrade one major version at a time (Nextcloud doesn’t support skipping versions), checking apps at each step. Replace the two incompatible apps.

3. The disk is nearly full πŸ”΄#

What we found: the disk is 88% full. Most of the space is old file versions and the trash bin, which have no limits set, plus a 60 GB folder of raw video from a past event.

Why it matters: when the disk fills up, Nextcloud stops accepting uploads and syncing can fail, sometimes mid-file.

What to do: set sensible limits for file versions and the trash bin, move the video archive to low-cost cloud storage, and add disk-space alerts. Plan a storage increase for next year.

4. Logins and sharing need tightening 🟑#

What we found: multi-factor sign-in is not enabled, brute-force protection has been switched off, and there are 46 public share links with no password or expiry date. Some point to folders containing member details.

Why it matters: a guessed password gives access to everything that person can see. Old public links can be found and shared beyond the people they were meant for.

What to do: turn on brute-force protection, roll out multi-factor sign-in (starting with admins), review the public links with the team, and set default expiry dates for new links.

5. Slower than it needs to be 🟑#

What we found: there’s no memory caching, background jobs run when people load pages rather than on a schedule, and the database hasn’t had maintenance since installation.

Why it matters: pages and syncing feel sluggish, especially when several people are working at once.

What to do: add memory caching, switch background jobs to a scheduled task, and run the database maintenance commands. Nextcloud’s admin overview will confirm each fix.

⚑ Quick Wins (This Week)#

TaskEffortWho
Full backup to separate storage, checked1 hourUs
Turn brute-force protection back on10 minutesUs
Set limits on file versions and trash20 minutesUs
Turn on automatic operating system security updates20 minutesUs

πŸ—ΊοΈ The Fix Plan#

Now (next 2 weeks)#

  • Verified full backup, then nightly backups with failure alerts
  • Disk space freed and disk alerts in place
  • Brute-force protection on, server security updates automatic

Next (2 to 6 weeks)#

  • Step-by-step upgrade to a supported Nextcloud release
  • Incompatible apps replaced
  • Memory caching, scheduled background jobs and database maintenance
  • Multi-factor sign-in rolled out and public share links reviewed

Ongoing#

  • Nextcloud and app updates every month
  • A quarterly check of backups, storage and sharing
  • A short how-to for staff and volunteers. See our Nextcloud adoption guide.

🧾 Security and Setup Checklist (Extract)#

CheckResult
HTTPS with a valid certificate🟒 Pass
Supported Nextcloud releaseπŸ”΄ Fail
Backups running and testedπŸ”΄ Fail
Brute-force protectionπŸ”΄ Off
Multi-factor sign-in available🟑 Not enabled
Public links with expiry or password🟑 46 without
Background jobs on a schedule🟑 No
Memory caching configured🟑 No
Server security updates automatic🟑 No

What Happens Next#

The report is yours to keep, whatever you decide. You can:

  • Hand it to your volunteer or IT person to work through.
  • Have us do the fixes through Cloud Experts, as a fixed price or by the hour.
  • Move to our Nextcloud hosting, so updates, backups, security and monitoring are looked after from then on.