31 minutes ago, skois said:

I'm getting the same error, so now i have to investigate it also lol

While i got the same error, after a minute or two, i refreshed the web and the file was there, so it might be a false positive!

@skois - I configured the client and it corrected the uploaded files in seconds.  I am going to attempt to upload as much as I can prior to maxing out my local drive.  I guess I can development my tree top level folders and sub folders one by one....  A long process but maybe more reliable than the WEB.

 

I will let you know how things go,  Keep me posted with your progress....

 

No worries on time...  a day a week, I am just happy someone more clever then me is on the case

I need urgent help to fix an failed update of Nextcloud. Seems that this update trashed my instance completely:

 

The update via GUI did hang several times, needed restarts and stopped at some point during 'Delete old files'. So maintenance is active currently.

 

1.) I tried to switch off maintenance mode and edited the config.php file from /config/www/nextcloud/config/config.php. I changed maintenance mode from 'true' to 'false' and did restart the container - no joy. The GUI still says 'Update in process.'.

 

2.) I tried to switch off maintenance mode with this command. It says there's no occ file. In fact there's no occ file anywhere.

root@Tower:/mnt# docker exec --user abc nextcloud php /config/www/nextcloud/occ maintenance:mode --off
Could not open input file: /config/www/nextcloud/occ

 

3.) The updater, called manually within the container at location /data/updater-octcdtkazv4p/downloads/nextcloud/updater, returns:

Nextcloud Updater - version: v19.0.3-8-gbfdc40b

PHP Notice:  Undefined variable: CONFIG in phar:///data/updater-octcdtkazv4p/downloads/nextcloud/updater/updater.phar/lib/Updater.php on line 59
Could not read data directory from config.php.

 

So I'm stuck with an activcated maintenance mode and a backup directory containing three partly filled backups.

root@Tower:/mnt/disk17/NextCloud/updater-octcdtkazv4p/backups# ls -lisa
total 8
 4820253502 0 drwxr-x---  5 nobody users  133 Nov 20 05:49 ./
 2177489188 0 drwxr-xr-x  4 nobody users  100 Nov 20 05:50 ../
 8925770799 4 drwxr-x--- 13 nobody users 4096 Nov 20 05:34 nextcloud-19.0.4.2-1605846684/
10904276397 4 drwxr-x--- 13 nobody users 4096 Nov 20 05:35 nextcloud-19.0.4.2-1605846907/
 5674653091 0 drwxr-x---  5 nobody users  150 Nov 20 05:49 nextcloud-19.0.4.2-1605847799/

 

I looked thru the Nextcloud backup/restore docs but I didn't find instructions what to do with these different backup files that are all from the same previous release level.

 

Any help is highly appreciated.

 

15 hours ago, Mystic said:

@skois - I configured the client and it corrected the uploaded files in seconds.  I am going to attempt to upload as much as I can prior to maxing out my local drive.  I guess I can development my tree top level folders and sub folders one by one....  A long process but maybe more reliable than the WEB.

 

I will let you know how things go,  Keep me posted with your progress....

 

No worries on time...  a day a week, I am just happy someone more clever then me is on the case

I didn't find a fix yet, i believe we must change something in nginx.conf (not in php) because LSIO runs on nginx not apache.
Also we might have to do the same on the reverse proxy config.

And warn you that all "failed" uploads are stored in /mnt/user/nextcloud/USER/uploads. So i tried 4 times a 11GB file and there was 4 11GB files there consuming space. 
This folder is the 1st folder the new uploaded files go until they are processed. 
So if you dont upload anything and you see files there (its probable the failed uploads) should be safe to delete

6 hours ago, hawihoney said:

I need urgent help to fix an failed update of Nextcloud. Seems that this update trashed my instance completely:

 

The update via GUI did hang several times, needed restarts and stopped at some point during 'Delete old files'. So maintenance is active currently.

 

1.) I tried to switch off maintenance mode and edited the config.php file from /config/www/nextcloud/config/config.php. I changed maintenance mode from 'true' to 'false' and did restart the container - no joy. The GUI still says 'Update in process.'.

 

2.) I tried to switch off maintenance mode with this command. It says there's no occ file. In fact there's no occ file anywhere.

root@Tower:/mnt# docker exec --user abc nextcloud php /config/www/nextcloud/occ maintenance:mode --off
Could not open input file: /config/www/nextcloud/occ

 

3.) The updater, called manually within the container at location /data/updater-octcdtkazv4p/downloads/nextcloud/updater, returns:

Nextcloud Updater - version: v19.0.3-8-gbfdc40b

PHP Notice:  Undefined variable: CONFIG in phar:///data/updater-octcdtkazv4p/downloads/nextcloud/updater/updater.phar/lib/Updater.php on line 59
Could not read data directory from config.php.

 

So I'm stuck with an activcated maintenance mode and a backup directory containing three partly filled backups.

root@Tower:/mnt/disk17/NextCloud/updater-octcdtkazv4p/backups# ls -lisa
total 8
 4820253502 0 drwxr-x---  5 nobody users  133 Nov 20 05:49 ./
 2177489188 0 drwxr-xr-x  4 nobody users  100 Nov 20 05:50 ../
 8925770799 4 drwxr-x--- 13 nobody users 4096 Nov 20 05:34 nextcloud-19.0.4.2-1605846684/
10904276397 4 drwxr-x--- 13 nobody users 4096 Nov 20 05:35 nextcloud-19.0.4.2-1605846907/
 5674653091 0 drwxr-x---  5 nobody users  150 Nov 20 05:49 nextcloud-19.0.4.2-1605847799/

 

I looked thru the Nextcloud backup/restore docs but I didn't find instructions what to do with these different backup files that are all from the same previous release level.

 

Any help is highly appreciated.

 

If you are running LSIO docker, click on the docker icon and open console.
There you can run the commands directly like "occ update:check"

So, try

- occ update:check

- occ upgrade

- updater.phar

 

if nothing works. try

- occ maintenance:repair

 

and try the above again.

And a tip while updating from GUI.

When a step times out. DONT hit retry, it still running on the backgroud, just the gui timed out. Just refresh the page, it will ask you if you are sure, hit yes.
If its still running it will tell you that is in progress, keep refreshing every 20seconds until its done, when its done it will take you back to GUI updater and then hit continue update
 

EDIT* Also upload your config file, something seems misconfigure because updater couldnt read config.php.
Maybe when you changed maintenace mode you made a typo?

 

EDIT2* This is the steps I would do.

Edited November 20, 20205 yr by skois

Thanks for your answer.

 

It seems that's there's no occ anywhere. I used find over the complete environment.

 

I'm currently rolling back completely. I store nightly backups from the (stopped) mariadb and nextcloud /config and /data directories. I guess I'm up and running again in an hour or so.

 

My first descision was to never again update Nextcloud as every update thru GUI was a pain here. Somewhere in this thread I found the manual steps to upgrade via CLI. If my nerves are back I'll try that way.

 

Thanks for taking your time to respond.

 

10 minutes ago, hawihoney said:

Thanks for your answer.

 

It seems that's there's no occ anywhere. I used find over the complete environment.

 

I'm currently rolling back completely. I store nightly backups from the (stopped) mariadb and nextcloud /config and /data directories. I guess I'm up and running again in an hour or so.

 

My first descision was to never again update Nextcloud as every update thru GUI was a pain here. Somewhere in this thread I found the manual steps to upgrade via CLI. If my nerves are back I'll try that way.

 

Thanks for taking your time to respond.

 

occ should be in /usr/bin/occ 
probably something is wrong with the config.php. 
After rollback, try updating from gui as i mentioned

1 hour ago, skois said:

So, try

- occ update:check

- occ upgrade

- updater.phar

Rolled back successfully. So I tried the steps you did sugest. Here's the result:

root@2cca0e75b737:/# occ update:check
Nextcloud 19.0.5 is available. Get more information on how to update at https://docs.nextcloud.com/server/19/admin_manual/maintenance/upgrade.html.
1 update available
root@2cca0e75b737:/# occ upgrade
Nextcloud is already latest version

Is this the expected result?

 

Thanks again.

 

Just now, hawihoney said:

Rolled back successfully. So I tried the steps you did sugest. Here's the result:

root@2cca0e75b737:/# occ update:check
Nextcloud 19.0.5 is available. Get more information on how to update at https://docs.nextcloud.com/server/19/admin_manual/maintenance/upgrade.html.
1 update available
root@2cca0e75b737:/# occ upgrade
Nextcloud is already latest version

Is this the expected result?

 

Thanks again.

 

I think update:check might only check for app updates but not sure.
What does the gui updater says?

51 minutes ago, skois said:

I think update:check might only check for app updates but not sure.
What does the gui updater says?

"There's an update available."

 

I have fear to go thru this again. Won't use the GUI updater in the future.

 

3 minutes ago, hawihoney said:

"There's an update available."

 

I have fear to go thru this again. Won't use the GUI updater in the future.

 

Just instead of hitting retry on updater, refresh the page. i'm updating my "produciton" docker and my test docker all the time like this! 

Did it and it worked this time. Thanks for your support.

 

55 minutes ago, hawihoney said:

Did it and it worked this time. Thanks for your support.

 

