Nextcloud 32 ends on 30 September — and you cannot just jump to 34

Nextcloud 32 falls out of maintenance on 30 September 2026 — 42 days from 19/08/2026. That is the easy part. The awkward part is that you cannot move from 32 to the current 34. Nextcloud does not allow major releases to be skipped, so it is two upgrades back to back. If you are still on 30, it is four.

The date, and what is actually fixed about it

One sentence in the project’s release schedule decides everything else: major versions appear every four months and are “supported for one year through monthly maintenance releases”. The freely available server edition has no LTS line. Every version gets its year and then stops.

The vendor keeps to that year, but not to the day. Across the twelve Nextcloud cycles patchletter holds as of 19/08/2026, the gap between release and end of maintenance runs from 362 to 415 days, averaging 380 — version 24 was the shortest, version 30 the longest. Longer support does exist, but only in the subscription: Nextcloud advertises “Up to 5-10 years of long term support” as an Enterprise feature. Without it, the year is what you have.

Why 32 to 34 is not a thing

The admin manual leaves no room. “You cannot skip major releases.” — “Before you can upgrade to the next major release, you need to upgrade to the latest point release of your current major version.” The update chapter does the arithmetic for you: “You must update one major version at a time (e.g. 28 → 29 → 30, not 28 → 30).”

So from 32 it is two passes, 33 and then 34. From 31 it is three, from 30 it is four. Each pass is a separate migration with its own database changes and its own chance to go sideways — counting four of them as one maintenance window is how a Saturday turns into a weekend.

The chain also drags the platform along. Nextcloud 32 still runs on PHP 8.1 (marked deprecated) through 8.4; Nextcloud 34 starts at 8.2 and recommends 8.5. PostgreSQL 13 is listed for 32 and gone by 34. If your host sits on either, the runtime upgrade belongs before the chain — not between step two and step three with maintenance mode already on.

The point release you have to wait for

The rule that every major upgrade starts from the latest point release of your current major version has an uncomfortable consequence: the end date is in your calendar, the thing you need before it is not. As of 19/08/2026 the 32 line stands at 32.0.14, published 13/08/2026, and the schedule lists 32.0.15 for 10/09/2026. Whether that is the last one, nobody says in advance — version 24 finished at 24.0.12, version 30 ran to 30.0.17. Where a line stops is only visible afterwards. The deadline is predictable, the release you need before it is not.

What one step looks like

The documented path, repeated once per major version. Paths depend on your installation; the manual uses /var/www/nextcloud.

• Take a backup — the manual is blunt: “You should always maintain regular backups and make a fresh backup before every upgrade.”
• sudo -E -u www-data php /var/www/nextcloud/updater/updater.phar — the updater switches maintenance mode on itself, you do not do that beforehand
• sudo -u www-data php ./occ upgrade
• Let the database catch up: occ db:add-missing-columns, occ db:add-missing-indices, occ db:add-missing-primary-keys

Then start over — the updater only ever offers the next major version. Hence the manual: “Please re-run the upgrade until you have reached the highest available (or applicable) release.”

The honest limitation

Nextcloud publishes the month, not the day — the schedule says 2026-09 for version 32. The 30 September here comes from endoflife.date, which resolves the month to its last day: good enough to plan against, not confirmed by the vendor in that precision. And end of maintenance is not a shutdown. On 1 October nothing stops, the instance keeps serving files, monitoring stays green. What ends are the security fixes — which is why the date matters and why nothing will announce it.

Where the calendar stops helping

You can write 30 September into a calendar today. You cannot write in when 32.0.15 lands, or whether a 32.0.16 follows — and that release is the gate to the first of your two upgrades. That half of the problem needs a notification, not a reminder, which is what patchletter does with Nextcloud: tick it on the Nextcloud product page and an email goes out the day a new version ships, instead of you finding out the next time you happen to check. The recorded support cycles, the ones above included, sit on the end-of-life overview. Free, no account, one-click unsubscribe.

Cycle data and version states from our own dataset as of 19/08/2026: twelve recorded Nextcloud cycles, newest recorded version 34.0.3 of 13/08/2026. Dates, quotations and requirements from the Nextcloud release schedule wiki, the admin manual (upgrade, update, system requirements 32 and 34), endoflife.date and nextcloud.com/enterprise, all retrieved on 19/08/2026.