[Support] Linuxserver.io - Nextcloud


Recommended Posts

8 minutes ago, elco1965 said:

Collabora stopped working for me after updating the container. I spent most of the day trying to fix, uninstall, re-install the container. looking at config files. This fixed it for me. Why does this happen? Where did you find the answer?

 

And thank you!

I don't really remember where I saw it. But now I'm puzzled :D 
Did you upgraded to 6.4.10, and it works? 
Because I upgraded to 6.4.10 and looks like is totally broken :D (At least when trying to open a file within NC.

Link to comment

Skois, I see quote above about not update Collabora; sure as fire mine didn’t work. I see where your quoted saying go back to 6.4.2.2; I did, it worked. When was that post made by you? Can’t seem to find its origination. Has anyone figured out what’s wrong with 6.4.10 yet by chance?

Do any versions after 6.4.2.2 work before getting all the way to the broke 6.4.10?

Link to comment
Posted (edited)
6 hours ago, blaine07 said:

Skois, I see quote above about not update Collabora; sure as fire mine didn’t work. I see where your quoted saying go back to 6.4.2.2; I did, it worked. When was that post made by you? Can’t seem to find its origination. Has anyone figured out what’s wrong with 6.4.10 yet by chance?

Do any versions after 6.4.2.2 work before getting all the way to the broke 6.4.10?

6.4.9.3 works fine and i can say have become faster!
About 6.4.10, i can't figure it out, but i made a post in their forums today, waiting for reply
https://forum.collaboraonline.com/t/code-6-4-10-docker-nextcloud-not-working/440

*The post from the fix after 6.4.2.2 was a ~5 months back :D

Edited by skois
  • Like 1
Link to comment
6.4.9.3 works fine and i can say have become faster!
About 6.4.10, i can't figure it out, but i made a post in their forums today, waiting for reply
https://forum.collaboraonline.com/t/code-6-4-10-docker-nextcloud-not-working/440

*The post from the fix after 6.4.2.2 was a ~5 months back

So at moment it IS safe to change tag to 6.4.9.3 for now?

Can you please keep us posted on your findings with them, Please? :-)

Edit: thank you man; appreciate it!!! All the thanks.
  • Like 1
Link to comment

So at moment it IS safe to change tag to 6.4.9.3 for now?

Can you please keep us posted on your findings with them, Please? :-)
Yes, 6.4.9.3 is safe and working.
If I forget to post here what is the problem with 6.4.10, make sure you follow the link I posted

Sent from my Mi 10 Pro using Tapatalk

  • Like 1
Link to comment
I don't really remember where I saw it. But now I'm puzzled  
Did you upgraded to 6.4.10, and it works? 
Because I upgraded to 6.4.10 and looks like is totally broken  (At least when trying to open a file within NC.

Discard; I’m a fool :facepalm:
Link to comment
On 1/16/2020 at 6:32 PM, Bob1215 said:

I kept getting a 504 code when attempting to update form the webUI. Now I can't access nextcloud at all. I posted and issue here

 

Expected Behavior
When navigating to the NextCloud instance through the web browser, the application should be shown.

 

Current Behavior
The following message is shown "Update in process." and has persisted for multiple hours, including after reboot and using multiple browsers (FireFox ESR and Brave Browser)

 

Steps to Reproduce
1. Open web browser
2. Type in NextCloud URL
3. See message

 

Environment
OS:      unRAID 6.8.0
CPU architecture: x86_64

Docker logs


[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
[cont-init.d] 50-install: exited 0.
[cont-init.d] 60-memcache: executing...
[cont-init.d] 60-memcache: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Could not open input file: /config/www/nextcloud/cron.php
Could not open input file: /config/www/nextcloud/cron.php
....

....

....
Could not open input file: /config/www/nextcloud/cron.php
Could not open input file: /config/www/nextcloud/cron.php
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
[cont-init.d] 50-install: exited 0.
[cont-init.d] 60-memcache: executing...
[cont-init.d] 60-memcache: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Could not open input file: /config/www/nextcloud/cron.php
Could not open input file: /config/www/nextcloud/cron.php
Could not open input file: /config/www/nextcloud/cron.php
Could not open input file: /config/www/nextcloud/cron.php

 

 

Do you remember how you fixed this? I am trying to update and I'm experiencing the exact same. 

Link to comment
On 5/20/2021 at 6:33 AM, Jessie said:

I presume you are talking about updating nextcloud itself vs updating the docker in unraid.

I'm also going to guess you are going to v21 from 20

In unraid open a console from the nextcloud icon

Then run these commands one at a time.

sudo -u abc php /config/www/nextcloud/occ db:add-missing-indices
sudo -u abc php /config/www/nextcloud/occ db:convert-filecache-bigint

sudo -u abc php /config/www/nextcloud/occ db:add-missing-columns
sudo -u abc php /config/www/nextcloud/occ db:add-missing-primary-keys

 

Then

sudo -u abc php /config/www/nextcloud/occ maintenance:repair

then

sudo -u abc php /config/www/nextcloud/occ upgrade

then

sudo -u abc php /config/www/nextcloud/occ maintenance:repair

(again for good measure)

Then turn maintenance mode off

sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off

Then see if you can get back to the logon screen

 

I'm having major issues getting Nextcloud to update. I tried to update through the GUI and eventually had to restore my appdata from a backup as Nextcloud became inoperable. Now I'm trying through the CLI. Option 2 from the first page of this forum results in:

Step 6 is currently in process. Please call this command later.

 So, I tried Option 3 (manual upgrade using occ) when I run the perform upgrade step, I am presented with:

Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Turned on maintenance mode
Exception: Updates between multiple major versions and downgrades are unsupported.
Update failed
Maintenance mode is kept active
Resetting log level

Then I found your post and I tried the first command you mention and I get:

sudo: unknown user: abc
sudo: unable to initialize policy plugin

It seems way too complicated to update Nextcloud. Any idea what my options are now? 

Link to comment
On 6/27/2021 at 3:29 AM, Harlequin42 said:

Reinstalling sometimes help if you configure the setting again but reinstalling using the same config files and hoping something would change is mostly not working out.


What is with this? Did you get an error? What happened?

 


$ sudo -u www-data php /var/www/nextcloud/occ user:resetpassword admin
Enter a new password:
Confirm the new password:
Successfully reset password for admin

 

maybe try a simpler password with less or no special character, you can change it later.

I think I had a similar issue somewhen (not sure if it was Nextcloud User or mariadb user) and figured out some character didn’t work. 

Hi,

 

Yes I tried the resetpassword and the error I get is:

sudo: unknown user: yourusername
sudo: error initializing audit plugin sudoers_audit

 

So I am still at a loss as to what is going on. Thanks!

 

 

Link to comment
On 7/2/2021 at 8:24 AM, Danuel said:

hi, can anyone please help with this fix, i did a update to nexcloud 20.0.11 and i get this error

Some files have not passed the integrity check

Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results
=======
- contacts
    - INVALID_HASH
        - appinfo/app.php

Raw output
==========
Array
(
    [contacts] => Array
        (
            [INVALID_HASH] => Array
                (
                    [appinfo/app.php] => Array
                        (
                            [expected] => ecd6dbda1c2759006a6f2c43856bcfeb64274d4f5e8a0821f4aef9adbfa835d01d4d90143cf8960b7e2e70d6eca0cf444a244b3d06bc861067a852575799410e
                            [current] => 73c10c4bdef249f3b59e97a3992270e01bdd0aa547b715909fe8822a35f9e9423a81654eeca571c1cc1c83acab5ca4052d96f387df1cf869ce442c3da3499cc2

 

any idea on how i can fix this please

 

 

anyone any fix ?

Link to comment
Posted (edited)
On 7/2/2021 at 11:48 PM, skois said:

I don't really remember where I saw it. But now I'm puzzled :D 
Did you upgraded to 6.4.10, and it works? 
Because I upgraded to 6.4.10 and looks like is totally broken :D (At least when trying to open a file within NC.

 

I did and it broke. In Nextcloud, setting, CODE, the server would show reachable. But when trying to open a document from within Nextcloud I would get a "Document Failed To Download Error". 

 

On 7/3/2021 at 9:53 AM, skois said:

6.4.9.3 works fine and i can say have become faster!
About 6.4.10, i can't figure it out, but i made a post in their forums today, waiting for reply
https://forum.collaboraonline.com/t/code-6-4-10-docker-nextcloud-not-working/440

*The post from the fix after 6.4.2.2 was a ~5 months back :D

 

I am now on 6.4.9.3 it seems to work but the Collabora log reports messages like this,

 

wsd-00007-00043 2021-07-05 17:5xxx67 [ websrv_poll ] WRN FileServerRequestHandler: File not found: Invalid URI request: [/loleaflet/0b3211b/undefined].| wsd/FileServer.cpp:487
sh: 1: /usr/bin/loolmount: Operation not permitted
frk-00039-00039 2021-07-05 17:xxxxxx27 [ forkit ] ERR Failed to unmount [/opt/lool/child-roots/MYVtxquZPEzEwk4h/tmp].| common/JailUtil.cpp:68
sh: 1: /usr/bin/loolmount: Operation not permitted
frk-00039-00039 2021-07-05 17:xxxxx9 [ forkit ] ERR Failed to unmount [/opt/lool/child-roots/MYVtxquZPEzEwk4h/lo].| common/JailUtil.cpp:68
sh: 1: /usr/bin/loolmount: Operation not permitted
frk-00039-00039 2021-07-05 17:5xxxxx945 [ forkit ] ERR Failed to unmount [/opt/lool/child-roots/MYVtxquZPEzEwk4h].| common/JailUtil.cpp:68even though I am able to open and edit a document in Nextcloud

 

even though I am able to open, edit, and save a document. 

 

P.S. I never really looked at the Collabora logs much before as it worked without issue before the last update that broke it. So I have no idea what the logs should look like.

Edited by elco1965
Link to comment

Morning,

Skois, I saw Nextcloud this morning had a update for Collabora Online. I don’t think updating that helps with our Collabora issue BUT I looked at change log

91a802b5d398525f90b10dcac09807d3.jpg


File permissions was the issue we were having when upgrading so perhaps this tidbit of info is relative to our issue upgrading Collabora past whatever version it was broke on?

Link to comment
Morning,

Skois, I saw Nextcloud this morning had a update for Collabora Online. I don’t think updating that helps with our Collabora issue BUT I looked at change log

91a802b5d398525f90b10dcac09807d3.jpg


File permissions was the issue we were having when upgrading so perhaps this tidbit of info is relative to our issue upgrading Collabora past whatever version it was broke on?
Tried again today with 6.4.10.2 also, but still broken

Sent from my Mi 10 Pro using Tapatalk

  • Like 1
Link to comment

After update I got this:

 

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

 

I have no idea how to hunt the problem.

Link to comment
14 hours ago, jafi said:

After update I got this:

 


Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

 

I have no idea how to hunt the problem.

Probably best start by providing info on the container - Have you been keeping nextcloud updated within the container? Nginx logs? nextcloud logs?

  • Like 1
Link to comment
8 hours ago, j0nnymoe said:

Probably best start by providing info on the container - Have you been keeping nextcloud updated within the container? Nginx logs? nextcloud logs?

 

Eventually I figured the problem: mariadb docker is disappeared.

Sorry for the spam.

Link to comment
Posted (edited)

I've been having similar issues... for some reason, the docker image never updated from 19.0.3 automatically from the Unraid docker dashboard.  I just went through a process to update to 22.0.0... I'll explain below.

 

On 7/4/2021 at 2:16 PM, Richamc01 said:

Then I found your post and I tried the first command you mention and I get:



sudo: unknown user: abc
sudo: unable to initialize policy plugin

 

 

I found that these issues were usually because I didn't give Nextcloud enough time to start.  Watch the logfile for the following line before trying to execute occ commands.

[cont-init.d] 01-envfile: exited 0.

 

 

On 7/4/2021 at 2:16 PM, Richamc01 said:

Exception: Updates between multiple major versions and downgrades are unsupported. Update failed Maintenance mode is kept active Resetting log level

 

Didn't scour through all 199 pages of this support thread, but here was my solution...  it doesn't want to upgrade more than one major version at a time, so do just that... one major version at a time.  Basically, I followed the instructions in the stickied post, option 3, except for the version change indicated below:

 

##Turn on maintenance mode
docker exec -it nextcloud occ maintenance:mode --on

##Backup current nextcloud install
docker exec -it nextcloud mv /config/www/nextcloud /config/www/nextcloud-backup

##Update to latest v19 
docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest-19.tar.bz2 -P /config
docker exec -it nextcloud tar -xvf /config/latest-19.tar.bz2 -C /config/www

##Copy across old config.php from backup
docker exec -it nextcloud cp /config/www/nextcloud-backup/config/config.php /config/www/nextcloud/config/config.php

##Now Restart docker container
docker restart nextcloud

##Perform upgrade
docker exec -it nextcloud occ upgrade

##Turn off maintenance mode
docker exec -it nextcloud occ maintenance:mode --off

## Now Restart docker container
docker restart nextcloud

 

After updating, you should go into Nextcloud /settings/admin/overview page and address any security & setup warnings that are found before proceeding.

 

Then repeat the whole process except changing this step:

##Update to latest v20
docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest-20.tar.bz2 -P /config
docker exec -it nextcloud tar -xvf /config/latest-20.tar.bz2 -C /config/www

 

address any warnings as above, Then repeat the whole process except changing this step:

##Update to latest v21 
docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest-21.tar.bz2 -P /config
docker exec -it nextcloud tar -xvf /config/latest-21.tar.bz2 -C /config/www

 

address any warnings as above, then finally repeat with the steps as indicated in the sticky to get to v22:

##Grab newest nextcloud release and unpack it
docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest.tar.bz2 -P /config
docker exec -it nextcloud tar -xvf /config/latest.tar.bz2 -C /config/www

 

Once everything is working, you can remove the downloads and backup folders:

##Remove  backup folder
docker exec -it nextcloud rm -rf /config/www/nextcloud-backup

##Remove ALL Nextcloud tar files
docker exec -it nextcloud rm /config/latest*.tar.bz2

 

Edited by sdub
Link to comment
On 7/3/2021 at 12:53 PM, skois said:

6.4.9.3 works fine and i can say have become faster!
About 6.4.10, i can't figure it out, but i made a post in their forums today, waiting for reply
https://forum.collaboraonline.com/t/code-6-4-10-docker-nextcloud-not-working/440

*The post from the fix after 6.4.2.2 was a ~5 months back :D

This problem must not be to common, or I suspect we would be hearing more about it. Hope we can figure it out, but I've run out of ideas...

Link to comment
This problem must not be to common, or I suspect we would be hearing more about it. Hope we can figure it out, but I've run out of ideas...
6.4.10.3 now gives different error.
6.4.10.4 also not working.
I suspect something wrong with the reverse proxy, but not sure. Will have to dig some more tomorrow

Sent from my Mi 10 Pro using Tapatalk

  • Like 1
Link to comment
6.4.10.3 now gives different error.
6.4.10.4 also not working.
I suspect something wrong with the reverse proxy, but not sure. Will have to dig some more tomorrow

Sent from my Mi 10 Pro using Tapatalk


Thanks a ton for the continuing efforts! :-)
Link to comment

I'm on Nextcloud version 20.0.10 and I no longer see the open updater in overview under administration.  I remember disabling a bunch of apps to try and improve performance.  Could that be related?  Is there a way for me to check and upgrade another way?  Thanks. 

Link to comment
On 7/10/2021 at 12:56 AM, blaine07 said:


Thanks a ton for the continuing efforts! 🙂

Tried to bypass NginxProxyManager, and tried to connect to collabora directly, with self signed cert, and disabled cert verification from NC side.

On 6.4.10.3 it does NOT work even like this.
but on 6.4.9.3 it DOES work.

Something is going very wrong with these images. Collabora did some RE-UPLOADS of 6.4.10.3 (and i think on 6.4.10.2 also) and REMOVED 6.4.10.4.
TBH, removing and overwriting images on a repository is a very very very bad tactic and can mess up with a lot of automated systems. 
If something goes wrong just issue a patch and create a new image. Imagine someone have updated to the broken 6.4.10.3 image and they re-upload a working 6.4.10.3 image, the poor guy will never see the update because the update check will tell him that he is up to date. And he will be struggling for no reason.

I hope OnlyOffice starts supporting Cell Locking/protection soon (it's been on their todo list since 2017..) so I can move there.

rant over..

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.