# Version confusion (AIO vs. admin page vs. scanner vs. "season")

**URL:** <https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014>\
**Category:** ℹ️ Support\
**Tags:** nc32, nc34, aio, security\_scanner\
**Created:** [October 15, 2026, 6:45am UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014 "2026-10-15T06:45:36Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kugeleis](https://help.nextcloud.com/user_avatar/help.nextcloud.com/kugeleis/32/8171_2.png) [@Kugeleis](https://help.nextcloud.com/u/Kugeleis)\
**Post date:** [October 15, 2026, 6:45am UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014/1 "2026-10-15T06:45:36Z")

</div>

Different pages show different versions. Also the overall wording is not helpful. My AIO docker installation shows

- Nextcloud Hub 26 Spring (35.0.1) on the admin page

The AIO interface then says

- Nextcloud AIO v14.3.0

- … and it offers the button **Upgrade to Nextcloud Hub 26 Summer** ; if I klick it I get:

On [https://scan.nextcloud.com](https://scan.nextcloud.com) I get:

> Running **Nextcloud 32.0.3.2**  
> **NOT** on latest patch level  
> Major version still supported  
> Scanned at 2026-01-12 13:29:39

This is all very confusing. I guess I am on **Spring** , see the offer to update to **Summer** but the same interface then says I’m up to date?!?! And finally the scanner page reports even something completely different.

So we have the AIO version, we have the semantic version x.y.z and we have a **cloudy** season name. And all this disagrees with the scanner.

Is there a PhD I have to have to understand this ;~]

---

<div class="post-metadata">

**Author:** ![scubamuc](https://help.nextcloud.com/user_avatar/help.nextcloud.com/scubamuc/32/63165_2.png) [@scubamuc](https://help.nextcloud.com/u/scubamuc)\
**Post date:** [October 15, 2026, 6:48am UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014/2 "2026-10-15T06:48:08Z")

</div>

@Kugeleis welcome back 👋

try trigger a rescan on [https://scan.nextcloud.com](https://scan.nextcloud.com)

 ![grafik](https://help.nextcloud.com/uploads/default/original/3X/1/5/15ffa631289a62871d0a69b463e809b84d1ea154.png)

---

<div class="post-metadata">

**Author:** ![tflidd](https://help.nextcloud.com/letter_avatar/tflidd/32/6_22734026db12803ebb3e059622ac3534.png) [@tflidd](https://help.nextcloud.com/u/tflidd)\
**Post date:** [October 15, 2026, 10:49am UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014/3 "2026-10-15T10:49:35Z")

</div>

> [@Kugeleis](#):
>
> - 35.0.1

This version number is the most important that tells you which will be the next version to upgrade (NC 36), and which patch-level you have.  
And here you can check the currently supported versions:

> **[Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule)**
>
> ☁️ Nextcloud server, a safe home for all your data - nextcloud/server

For major upgrades, the AIO image might take a bit of time before it is available.

---

<div class="post-metadata">

**Author:** ![Rei\_Kurosawa](https://help.nextcloud.com/letter_avatar/rei_kurosawa/32/6_22734026db12803ebb3e059622ac3534.png) [@Rei\_Kurosawa](https://help.nextcloud.com/u/Rei_Kurosawa)\
**Post date:** [October 15, 2026, 2:58pm UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014/4 "2026-10-15T14:58:52Z")

</div>

The three version strings you found are three different things, and only one of them describes your server:

**35.0.1** is your actual Nextcloud server version - as tflidd said, this is the authoritative number. The official Maintenance and [Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) maps the season names to the numbers: 33 = Hub 26 Winter, 34 = Hub 26 Spring, 35 = Hub 26 Summer. So your server already runs “Hub 26 Summer”, which is why the “Upgrade to Hub 26 Summer” button correctly reports “No update available”. The “Spring” label your admin page shows next to 35.0.1 does not match the official mapping; I can’t say why the UI displays that, but the number wins over the label.

**Nextcloud AIO v14.3.0** is the version of the AIO management tooling itself, not of the Nextcloud server. AIO has its own release line (v14.3.0 was published on October 8) and updates independently of server releases.

**[scan.nextcloud.com](http://scan.nextcloud.com) showing 32.0.3.2**: note the “Scanned at 2026-01-12” line in your quote - that result is over nine months old, from when your server actually ran 32. scubamuc’s rescan advice is the fix here; after a fresh scan it should report 35.0.1.

On top of that, 35.0.2 was released today (see the News section). With AIO, server updates appear once the AIO channel ships them, so a short delay between the upstream release and the update offer is normal.

(AI-assisted translation/polish)

---

<div class="post-metadata">

**Author:** ![Michaelmonney](https://help.nextcloud.com/letter_avatar/michaelmonney/32/6_22734026db12803ebb3e059622ac3534.png) [@Michaelmonney](https://help.nextcloud.com/u/Michaelmonney)\
**Post date:** [October 16, 2026, 3:05pm UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014/5 "2026-10-16T15:05:14Z")

</div>

I agree and I have already also written this elsewhere: Nextcloud should simplifiy it’s version and naming scheme, as well as streamline the AIO update, and versions number.

---

<div class="post-metadata">

**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/6_22734026db12803ebb3e059622ac3534.png) [@bb77](https://help.nextcloud.com/u/bb77)\
**Post date:** [October 16, 2026, 4:35pm UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014/6 "2026-10-16T16:35:09Z")

</div>

I agree with that as well, at least in part. This whole thing with the Hub versions and the “Seasons” only confuses people. However, I do understand that AIO and Nextcloud have different version numbers, since AIO also updates other components, such as dependencies like PHP and the database, or itself independently of Nextcloud updates. Therefore, AIO’s versioning can’t simply be tied to Nextcloud’s versioning.

Also, the thing with the security scanner is just a reading comprehension issue. It says right next to the “Retrigger Scan” button when the last scan was performed. Unless I’d retriggered a scan at least five times and still gotten an incorrect result, I wouldn’t even post here in the first place. 😉

So Id’ say OP has probably already figured everything out by the time they made their post, because I don’t see any question marks in that post. So, as far as I see it, this is more of a rant or an opinion post than an actual support request. 😉

---

<div class="post-metadata">

**Author:** ![YurkshireLad](https://help.nextcloud.com/letter_avatar/yurkshirelad/32/6_22734026db12803ebb3e059622ac3534.png) [@YurkshireLad](https://help.nextcloud.com/u/YurkshireLad)\
**Post date:** [October 16, 2026, 6:41pm UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014/7 "2026-10-16T18:41:36Z")

</div>

Yeah, it’s incredibly confusing. It’s even more confusing when the mobile app tells me there’s a new version 35.0.x available (sorry, forget the actual value), but updating the AIO master container only updates it to 34.0.4. I have no idea what’s going on.

---

<div class="post-metadata">

**Author:** ![Michaelmonney](https://help.nextcloud.com/letter_avatar/michaelmonney/32/6_22734026db12803ebb3e059622ac3534.png) [@Michaelmonney](https://help.nextcloud.com/u/Michaelmonney)\
**Post date:** [October 19, 2026, 5:26am UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014/8 "2026-10-19T05:26:31Z")

</div>

Sorry I wrote a bit too fast to be clear 🙂  
I meant this:  
That AIO and Nextcloud itself has different version scheme is not an issue if it’s comunicated clearly. It can, as you (@bb77 ) say, even be better.  
The problem is: AIO is the preferred installation method communicated by Nextcloud marketing (it seems to me), but it is always a bit late compared to Nextloud versions. So we get e-mail, social network, admin page notification of updates, that are in fact not yet available through AIO’s containers updates.

Also, now I would like to update to the latest 34.0.X version, but AIO mastercontainer doesnt do so. It would let me update to NC35, though, which is not what I want. There’s probably a way (with CLI I guess) and I haven’t had the time yet to look it up, and in any case I find all this unclear.

Maybe few buttons in AIO’s interface that would say:

- Update to 34.0.X (latest Spring version)
- Update to 35 (newset Summer version)  
?

---

<div class="post-metadata">

**Author:** ![JimmyKater](https://help.nextcloud.com/user_avatar/help.nextcloud.com/jimmykater/32/4850_2.png) [@JimmyKater](https://help.nextcloud.com/u/JimmyKater)\
**Post date:** [October 19, 2026, 7:52am UTC](https://help.nextcloud.com/t/version-confusion-aio-vs-admin-page-vs-scanner-vs-season/251014/9 "2026-10-19T07:52:17Z")

</div>

I reallly don’t know which problems some of you guys do have here…

season, Hub, etc… was talked about back and forth already when the “new” season-naming came across… roundabout 1 year ago. pls do some research here on the forum about your inquiries before posting.

same with AIO. It was clearly communicated, several times and even the AIO-page itself tells it directly, AIO prefers stability over new versions.  
this means: it usually will take at least 2 minor versions (Vxx.0.2) before it’ll be upgraded to a new major version. sometimes it’ll even take a bit longer. if you don’t like it you can always chose “upgrade now” from the AIO-page when a new version is out. Even now. Try it (careful, downgrading isn’t supported). again: everything clearly and directly communicated. At the AIO-page itself.

for me, personally, I only care about the Serverversion itself… Like NC V35.0.2 or V34.0.7 etc.
