Update from 30.0.4 to 30.0.5 blocked everything

good morning, forgive me I’m new to NC.
two days ago I started the update from 30.0.4 to 30.0.5.
The update continually stopped giving errors and finally it didn’t work so I closed everything.
Since yesterday I have found my page with the writing “Update in process” and the local app with the error “503 service unavailable”.
Considering that OCC is no longer usable, could you kindly help me solve the problem?
Thank you

which ones?

php and/or webserver logs are interesting for this type of error. There can be numerous reasons why this fails (e.g. no database connection, wrong permissions, …)

What is the error here?

1 Like

thanks for replying.

It started to give problems at the “create backup” point. After a few attempts it went ahead and finally stuck on “replace entry points”.

My files are intact but the NC folder contains fewer files than it should.

This is the current content of NC

Index. Public. Remote. and Static. they all contain the same code.

This is the contents of NC’s automatic backup from a week ago

I wonder if I can overwrite all the files from the backup (except my data) in the main folder?

Those smaller files are just the temporary entrypoint files put in place to keep clients from getting confused during the in-progress update.

Anyhow, can’t determine what happened for you originally (more on that in a moment), but you can do a manual upgrade to recover (which is less scary than it sounds).

As for what originally happened, see Built-in Updater: Troubleshooting.

well, it seems within my reach.
But where do I find the console?
OCC no longer works.

I’m on Aruba Linux server

If you do the manual upgrade, there is a step where you download the new zip archive which also contains the occ command.

1 Like

you have to excuse me, I’m new to NC, but I don’t understand.

OCCweb no longer works so I don’t know how or where to run the required commands.

https://docs.nextcloud.com/server/stable/admin_manual/configuration_server/occ_command.html

It sounds like the update didn’t complete properly. You might try accessing the server via command line to clear the update lock, or restore from a backup if possible.