Upgrading old revision

ℹ️ Support
,
1
Support intro

The Basics

  • Nextcloud Server version (e.g., 29.x.x)
  • 20.0.1
  • Operating system and version (e.g., Ubuntu 24.04):
    • webhost OVH
  • Web server and version (e.g, Apache 2.4.25):
    • inconnue
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • inconnue
  • PHP version (e.g, 8.3):
    • 7.4
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • replace me
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • inconnue
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

Hello, I’ve just taken over the management of a Nextcloud instance hosted on an OVH web server. It’s a very old version (20.0.1). I’ve already managed to complete a few steps (managing PHP versions, setting the secret for updates, etc.).

I know I’ll have to take it step by step (updating Nextcloud, then PHP, then Nextcloud again, and so on).

But I’m stuck at the very first step.

The overview page says I can update to 20.0.4.

But the updater tells me the version is up to date

Current version is 20.0.1.
No update available.

Just to remind you, there’s no SSH access on this web host. I’d like to avoid having to reinstall manually (via FTP). Is there a way to enable the updates?

2

Hej,

I am very curious about this topic, because it’s almost the same situation here:

I took over a NC 15 and of couse need to upgrade. Since I have ssh-access, my situtation is a bit differentnt, but a solution to Didierdrums issue should help me as well! So I thank in advance for helpful answers!
Regards,

Boris

3

I switch to “Beta”, clean old backup, remove the .step file, and update is now OK

4

Hej Didierdrum,
thanks for explaining. May I ask back: Have you been able to switch back to ‘stable’ after doing like you wrote?

Thanks,

Boris

5

Not yet, I am still in the upgrading process (the upgrade is incrmental, you can not jump from 20 to 33, you you to go through all the intermediate revision)

I have no doubt tha I can swith back to stable when I will reach rev 30 .

I supose that for old revision, without available maintenance, you need to keep beta channel.

6

Thank you. I thought I was reading that the switch back is not possible. I am curious about your experience!

7

You can go from beta to stable without issue*, but you will be running the beta version until a version on stable is >= the version of Beta you are using. For instance, if the latest stable version of server is 33.0.2, but a beta is released (for instance, 33.0.3rc1) and you update to that version, changing your channel to Stable will mean you are stuck on 33.0.3rc1 until 33.0.3 releases to stable, even if another beta (ie, 33.0.3rc2) releases in the meantime.

*Normal update-related issues notwithstanding.

8

I reach rev 31stable, but lost the css in the process. I will check on internet if there is a solution to correct.

9

Well, finally I used my advantage to have possibility to connect with ssh to ‘my’ server. Updates were possible to do without switching to beta. I came from 15.0 and reached 23.0.12, doing step-by-step upgrades with some maintenace in between, adding db-missing-indices and so….

I am optimistic to run forward to up-to-date version.
Did I mention I find NC to be a top-of-the-pops piece of software?

10

I add the app theming that destroyed the css. Remove it, by css still missing. NC unusable without css! Il will check if I can solve this point.