That is indeed a great point. I did have some issues in the past though, because I simply use "linuxserver/nextcloud" -> latest. Potentially not the greatest idea on my side. Before the updater.phar change it did not bother me too much, because I could simply upgrade myself. Now I can't see directly when the new major will be applied if I update my container.

F.e. with postgres, I simply use "postgres:16" for the latest minor release in current major and don't worry about it.

 

If I check the NC tags, I can see "29.0.7 as well as "30.0.0". (I don't know though what the additional tags like "29.0.7-previous" do)

Is there a best practice like using explicit tags like "linuxserver/nextcloud:29.0.7" instead of "linuxserver/nextcloud" and only changing to "linuxserver/nextcloud:30.0.1" (or as you mentioned .3) when they are available?

 

How do you (in the sense of everybody else) handle your NC upgrades?

 

The official container has e.g. "29" and "30" tags so if you choose that it'll update within the major release but not jump to the next major without you changing it. Unfortunately LSIO don't do that.

1 hour ago, dreadu said:

That is indeed a great point. I did have some issues in the past though, because I simply use "linuxserver/nextcloud" -> latest. Potentially not the greatest idea on my side. Before the updater.phar change it did not bother me too much, because I could simply upgrade myself. Now I can't see directly when the new major will be applied if I update my container.

F.e. with postgres, I simply use "postgres:16" for the latest minor release in current major and don't worry about it.

 

If I check the NC tags, I can see "29.0.7 as well as "30.0.0". (I don't know though what the additional tags like "29.0.7-previous" do)

Is there a best practice like using explicit tags like "linuxserver/nextcloud:29.0.7" instead of "linuxserver/nextcloud" and only changing to "linuxserver/nextcloud:30.0.1" (or as you mentioned .3) when they are available?

 

How do you (in the sense of everybody else) handle your NC upgrades?

 

I use a specific version  in my container config. For example, I'm on nextcloud:27.1.4-ls289 right now and I'll be going to 28 next week(probably previous-28.0.10-ls12). I've read that it's a good practice to use a specific tag for stability otherwise, you might wake up one morning with a borked system. For less important stuff, like Plex, I just use the general tag to keep on the latest.

 

Before I upgrade, I usually go to the last version of the current release(in this case, 27.1.4-ls289), then go to the next major release. Don't skip major releases(27->28 is OK, 27->29 no bueno).

 

I'm also going with an n-2 strategy, again for stability.

6 hours ago, dreadu said:

That is indeed a great point. I did have some issues in the past though, because I simply use "linuxserver/nextcloud" -> latest. Potentially not the greatest idea on my side. Before the updater.phar change it did not bother me too much, because I could simply upgrade myself. Now I can't see directly when the new major will be applied if I update my container.

F.e. with postgres, I simply use "postgres:16" for the latest minor release in current major and don't worry about it.

 

If I check the NC tags, I can see "29.0.7 as well as "30.0.0". (I don't know though what the additional tags like "29.0.7-previous" do)

Is there a best practice like using explicit tags like "linuxserver/nextcloud:29.0.7" instead of "linuxserver/nextcloud" and only changing to "linuxserver/nextcloud:30.0.1" (or as you mentioned .3) when they are available?

 

How do you (in the sense of everybody else) handle your NC upgrades?

 

Like this.....

 

1. Go to linuxserver.io 

2. Find the tag of the version you want, ie.

 

 

3. Open your Nextcloud docker and copy / paste the tag onto the end of lscr.io/linuxserver/(paste here)

 

 

Proceed to update. Make sure you backup your appdata first. If the upgrade fails or has too many errors, it will save you time to roll back than deal with the issues. Make sure its your NC and Database folder that are backed up properly. If NC won't upgrade, but the database has, as part of the upgrade. You ideally should roll back both.

As a minimum, if you're jumping to new main versions, I would do at least the middle and last upgrade before jumping. ie. v. 28 to 30. I would be doing 28.03, 28.05, 28.09 then go to v29 up until its latest version before jumping to the v.30 stable version available.

 

Hope that helps.

As far as I know, it is not a mistake to enter the full tag, you could also use

lscr.io/linuxserver/nextcloud:29 ----> Upgrades every time there is an new subversion of the image like 29.0.1 or 29.1.2 and so on

lscr.io/linuxserver/nextcloud:29.0.7 ----> this only updates the docker image to the latest 29.0.7 branch like 29.0.7-ls340 or 29.0.7-ls343 and so on

Hi,

can someone please help me with my lsio nextcloud container? I think after a recent update(s?) I get internal server error 500, and can't login to nextcloud (my mobile app seems to stay connected to the nextcloud server, I can browse but can't upload files). I'm trying various things now for 3 days to fix it:

 

I have configs and logs:

config.php

/mnt/user/nextcloud/nextcloud.log

pw: MbtNuJXPWK

 

/mnt/user/appdata/swag/log/nginx/access.log <-- nothing, only tokens

/mnt/user/appdata/nextcloud/log/nginx/error.log <-- this is empty

nothing suspicious in redis and in mariadb logs

 

I tried the following things so far:

- force reinstall nextcloud docker

- reinstalling nextcloud with specific version tags (by the way the linuxserver dockers are updating and installing extremely slowly for me)

- using sample swag subdomain config for nextcloud

- trying out two differently setup cloudflared tunnel (locally managed "cloudflared" container and the newer one guided by Spaceinvader One, where the public host names are set up on the web ui of cloudflare: "Unraid-Cloudflared-Tunnel").

At the moment the latter one is active and recorded some logs on cloudflare web ui (clicked on Connector details, and started a log stream). Here I only see the Internal server error 500

- removed all of the swag mods from booting and from the conf files

- I don't want to open a port on my router, so I haven't checked what happens if I turn off the proxy on cloudflare and put my real IP in DNS settings

 

I'm really frustrated, because I didn't change anything on mariadb or nextcloud config, "just updated" nextcloud container and nothing else.

 

I have appdata backups of all dockers, from 09-14. Should I do a restore (with appdata backup) for nextcloud and mariadb?

I already set up zfs datasets on my appdata. If I would have done snapshots before the crash, maybe restoring would be even easier...?

I appreciate any help, 

Thanks

 

So finally I restored mariadb and nextcloud from my appdata backp and installed nextcloud:29.0.7-ls339 from CA. Now it works, but I'm not sure about upgrading now.. 😅

Edited October 1, 20241 yr by zoller
partially solved

You haven't provided sufficient detail to help with this.

However, I would try again. It could simply be a partial upgrade failure, since you mentioned how slow it was to upgrade.

 

You should always post your config.php and nginx conf file and explain if there are reverse proxy, etc. Otherwise, any answers you get are not going to pinpoint the issue.

On 6/1/2023 at 10:01 PM, JonathanM said:

Exactly. Never update the container without first checking the Nextcloud version inside the app.

 

The two events will seldom if ever overlap, the app will typically update much less often than the container, so many times you will still be up to date with Nextcloud when the container updates. The issue comes when people ignore the app updates for months and automatically update the container.

Hi,

 

I found out few days ago that my Docker container was set to "lscr.io/linuxserver/nextcloud:25.0.2" probably due to History reasons and issue with the PHP

Quote

This version of Nextcloud is not compatible with PHP>=8.2.
You are currently running 8.2.6.

So i thought lets set it to "latest" , but then i got error about that version is on 30 and u need to be on 28 (or something in this matter)

So i set the mentioned docker version to the version it asked  "lscr.io/linuxserver/nextcloud:28.0.2" , but after doing it Nextcloud docker is gone from Docker Containers menu and i have no clue how to get it back.

 

Could you or someone please suggest what can I do about it? 

Thanks!

3 hours ago, killeriq said:

Could you or someone please suggest what can I do about it?

Look in previous apps, if it's in there you can reinstall, set the tag to linuxserver/nextcloud:28.0.10-previous and see what happens.

 

See here for a list of valid tags.

https://hub.docker.com/r/linuxserver/nextcloud/tags

For some reason, I can't quote.

Your NC docker has disappeared, because it's orphaned.  You can open the advanced view of the docker page and remove it.

 

As for the main issue at hand, particularly if your existing version is generations out of date.

 

Personally, I would roll this back using an app data restore of your database and your NC.  Install the NC docker from previous apps (make sure you have the right version, by modifying the label).

 

Then upgrade NC by increasing the label versions. Look back through this thread of posts I've made if you're still stuck. This issue of jumping versions and breaking NC is common.

 

 

Hello everyone,

 

I've been using Nextcloud for a few years now without issues.

 

But for some reason my 2FA stopped working on my admin account and I can't disable it. I've tried changing the config.php file to "  'twofactor_enforced' => false," but it keeps asking me for my two factor code.

 

I somehow lost the backup code, I still have my two factor app and I still see my nextcloud on there but for some reason nextcloud just won't accept the codes and keep saying "Error while validating your second factor"

Edited October 13, 20241 yr by sloob

I'm away, so I can't give you exact commands. Use occ to generate a one off code for login.

13 minutes ago, sloob said:

Hello everyone,

 

I've been using Nextcloud for a few years now without issues.

 

But for some reason my 2FA stopped working on my admin account and I can't disable it. I've tried changing the config.php file to "  'twofactor_enforced' => false," but it keeps asking me for my two factor code.

 

I somehow lost the backup code, I still have my two factor app and I still see my nextcloud on there but for some reason nextcloud just won't accept the codes and keep saying "Error while validating your second factor"

 

all of a sudden I am getting error in container log as below:

 

Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused in /app/www/public/lib/private/DB/Connection.php:233

 

DB user and password are correct and have not changed in over a year. All of a sudden it happened yesterday.

Edited October 15, 20241 yr by nekromantik

On 10/11/2024 at 9:50 PM, JonathanM said:

Look in previous apps, if it's in there you can reinstall, set the tag to linuxserver/nextcloud:28.0.10-previous and see what happens.

 

See here for a list of valid tags.

https://hub.docker.com/r/linuxserver/nextcloud/tags

I found it in Previous Apps (didnt knew it exist  ) and did re-install, now I see Docker again, but it wont start WebUI.

It gives 404

 

Seems like i had docker on this version "lscr.io/linuxserver/nextcloud:25.0.2"

Here is the output from NC Docker Log

 

Edited October 15, 20241 yr by killeriq

4 minutes ago, killeriq said:

Seems like i had docker on this version "lscr.io/linuxserver/nextcloud:25.0.2"

 

On 10/11/2024 at 3:50 PM, JonathanM said:

set the tag to linuxserver/nextcloud:28.0.10-previous and see what happens.

 

On 10/11/2024 at 11:15 PM, Geck0 said:

For some reason, I can't quote.

Your NC docker has disappeared, because it's orphaned.  You can open the advanced view of the docker page and remove it.

 

As for the main issue at hand, particularly if your existing version is generations out of date.

 

Personally, I would roll this back using an app data restore of your database and your NC.  Install the NC docker from previous apps (make sure you have the right version, by modifying the label).

 

Then upgrade NC by increasing the label versions. Look back through this thread of posts I've made if you're still stuck. This issue of jumping versions and breaking NC is common.

 

 

I found your post,

I assume this might do the trick...but seems like Apps backup isn't backing up for some time, probably something changed during upgrades. 

Or where i could double check please?

16 minutes ago, JonathanM said:

 

 

My curiosity was Faster and i've set 28.0.4 as it mentioned in the Log

 

Now it loads till WebUI. So what is the correct process to upgrade with NC Docker (unraid) and the Nextcloud server it self?

Just now, killeriq said:

what is the correct process to upgrade with NC Docker (unraid) and the Nextcloud server it self?

For THIS specific container, just keep walking the tag versions forward. I don't know how many you can jump, sometimes even point updates are needed for major versions to work.

 

Other containers may handle this differently.

I did set "28.0.10-previous" , but then it didnt want to upgrade to 28.0.11 from WebUI. 

So i went via commands and now i'm stuck here:

 

No such Log in Nextcloud folder, will check also inside docker

Edited October 15, 20241 yr by killeriq

20 minutes ago, killeriq said:

My curiosity was Faster and i've set 28.0.4 as it mentioned in the Log

 

Now it loads till WebUI. So what is the correct process to upgrade with NC Docker (unraid) and the Nextcloud server it self?

JonathanM is correct. If you look st my previous posts, you'll see how to change versions using labels. There should be several recent ones precisely on this topic. I suggest you fix your appdata backup process first. This should be done before each backup.

 

Secondly, I suggest you look at my posts in this thread  and learn the basic commands to run after each restore or upgrade.  Otherwise, you'll have further perceived issues.

 

Thirdly, if you're upgrading through multiple versions, you're likely to see errors in the logs. Some will be issues that are resolved in later upgrades, so I wouldn't stress over them. 

 

Fourth. If you can replicate your current setup easily. You could always bypass the headache of upgrading multiple versions and just clean install the latest version and start to keep it updated moving forward. Your data will still be preserved but Calendar, tasks and anything thst is database driven will need to be recreated. 

 

If you're appdata isn't being backed up and your multiple versions behind on Nextcloud, then this could be your shortcut. Your photos, documents etc will still be there, provided you don't do something odd. 🤪

 

I suggest you figure out a good backup process. My NC backs syncs our family devices automatically. If we all lost our phones today, it would be a pain, and expensive to replace but everything is back to normal within the day once we've restored the settings from backup and Nextcloud syncs.

 

 

 

 

 

 

 

11 minutes ago, killeriq said:

I did set "28.0.10-previous" , but then it didnt want to upgrade to 28.0.11 from WebUI. 

So i went via commands and now i'm stuck here:

 

No such Log in Nextcloud folder, will check also inside docker

 You're trying to upgrade NC within the container, instead of upgrading the container and NC itself. You also shouldn't have to chmod, despite what it says. I suggest you occ maintenance:off and then upgrade using the label method, which is the correct method for this container. 

 

 

 

16 minutes ago, Geck0 said:

 You're trying to upgrade NC within the container, instead of upgrading the container and NC itself. You also shouldn't have to chmod, despite what it says. I suggest you occ maintenance:off and then upgrade using the label method, which is the correct method for this container. 

 

 

 

Ahh i didnt knew that the Docker upgrade , updates also the Nextcloud server...

 

As formerly Docker was on 25.0.4 and NC on 28.x.x

 

Ok my bad, will try as u say...thanks (another hour wasted  

Ok now im on 29.0.8-previous , update went well.

 

But in UI i see this error, nothing specific in logs...

 

Will leave it for next day...1am here

 

49 minutes ago, killeriq said:

Ahh i didnt knew that the Docker upgrade , updates also the Nextcloud server...

 

As formerly Docker was on 25.0.4 and NC on 28.x.x

 

Ok my bad, will try as u say...thanks (another hour wasted  

If you've upgraded Nextcloud to 28. You can try changing the label to the same version, or as close to the higher version available. If that works then continue to use the label version.

 

Again, read my posts, they're written for others that have similar issues. NC is not as simple as other dockers.

On 10/15/2024 at 3:57 PM, nekromantik said:

all of a sudden I am getting error in container log as below:

 

Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused in /app/www/public/lib/private/DB/Connection.php:233

 

DB user and password are correct and have not changed in over a year. All of a sudden it happened yesterday.

anyone?