I'm happy it worked! I changed my timout settings to 7200 yesterday (from 3600) ill check on next update if its enough! I'll try to remember to mention here!
If you see an update just ping me to remind me lol!

@ skois - I seen you post.

 

I attempted to upload large files using the client and received the 504 error.  I am going to try to move thing over is small chunks since nextcloud doesn't like large chunks . 

 

I found a thread about using terminal to move data.  First I have to connect my Qnap to my Unraid server and then identify the location of the data and move it.  I am sure they make it sound easier then it is but it maybe my only choice.  I have this thread now sending me emails so I can keep up with your progress.

 

And of course once I figure out using terminal to transfer data I will let you know how it goes..

On 11/19/2020 at 10:34 AM, capt.shitface said:

 

Thank you!

It was the Collabora plugin that broke nextcloud!
Just open a terminal to the nextcloud-docker and type:

sudo -u abc php /config/www/nextcloud/occ app:disable richdocumentscode
sudo -u abc php /config/www/nextcloud/occ app:disable richdocuments

Then restart docker.

Thank you!!  It worked!

On 11/17/2020 at 2:29 PM, huladaddy said:

Just tried to launch the webui and got this message:

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.

 

This is all that is in the container log:

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


Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
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] 70-aliases: executing...
[cont-init.d] 70-aliases: exited 1.
[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.

Not sure what went wrong or where to go from here.

 

Could really use some assistance. Does anyone have any ideas of what is going on?

 

 

I am trying to share an existing media share on my unraid server using the external storages app. It is my understanding that if I create a Host path to the share in the container settings, I would simply need to configure in the Nextcloud settings for External storages a point to that mapped share and then add the username and password for SMB.

I keep getting an error when I do so. Can someone point me to instructions on how to setup external storages?

 

I am trying to share an existing media share on my unraid server using the external storages app. It is my understanding that if I create a Host path to the share in the container settings, I would simply need to configure in the Nextcloud settings for External storages a point to that mapped share and then add the username and password for SMB.

I keep getting an error when I do so. Can someone point me to instructions on how to setup external storages?

 

If you want to map a share via external storages, you don't map it in the docker template.

 

You just go to external devices and fill the forms.

You just have the share to be visible on network.

On host put your server ip address and on share put the share path excluding the /mnt/user/

 

Sent from my Mi 10 Pro using Tapatalk

 

 

 

1 hour ago, skois said:

If you want to map a share via external storages, you don't map it in the docker template.

 

You just go to external devices and fill the forms.

You just have the share to be visible on network.

On host put your server ip address and on share put the share path excluding the /mnt/user/

 

Sent from my Mi 10 Pro using Tapatalk

 

 

 

This fixed me up thank you. 

I see that version 20.0.2 is the latest version for the linuxserver.io docker, but when I do a check from Settings it still shows me 19.0.5 as the current version on the Stable channel. Is 20.0.2 only available via the Beta channel? Or is there something in my configuration holding it back?

Hello all,

I have been trying to have other people upload files to a folder I have created on Nextcloud and created a share link to allow for uploading to the folder. However it was reported to me that they were having trouble and I was able to "recreate" the issue on my side. 

The issue: when uploading files to the shared folder all files no matter how I upload them (via drag and drop or the dialogue to upload files) immediately shows the error "An unknown error has occurred." On occasion I'll get an error along the lines of - Server connection lost - but that one has been far more inconsistent and I think it is related to whatever the problem is preventing any files from being uploaded. 

Now with all of that being said I can upload files if I am logged in as a user and that is the workaround I have created for the other person in this case but I would like to be able to simply share a link in the future and have other people be able to upload files to me. The other part in this case has been able to download files from the link without issue however uploading seems to be a problem. Which is strange. Why would downloading work but not uploading, any bight ideas here? 

 

Thanks for your help! 

23 minutes ago, GalacticSpines said:

I've just upgraded to Nextcloud 20.0.2 and everything works fine, but when I run Nextcloud Security Scan it shows my old version Running Nextcloud 19.0.2.2?  Just wondering if this is normal or did I screw something up?

 

 

 

 

Trigger re-scan

Has anyone had any luck getting HEIC to work natively in nextcloud or at least the plugin HEIC to JPG? A while back I found a forum saying that they believed it was something that should work but the problem is unique to this docker image but I cannot find that forum post anymore. 

1 hour ago, skois said:

Trigger re-scan

Thanks, I didn't see the date at the bottom.  Did a re-scan and it updated correctly.

Thanks, I didn't see the date at the bottom.  Did a re-scan and it updated correctly.

[emoji6][emoji6]

Sent from my Mi 10 Pro using Tapatalk