I have NC18 in nginx and collabora in docker since long. It works also after update. And by the way update was very smoth. Why did you have to remove all files in var/www? Maybe the fault is yours and not NC18 update.
How is your set-up and how is collabora installed?
I use the collabora docker. I’ve already reinstalled the docker instance with no success.
Here is the error - https://pastebin.com/gtcHqWgp
I am no programmer so cannot interpret this. I would go back to 18.0.3, update all apps and try an update again. If it goes wrong I would try upgrade from the terminal.
Yes, I’m not going to continue to derail the topic. I had to manually reinstall the files as the web upgrade failed midway through. Thankfully I have a full backup.
All the same, the rest of nextcloud is fully function. It’s specifically collabora with the issue. A full app reinstallation did not fix it, nor did reinstalling the container.
Since I use postgresql, curious on if that’s the issue. I will indeed try a fresh installation of 18.0.4 to see if it was an upgrade issue.
Did a manual upgrade from my backup instead of the web upgrade. Fixed the problem - have removed my previous posts to avoid misinformation.
I need to stop jumping the gun on these things.
Hi @simonspa
Thanks for pointing that out. It happens every now and then that some markdown control characters get lost when the blog is transferred over here to the forum. So maybe that was it again.
I changed the text according to your findings.
Thanks a lot.
Nevermind, after fully reinstalling and importing all of my contacts etc the issue came right on back. Sticking with 18.0.3 for now.
Thank you for the help though!
Hi @Schmu
thanks for fixing it here - but the issue is also present in the actual blog post on the NC website, which is why I addressed @marinela - at least she’s listed as the author…
Cheers
Here is a statement from the twitter Account:
sadly github is having issues so we didn’t manage to grab the changelog yet… probably at some point today.
Sorry for the very newbie question, in version 18.0.3, this is normal?
occ upgrade
Nextcloud is already latest version
Thanks
Try switching to unstable and then again to stable branch.
Doesn’t work, both on Docker (crazymax image), and plain ubuntu 18.04.
Anyway, in your opinion is better to stick on 18.0.3 ?
Usually i’d say “apply a bugfix release asap”, but as long as no changelog is published one can only guess if it’s really desired to update…
After trying to upgrade from 18.0.3 to 18.0.4 my instance continues to fail when “Checking for update of app “accessibility” in appstore”
Replacing the accessibility app with the version from Github does not solve it, neither does the version from 18.0.3 that I found on nextcloud.com.
Update went well on my side.
Generally you can have a look at github to see what changed:
For an overview: https://github.com/nextcloud/server/milestones
Especially for 18.0.3 to 18.0.4: https://github.com/nextcloud/server/issues?q=is%3Aclosed+milestone%3A"Nextcloud+18.0.4"
Yesterday I upgraded from version 17.0.5 to 18.0.4.
I got an error related to the Talk App.
2020-04-23T20:41:43+02:00 Repair error: Repair step ‘OCA\Talk\Migration\FixNamespaceInDatabaseTables’ is unknown
2020-04-23T20:41:43+02:00 Repair info: No repair steps available
PHP Fatal error: Cannot declare class OCA\Talk\Migration\Version8000Date20200331144101, because the name is already in use in /var/www/nextcloud/apps/spreed/lib/Migration/Version8000Date20200331144101.php on line 54
i had to do an occ upgrade again and enable Talk App after that.
Today I realized that my shared files and folders from a read only external storages does not work. It is configured in Settings -> Administration -> External storages as local and read only. It does not work with version 18.0.4. I have a test installation with 18.0.4 and it does not work either.
I lot of errors in the log because of that. I decided to go back to version 17.0.5.
The changelog page is now updatet.
Cannot recomment this right now. Switching to beta would bring the 19.0.0 beta 5, which is really beta.
This is not what I meant, sorry if I was unclear.
My suggestion was to switch the channel to unstable and then back to stable again without performing any upgrade. I used this several times when updates didn’t show up.
Thanks for the clarification, this I did not know. I did the update sometimes after switching to beta. After the update I switched back to stable. So you are suggesting the other sequence of actions.