Web Update is a nightmare - shared hosting

I’ve been using NextCloud for a couple of years on my shared webspace. Its not the ideal enviroment for NextCloud, but I pay for it anyway and its a way to get more independent from big tech companies. Until I have to update.

NextCloud runs in the server and is accessible from anywhere, which is good. But it also means, I have to keep it up to date, to not make it a security risk. But that has proven to be a nightmare for a long time.

Basically, the web updater always fails to verify the archive. I’m not sure why, could be a limitation of my shared webspace, which I can’t fix. I don’t have system access, so I can’t even check. I always have to manipulate the updater to skip the verification step. I’ve done this for years.

Recently, thats not enough. I always have to generate and provied the updater secret - not to mix up with the other “secret” in the config file, which I did in the past, putting my installation in an infinite update loop. Sometimes it helps just stupidly running the updater again and again, and at somepoint, it will work. At least, it did in the past.

But that is just an nightmare to do. Not enough that I don’t get any notification despite signing up for it, always have to check manually and then start the process manually. Couldn’t there be at least the option to have it update automatically? Plus all the additional, manual steps I have to do to get it actually to update. Its really annyoing, time consuming and overall frustrating to do. So much, that I think about switching back to one of the commercial, closed off cloud storage provider. Just to get that hassle out of my way.

I’m certainly not the only one, I’ve found tons of threads complainig about failed updates with hacky solutions to them. Its really a problem and I don’t see it getting any better. Having smooth, painless update is a needed features these days, and I don’t understand why NextCloud hasn’t to a point anywhere near it. Is there anything I can do? Or just hope and pray the devs will allocate some time to it at some day?

Well first off, it’s not really fair to blame the software when you don’t even have root access to the system that’s failing to update. Personally I don’t see why anyone would want to host Nextcloud on a system they don’t even have admin access to. Seems like that’s asking for something to go wrong.

I’ve been running Nextcloud since version 16 and have never had it break on an update. But, I’m not using the same procedure you are because I run it in Docker. Docker updates are easy, and many of the usual variables are no longer variables because docker images include a known working set of libraries.

Maybe you could consider changing to a VPS where you at least have root access. You could keep with the manual install if you wanted, but you’d have the option of running docker or AIO methods too.


If you want to get independant from big tech companies you should switch to a VPS and use Linux to host your Nextcloud. The Updater works fine except if you have more than 100 users. It then tells you to use the command line which is also an easy task.

BTW - Nextcloud will never update automatically because of third party apps.

If you want to have absolute security with testing for working apps before an update you will have to pay for an enterprise license - which we use for one of our instances. Enterprise version is always 2-3 subversions behind community edition (currently 24.0.7 enterprise but 25.0.1 community) but it’s tested to the limit and has enterprise support which will take care of all problems that may occur.

1 Like

apart from all the other right things the previous commenters have already mentioned you should note:

NC isn’t really made to run on shared hosting.

So of course you chose that service because it’s somewhat cheaper. But is it really cheaper? I mean you noticed yourself, already, your solution comes with more work (meaning: time) you need to invest. So it’s up to you to decide how to spend your money… investing it in your sparetime and trying to get in running on a cheap hosting service? or maybe investing your bucks in a more reliable way to host your instance, maybe on a VPS, or whatever to just enjoy your sparetime for things you like to do?

And no this doesn’t mark any resonsibility of NC, since it’s your very own responsibility. You alone decide where and how to host your instance.

Plus, and just let’s keep that in mind, you are using NC for free. Absoultely. F-R-E-E.

However, it is somehow supported. Problem is that these environments are different and hard to compare.

Well, it’s good practice to verify downloads, so just disabling it can’t be a solution for everybody. If you put an option to ignore this step, that is dangerous because if there is someone injecting a wrong update, this way it will be very likely that people just click on it and ignore the warning.
Perhaps just some missing packages or something that you could report to your ISP?


my shared webspace.

Check with your provider from time to time if they updated their offerings. Occasionally, you get more features and better performance for the same price.

Basically, the web updater always fails to verify the archive. I’m not sure why, could be a limitation of my shared webspace, which I can’t fix. I don’t have system access, so I can’t even check. I always have to manipulate the updater to skip the verification step. I’ve done this for years.

The verification process needs a lot of memory. If your shared webhosting does has a low memory_limit it will fail.

Recommendation 1: When you have access via SSH, use the CLI updater.

Recommendation 2: If you cannot use the CLI updater: use the manual update process: Upgrade manually — Nextcloud latest Administration Manual latest documentation (some points like stopping the web server are not possible, but it should more or less work).

Don’t you please open a backdoor to community-support :thinking:

As you already said: environments are pretty diverse and thus it could happen that NC works on one and won’t work on the next one. In no case that means any guarantee for any kind of support.

So i consider it fair if NC says “not made for shared hosting”. Which means you’re all on yourself first and foremost. And you can’t blame anyone else for problems that arise from your decision to host your instance on a shared hoster.

1 Like

I fully agree with Jimmy here. I would go even further, and say, that Nextcloud should have more clear and higher system requirements. Sure you can run Nextcloud on a Raspi 2 with 512MB Ram or on a €1.99 webhosting plan, until you want to run Talk or Office on the former or something goes wrong and you need to run an OCC command on the latter. Or maybe you need a PHP module for a certain app or function that the hosting provider doesn’t provide etc. etc…

People usually mean the full Nextcloud HUB package when they say Nextcloud. And for that to work reasonably with multiple users you need at least 2 cores and 4GB RAM and SSH access to run OCC commands. Anything less will result in a bad experience and users will think the product is bad, when actually their environment / HW is too weak.


We are on a shared hosting and it works really well. We are running both Talk and Office. Onlyoffice is installed on a separate local server. We have SSH access, 12 core, 32GB ram and can change php memory limits etc.

Even if Nextcloud is running smoothly there are often minor upgrade issues that has to be solved.

Yes, but to some extent, I would consider that as normal. Ask Exchange or Share Point admins if they can upgrade their servers with one click, and if there never are any unexpected issues… We are talking about a relatively complex server environment here and not about some weather app on a cell phone :wink: