NextCloud update and is now broken

DivideBy0

By DivideBy0
in General Support

Recommended Posts

tomwhi Noob

tomwhi

Posted
Posted

I found a way to progress past this error. 

 

I added a tag onto my repo referenced in my container. 

 

In my case I'm on V24 so I used this tag however all the tags can be found can be found here: https://hub.docker.com/r/linuxserver/nextcloud/tags

 

(This is assuming you're using the LinuxServer container, adjust for your own image creator of choice). 

 

image.thumb.png.d240ea8c6febf160c03e0a1fa55f6326.png

 

 

I then started my container up and ran the following command in the Console for Nexcloud container (I'm assuming the user is abc but I've seen it called other things in different OS'): 

  

sudo -u abc php /config/www/nextcloud/updater/updater.phar

 

I kept doing this until my application was up to date (I tried running this command without changing the tag first, and I found it wouldn't progress past the error). 

 

During the process I couldn't update any more...  I tried reverting back to the "latest" tag (by not imputting a tag), but i still got the error. 

 

I changed to tag on the repo to a v25 tag (25.0.4) and was able to get back into the GUI and was able to keep updating. I was then presented with an update to v26.0.2 inside the GUI and the CLI updater. 

 

 

Once I completed that I removed the tag off my application and restarted the docker again. 

 

 

This is probably a good time to think about the way we look after our NextCloud instances. It's an amazing app but it's not "set and forget"...  I think what I'll start doing it setting the tag to the version I'm on so that it can update the container within the major version (i.e. now I'm on v26) which will not allow it to go to v27 when that comes out - and i'll do the in-app updates first before I do the container updates.... 

 

 

 

Ref: https://github.com/linuxserver/docker-nextcloud/issues/288

Ref: https://www.reddit.com/r/unRAID/comments/13xlxyz/nextlcoud_stuck_in_step_3/

 

image.png

  • Like 3
  • Thanks 4
Link to comment
dtctechs Rookie

dtctechs

Posted
Posted
6 hours ago, tomwhi said:

I found a way to progress past this error. 

 

I added a tag onto my repo referenced in my container. 

 

In my case I'm on V24 so I used this tag however all the tags can be found can be found here: https://hub.docker.com/r/linuxserver/nextcloud/tags

 

(This is assuming you're using the LinuxServer container, adjust for your own image creator of choice). 

 

image.thumb.png.d240ea8c6febf160c03e0a1fa55f6326.png

 

 

I then started my container up and ran the following command in the Console for Nexcloud container (I'm assuming the user is abc but I've seen it called other things in different OS'): 

  

sudo -u abc php /config/www/nextcloud/updater/updater.phar

 

I kept doing this until my application was up to date (I tried running this command without changing the tag first, and I found it wouldn't progress past the error). 

 

During the process I couldn't update any more...  I tried reverting back to the "latest" tag (by not imputting a tag), but i still got the error. 

 

I changed to tag on the repo to a v25 tag (25.0.4) and was able to get back into the GUI and was able to keep updating. I was then presented with an update to v26.0.2 inside the GUI and the CLI updater. 

 

 

Once I completed that I removed the tag off my application and restarted the docker again. 

 

 

This is probably a good time to think about the way we look after our NextCloud instances. It's an amazing app but it's not "set and forget"...  I think what I'll start doing it setting the tag to the version I'm on so that it can update the container within the major version (i.e. now I'm on v26) which will not allow it to go to v27 when that comes out - and i'll do the in-app updates first before I do the container updates.... 

 

 

 

Ref: https://github.com/linuxserver/docker-nextcloud/issues/288

Ref: https://www.reddit.com/r/unRAID/comments/13xlxyz/nextlcoud_stuck_in_step_3/

 

image.png


Thanks for this, was able to follow these steps and get Nextcloud back online.

  • Like 2
Link to comment
sjmatth1 Noob

sjmatth1

Posted
Posted

Thanks for this. I didn't even know I was running on an older main version (v24), I only set this up from scratch a couple of months ago so would have assumed it was current.

 

I had nextcloud to auto update, I guess that was only auto update within that v24. I found the fix very useful, I am probably woahfully under knowledged in how to keep this working properly (sysadmin for 8 years). I don't know if anyone shares these thoughts, but the user friendlyness of all this is total garbage, start to finish. I thought containers were meant to be easier? When something goes wrong I feel like I am just guessing my way to fix with these container updates, I feel like I will just kill it randomly with these sort of fixes required

  • Like 2
Link to comment
caplam Contributor

caplam

Posted
Posted

I was having the same kind of troubles. 

I decided to go the nextcloud aio route and i don't regret it. It's not very easy to setup as it's quite different from a classical unraid docker install but once you have set it up it's really nice. Updates and backups are automated. 

Link to comment
xPliZit_xs Rookie

xPliZit_xs

Posted
Posted (edited)

Hi,

 

just wanted to share my story of a successful update.

Nextcloud was no longer accessible through web interface complaining about php v8.2 version.

My installed version of nextcloud was 25.0.4. (can be checked in nextcloud installation directory a file called: updater.log)

I changed the repository name as suggested by @tomwhi from: linuxserver/nextcloud to: linuxserver/nextcloud:24.0.6-ls204 and applied to the docker

From this point on nextcloud was accessible through web interface again.

From web interface started the usual update procedure.

In total there were two updates that completed one after the other.

Afterwards, i changed the repository back to linuxserver/nextcloud and applied.

 

Good luck!

 

 

Edited by xPliZit_xs
  • Like 2
Link to comment
isvein Enthusiast

isvein

Posted
Posted (edited)

Same thing here, followed the guide from @tomwhi and got it to work after a few tries.
Then tried to update the tag to 26.0.2 but then got the same php version error.
Had to go back to 26.0.1 for it to work, nextcloud gui says Nextcloud Hub 3 (25.0.7) and there is no newer update.
Gonna keep the tag at 26.0.1 for now :)

Edited by isvein
  • Like 2
Link to comment
Joshwaaa Rookie

Joshwaaa

Posted
Posted

Hi everyone. I made a HUGE mess of things. I'm in healthcare but I was hosting a cloud for my family so I'm messing with things way out of my lane. My intention was to create a cache pool upgrading from a 250gb to TWO 2tb SSDs and move my nexcloud to it for faster reads outside of my LAN. I screwed that process up and I'll have to get back to that. For whatever reason all my dockers disappeared and it took my parity offline on my array. I had to remove it and re-add it last night and it rebuilt that just fine. Now I'm in the process of rebuilding my nextcloud but I ran into the error in this forum. Also I'm stuck in maintenance mode. How do I get out of maintenance mode? Also I did the update mentioned above and before it started it said I was on 25.0.2. If I choose a tag from a past version I then get an "Internal server error." If anyone could point me in the right direction I'd really appreciate it!

Link to comment
Sinister Explorer

Sinister

Posted
Posted
On 6/2/2023 at 5:35 AM, tomwhi said:

I found a way to progress past this error. 

 

I added a tag onto my repo referenced in my container. 

 

In my case I'm on V24 so I used this tag however all the tags can be found can be found here: https://hub.docker.com/r/linuxserver/nextcloud/tags

 

(This is assuming you're using the LinuxServer container, adjust for your own image creator of choice). 

 

image.thumb.png.d240ea8c6febf160c03e0a1fa55f6326.png

 

 

I then started my container up and ran the following command in the Console for Nexcloud container (I'm assuming the user is abc but I've seen it called other things in different OS'): 

  

sudo -u abc php /config/www/nextcloud/updater/updater.phar

 

I kept doing this until my application was up to date (I tried running this command without changing the tag first, and I found it wouldn't progress past the error). 

 

During the process I couldn't update any more...  I tried reverting back to the "latest" tag (by not imputting a tag), but i still got the error. 

 

I changed to tag on the repo to a v25 tag (25.0.4) and was able to get back into the GUI and was able to keep updating. I was then presented with an update to v26.0.2 inside the GUI and the CLI updater. 

 

 

Once I completed that I removed the tag off my application and restarted the docker again. 

 

 

This is probably a good time to think about the way we look after our NextCloud instances. It's an amazing app but it's not "set and forget"...  I think what I'll start doing it setting the tag to the version I'm on so that it can update the container within the major version (i.e. now I'm on v26) which will not allow it to go to v27 when that comes out - and i'll do the in-app updates first before I do the container updates.... 

 

 

 

Ref: https://github.com/linuxserver/docker-nextcloud/issues/288

Ref: https://www.reddit.com/r/unRAID/comments/13xlxyz/nextlcoud_stuck_in_step_3/

 

image.png

Thank you for this

  • Like 1
Link to comment
exist2resist Contributor

exist2resist

Posted
Posted
On 6/3/2023 at 3:52 AM, caplam said:

I was having the same kind of troubles. 

I decided to go the nextcloud aio route and i don't regret it. It's not very easy to setup as it's quite different from a classical unraid docker install but once you have set it up it's really nice. Updates and backups are automated. 

 

Are you using this aio https://github.com/nextcloud/all-in-one?

What are you hosting it on, what kind of resources does the machine have?

 

I think I might like that better, I am finding the container can not keep up with my workload and the amount of files I have on the system.

The preview generator stopped working about a year ago as well. 

Link to comment
caplam Contributor

caplam

Posted
Posted
23 hours ago, exist2resist said:

 

Are you using this aio https://github.com/nextcloud/all-in-one?

What are you hosting it on, what kind of resources does the machine have?

 

I think I might like that better, I am finding the container can not keep up with my workload and the amount of files I have on the system.

The preview generator stopped working about a year ago as well. 

Afaik there is only one docker; at least accessible with unraid apps.

I have a very small server. I'm the only one user of my server. It runs on a HP Z620 2xE5 2650V2 with 128GB Ram. All the files are on a 2x1TB nvme btrfs pool.

Right after the installation i think it took a a day or 2 to generate preview for my 80k photos. But i mainly use it for files, calandar and contacts.

The main advantage of aio is, at least for me, the ease of installation (fulltextsearch, collabora out of the box is a must have) and integrated backups.

The AIO data size is 40GB (photos are mounted with external files so not on the pool.

Link to comment
DrSiva2022 Noob

DrSiva2022

Posted
Posted (edited)

Today when i opened , NExtcloud was showing error regarding PHP version incompatibility.

 

I then searched and found to do this


 

Quote

 

Change Repository to lscr.io/linuxserver/nextcloud:26.0.2-ls246 122

Start Nextcloud

Update via WEB GUI to 26.0x

Remove version Tag :26.0.2-ls246 from step 1
Done

 

i did a mistake by copying the link instead of the text

 

so instead of 

lscr.io/linuxserver/nextcloud:26.0.2-ls246 122

I pasted :
  

http://lscr.io/linuxserver/nextcloud:26.0.2-ls246

 

 

Now i cant find nextcloud in apps

 

Someone help me./

 

When i try to install , i get this error :

  

One or more ports used by this application are already in use by another service or app running on your server. You will need to adjust the host ports accordingly on the template

 

Edited by DrSiva2022
Link to comment
  • 4 weeks later...
guruleenyc Explorer

guruleenyc

Posted
Posted (edited)
On 6/2/2023 at 5:35 AM, tomwhi said:

I found a way to progress past this error. 

 

I added a tag onto my repo referenced in my container. 

 

In my case I'm on V24 so I used this tag however all the tags can be found can be found here: https://hub.docker.com/r/linuxserver/nextcloud/tags

 

(This is assuming you're using the LinuxServer container, adjust for your own image creator of choice). 

 

image.thumb.png.d240ea8c6febf160c03e0a1fa55f6326.png

 

 

I then started my container up and ran the following command in the Console for Nexcloud container (I'm assuming the user is abc but I've seen it called other things in different OS'): 

  

sudo -u abc php /config/www/nextcloud/updater/updater.phar

 

I kept doing this until my application was up to date (I tried running this command without changing the tag first, and I found it wouldn't progress past the error). 

 

During the process I couldn't update any more...  I tried reverting back to the "latest" tag (by not imputting a tag), but i still got the error. 

 

I changed to tag on the repo to a v25 tag (25.0.4) and was able to get back into the GUI and was able to keep updating. I was then presented with an update to v26.0.2 inside the GUI and the CLI updater. 

 

 

Once I completed that I removed the tag off my application and restarted the docker again. 

 

 

This is probably a good time to think about the way we look after our NextCloud instances. It's an amazing app but it's not "set and forget"...  I think what I'll start doing it setting the tag to the version I'm on so that it can update the container within the major version (i.e. now I'm on v26) which will not allow it to go to v27 when that comes out - and i'll do the in-app updates first before I do the container updates.... 

 

 

 

Ref: https://github.com/linuxserver/docker-nextcloud/issues/288

Ref: https://www.reddit.com/r/unRAID/comments/13xlxyz/nextlcoud_stuck_in_step_3/

 

image.png

This also resolve the issue for me. I was already on 25.x and I had to upgrade to 27.x via console CLI of docker and then reverting the repo tag afterwards to finally get back in to GUI. THANK YOU!

I also set my docker repo to 'lscr.io/linuxserver/nextcloud:version-27.0.0' to prevent this from happening again and have a controlled upgrade in the future.

Edited by guruleenyc
  • Like 1
Link to comment
  • 3 weeks later...
xlucero1 Rookie

xlucero1

Posted
Posted
On 6/2/2023 at 5:35 AM, tomwhi said: 
sudo -u abc php /config/www/nextcloud/updater/updater.phar

1) "abc" didn't work obviously, but nor did my Admin usernames. It didn't recognize them for some reason. 
  

docker exec -it nextcloud updater.phar

^ Running this instead worked.

2) I used these tags:
24.012-ls238
25.0.4-ls229

3) After upgrading to 26.0
a. Stop docker. Remove the tag & the docker automatically starts. Open the "logs"
b. Notice version 26.0... Then it says "Updating to 27.0."
c. Working, accessible GUI now. 

Nextcloud link for update versions & command: https://info.linuxserver.io/issues/2023-06-25-nextcloud/

(Thank you for your guide!)

Link to comment
Guest
This topic is now closed to further replies.
Go to topic listing