[SOLVED] Error while updating

Dumb question: Is there actually enough space to create a full backup including zip download before? Or to the developers: Would there be a meaningful error response if this was the case?

You can still do it manually:

  1. Maintenance mode
  2. Move content of nextcloud folder to backup location.
  3. Download newest server release: https://download.nextcloud.com/server/releases/nextcloud-11.0.3.zip
  4. Extract it to old nextcloud location.
  5. Copy config.php, potentially changes to .htaccess, themes and 3rd party apps back from backup. Or better install 3rd party apps fresh from app store, if no manual changes to some info.xml was made.
  6. Move data folder back in place, if it was actually inside nextcloud folder.
  7. Disable maintenance mode again and try.
1 Like

Hi ! Thanks for the manual instructions !

Indeed, since the 11.0.2 ->11.0.3 upgrade, I always get a timeout when the backup is being made. (hosted server). Even on a clean NC instance.

I wonder what changed meanwhile. Probably server related !

Hmm, I get a blank page after manually upgrading (and retaining the config and data files).

Actually, I’m stuck at the moment, because I use shared hosting.

What settings should I modify to use the updater app with a greater timeout value (or to be able to skip the backup step, which is where the timeout actually occurs) ?

I used to be able to upgrade with the updater app.

Thanks a lot :slight_smile:

Hmm, I re-tried the updater app several times in a row and it eventually succeeded :slight_smile:

I finally solved the issue, and managed to update to 11.0.4.

When I tried it, I still got the same error at stage 4. Even while using the try again button, I got stuck.

I then went to the config.php file changed the line maintenance = "true" to “false”, without reverting anything else, and next time I went to the update page, I clicked on the “try again” button, and it went through.

Hope it can help someone one day.

1 Like

Hi ! I still get this issue when updating. I know how to revert it, but it almost always timeouts at the “create backup” step. Any idea on how to improve the situation ? That’s probably due to a slow server ? Is it possible to skip the create backup step ?

I got this now on each of latest three minor updates of Nextcloud 12.0.x, and retrying (after changing maintenance mode by editing config.php) eventually succeeds.

As it seem to hit several users, i think it would be a good if this problem got further checked. Some progress indication or logging may help debugging it.

There are some reports on failing automatic backups (especially in hosted environments):


Feel free to open a feature request in the same repository to omit the backup step. Or for another report with more details to help to tackle this problem.

This topic here is solved, so we will close the discussion. Please open new topics for new problems.