dius

This is what started me trying to figure out what was wrong. I got some valuable help from a few folks on this forum. Here are my notes: Upgrading Nextcloud is best done through the command line. The Docker doesn't upgrade it. In my case, I had to first downgrade my Nextcloud docker image until I found one that worked. To do this, edit the Nextcloud Docker container template. Change the repository line. I changed mine to linuxserver/nextcloud:23.0.0 after a bit of digging. I actually did this incrementally by trying an earlier version of Nextcloud until I found one that worked. You can find the different versions (tags) here: https://hub.docker.com/r/linuxserver/nextcloud at the bottom of the page. Use the following command line to upgrade: sudo -u abc php /config/www/nextcloud/updater/updater.phar This will run the updater and when finished it will ask if you want to run occ, answer yes. When the occ is done it will ask if you want to stay in Maintenance mode. Answer no. If the updater gets stuck anywhere, it will tell you what is wrong, whereas if you use the Web UI, it just hangs. If you need to restart the updater, be sure to rename the updater updater-xxxxxx folder found in the /data folder. If you don't the update will not restart. I just used this command: mv /data/updater-(fill in the rest of the file name here) /data-DELETEMEn-updater where n is a number for each time I had to do this - I think I ended up around 8 or 9. If any files are missing, you may be able to pull them from the download folder in the updater-xxxxxx folder. I was able to get a version of the version.php file from the Git repo here: https://github.com/nextcloud/server I clicked on the file name, and then selected the text and copied it. I then went to the folder /config/www/nextcloud Using nano, I created a version.php file (because mine was missing). I then pasted the content into the file, saved and exited from nano. I was able to determine that my actual Nextcloud version was 23.0.0 when I first started the updater using the command line. It was trying to update to version 23.0.12, so that told me I was on an earlier version so I downgraded to 23.0.0 (I knew that was a valid tag by checking the tags available (noted above). Then I had to change the owner of the file with the following command: chown abc:abc /config/www/nextcloud/version.php This same command is used to change ownership of any files or folders you have to pull from the downloaded upgrade version if they are missing from your current installation. If you get any errors saying it couldn't find a file, try looking in the downloaded section (/data/updater-xxxxxxxx/download When you copy them, make sure the folder they need to go to exisit. In my case the whole folder was missing due to the upgrader already having deleted it (I think). Anyway, I decided to create the missing folder and copy the entire content over, then I had to change the ownership on the folder and all of the files underneath - you can do this recursively with the chown command: chown -r abc:abc /config/www/nextcloud/whatever folder name here/ This info may also help: https://techoverflow.net/2022/06/17/how-to-fix-nextcloud-step-is-currently-in-process-please-call-this-command-later/ To get the correct version of version.php, in the git repo, you can select the tag that matches the version you need. The version.php file is at the top level of the repo, so it should be copied to /config/www/nextcloud. I had to re-run the updater multiple times, fixing my mistakes - once it ran successfully, I just kept running it until it said there were no more updated. Then I went into the Nextcloud template again, and changed the repo line to linuxserver/nextcloud:latest. I hope this helps get you back up and running. Please let me know if you run into anything that these instructions don't help with. I will try help in any way I can. I'm not the expert by any means, but I will try.

So I was finally able to fix this. First, I pulled the correct version.php file from the git repo and put it in the www/nextcloud/ directory. I had to set the ownership on it too. Next I had to copy the /core directory from the download into the nextcloud directory and set the ownership on all of those files too. With all permissions and ownerships set, the upgrade went though without a hitch. Thanks to all for your invaluable help. With a bit of digging and imagination, I was finally able to get Nextcloud up to the most current version and everything is running. Thanks a ton!!

I tried to use the CLI method, but I get this error: [ ] Extracting ...PHP Warning: require(/config/www/nextcloud/updater/../version.php): Failed to open stream: No such file or directory in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 658 PHP Fatal error: Uncaught Error: Failed opening required '/config/www/nextcloud/updater/../version.php' (include_path='.:/usr/share/php8') in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php:658 Stack trace: #0 phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php(695): NC\Updater\Updater->getVersionByVersionFile() #1 phar:///config/www/nextcloud/updater/updater.phar/lib/UpdateCommand.php(372): NC\Updater\Updater->extractDownload() #2 phar:///config/www/nextcloud/updater/updater.phar/lib/UpdateCommand.php(233): NC\Updater\UpdateCommand->executeStep() #3 phar:///config/www/nextcloud/updater/updater.phar/vendor/symfony/console/Command/Command.php(256): NC\Updater\UpdateCommand->execute() #4 phar:///config/www/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(820): Symfony\Component\Console\Command\Command->run() #5 phar:///config/www/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(187): Symfony\Component\Console\Application->doRunCommand() #6 phar:///config/www/nextcloud/updater/updater.phar/vendor/symfony/console/Application.php(118): Symfony\Component\Console\Application->doRun() #7 phar:///config/www/nextcloud/updater/updater.phar/updater.php(10): Symfony\Component\Console\Application->run() #8 /config/www/nextcloud/updater/updater.phar(10): require('...') #9 {main} thrown in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 658 How do I fix this? I'm sure there's a quick and easy way. I'll see if I can locate any instructions in the resource material you suggested. Thanks for your help.

Thanks @cat2devnull for your advice and information. I had updated Nextcloud a couple of times a year or so ago as I recall, but every time I did it ran into problems - just like now :). I was able to down grade my docker to 23.0.0, then I tried to update Nextcloud to 23.0.12, but it kept timing out. Now it's stuck on step 6, and I can't go any further. I can't get into the UI either. It just keeps telling me an update is in progress and to reload the page later. This was why I stopped updating Nextcloud and thought that updating the docker image was the same thing. Any suggestions on how I fix this newest problem? I am able to get to the console, if that helps.

Unraid 6.11.5. To be honest, I'm not sure how to find out what version of Nextcloud I'm running. I've always tried to keep up with all of the latest updates so I would assume I was up to date. Is there a file I can open to find that out? The upgrade went find with no errors. Only now it doesn't work.

I think I'm going to have to stop updating my Nextcloud docker image. I just updated it today (Feb 22, '23) and now when I try to access the gui, I get this error message: There are no errors or warnings in the log file. I have no idea where to look to fix this. Any pointers would be greatly appreciated. Thanks.

Wow! I was only having problems accessing Nextcloud, so it never occurred to me to look at Swag. I followed these instructions, and also update my customized Nextcloud conf files and now everything is working. Thank you @sonofdbn for pointing this out to me. I'll try to remember to update the appropriate config files going forward.

I wish I knew more about how this worked. I am seriously thinking about just deleting Nextcloud from my UnRaid server and starting over, but I'm not sure if that will solve anything. I'd like to get some other opinions first before I take such a drastic step.

@sonofdbn I don't think those lines are significant. I have seen them from the very first time I started using Nextcloud. There definite differences in the config files, but that is due to your local setting etc. I don't know enough about the config options to know if there are any significant changes. I tried using the new sample config files, but it didn't make any difference. It looks like there may be an incompatible certificate now, but I have no idea how to figure that out.

Since there doesn't seem to be any way to fix what has broken on my Nextcloud installation, I was wondering if I could simply remove it, then add it again. Would that solve my problem? For the benefit of anyone reading this, my Nextcloud service was working fine. I always accessed it using a domain. Just a couple of days ago, I was notified that there was an update to my Nextcloud docker so I went ahead and updated it. Nextcloud starts just fine. There are no errors in the log, however I can no longer access it. It doesn't matter if I use the domain or the IP address. The result is the same. It appears that there may be some kind of certificate issue but I have no idea how to debug it it and fix it. My thinking is that I may just remove it entirely from my Unraid server, then download and install a new one. I may lose all of my configurations, and may have to figure out how to get Collabora working again, but that may get me back up and running. Any other recommendations? Any help would be greatly appreciated.

Thanks @Archonw for your help. In answer to your question, I always use a domain. If I click on Advanced and try to go to the site I get this error and can't go any further.

I updated my Nextcloud docker container today, and now I am not able to connect to it. This is the error I get: Where should I look in order to try to diagnose this problem? I don't see any errors in the log file. Any help would be greatly appreciated.

Thanks for the help. I was able to get everything working. I did a bit more reading and discovered that I had somehow managed to mess up a couple of settings in the management access settings. I set the User SSL/TLS to strict and enabled remote access. I then had to log out of the My Servers a pp, and log back in. That was the tricky part. At first it wouldn't let me log out, so I went to the website and logged out there. Then I was able to log out from my server. I then logged back in and suddenly everything was working and there were no errors. A wonder sight to see for sure. Thanks for your help. I was able to get it working. And yes I believe your suggestion was the trigger for me getting it working. From the look of things, the URLs were correct, but it made me did a little deeper. Thank goodness for documentation :).

So I've been tweaking things a bit on my server - I no longer have the unsecure access problem. To fix that all I had to do was set the Use SSL/TLS in Management Access to Strict. That fixed that issue. As for the initial problem, I'm now seeing a message that says: JSON.parse: unexpected character at line 1 column 1 of the JSON data. Where can I locate this JSON file that is being parsed so I can find out what is going on? Any ideas? Thanks.

After I followed the instructions to update my legacy SSL certificate, I started getting this error and can no longer connect securely to my server. I'm running Unraid 6.11.5. I see some unusual things in my Access Management page now too. Several warnings like this: When I click on the Learn More link, it just takes me to the Update Your Legacy SSL Certificate Now web page. I'd like to know where I should look to fix the unexpected token issue. Any ideas: