[Support] Linuxserver.io - Nextcloud


Recommended Posts

Hi there,
I hope someone can help me with my issue.
I´ve been trying to get it fixed, with several things i found online.
It started with the "stuck on step 6 update"
*Tried manually updating using occ command, and ended up completely without working NC (giving - Internal Server Error) .

*So i did a restore of the docker.
*After that i Updated the Mysql/Mariadb because of corrupt mysql.proc.
and so on.
But now still stuck with NC not working properly.
Apps page keeps loading but nothing shows.
A lot of apps give Internal Server Error since then.
@ the admin/overview page by Version this error is shown

Hope someone has a solution for me

image.png

Link to comment
4 hours ago, spiderben25 said:

Hi, 

My issues were resolved by updating all of the conf file in my swag nginx folder. Some were really old (2020) and I think updating to Nextcloud 25 might have cause incompatibilities. 

Now Nextcloud is working fine using the latest Linuxserver docker image.

New problem: I can't access Onlyoffice in Nextcloud. When I open a docx file I get a blank error screen saying "documentserver.myserver" doesn't allow connection. I didn't change anything in the Onlyoffice settings panel and I can access the welcome page. I think something is messed up in my swag config files but can't figure it out.

Hi Spiderben,

 

how would one update those files? Any pointers? :)

 

Best,

Rick

Link to comment

You can check which files are deprecated by looking at swag log on the Docker tab of your unraid webui.

Then you can delete (I strongly recommend you make a backup first) them, they are located in /mnt/user/appdata/swag/nginx. The next time you will restart the swag container it will create up to date config files.

You can also do this to the nginx config files in /mnt/user/appdata/nextcloud/nginx. Same warnings here.

Of course if you made custom changes in said files you will have to make them again. An easy way to check that is to compare side by side the old and new config file, with notepad++ for instance.

Edited by spiderben25
Link to comment

Tried some more things today.

First of all, connection between Nextcloud and OnlyOffice was ok (you can check this by using "occ onlyoffice:documentserver --check" command in Nextcloud docker command prompt).

 

When I tried to open a file, I got a "Onlyoffice cannot be reached" error. I got more explanation on this error by pressing F12 in Chrome. The source of the error was "too many redirects".

Than I edited my swag/nginx/proxy.conf swag file like this:

proxy_redirect off;
#proxy_redirect http:// $scheme://;

to turn off the redirecting system.

 

Tried again, this time it doesn't work and the error Chrome shows is "Refused to display 'https://documentserver.mydomain.net/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.

I tried to comment out "add_header X-Frame-Options "SAMEORIGIN" always;" line in /swag/nginx/ssl.conf but it didn't do anything.

Can anyone help me with this?

 

I will roll back to Collabora in the mean time.

 

 

 

Link to comment

Can anyone confirm that the latest linuxserver container works? I used to use a reverse proxy but a year back I uninstalled that container and stopped using it. Could it be possible that nextcloud breaking is due to residual config issues? But as to how that would result in a incompatible PHP version error is beyond me.

Link to comment
On 1/8/2022 at 7:20 AM, Vitor Ventura said:

Hello,

 

Im having a problem, cant make it work, nextcloud is tell me, that is updating, but never finish.

image.png.c46b1b8377e9026719d78c15892cd841.png

 

Log is simple:

Could not open input file: /config/www/nextcloud/cron.php

 

 

Did you ever find a fix for this?  Mine has done this as well when it was updating.

Link to comment

Hello guys!

 

Im having a lot of trouble with the syncing of big archives in Nextcloud. It seems like its a common problem, but i have tried a lot of proposed solutions in the web, with no avail.

 

Setup:

Unraid 6.11.1

Nextcloud Server: Latest LSIO Docker V25, Maria DB LSIO Container.

Nextcloud Client: Latest APPImage 3.6.1 (Kubuntu Linux 20.04)

 

Problem:

  • Nextcloud client in desktop gives the error " 413 Request entity too large", in all my files bigger than around 500MB.
  • Web client / Android with no issues.

Attempted Solutions:

nano /mnt/user/appdata/nextcloud/nginx/nginx.conf

# Original: 
    client_max_body_size 0;

#Test 1:
    client_max_body_size 16G;


#Test 2:
    client_max_body_size 16G;
    client_body_buffer_size 400m;

 

nano nano /mnt/user/appdata/nextcloud/php/php-local.ini

post_max_size = 10G
upload_max_filesize = 10G
post_max_size = 10G
max_input_time = 3600
max_execution_time = 3600
memory_limit = 1024M

 

image.png.58e06e9ac7a32cf021a9dabdfeb1a4f1.png

 

Restarting the docker service between al the testing.

 

appreciate any help!

Edited by mrdavvv
Link to comment

Can somebody explain how to set the System Timezone?  All my logs are in UTC.  System time shows UTC.  I want to change this to PST.

image.png.289e2bb4f83e79a6538ba3e97c869074.png

 

Ive tried editing php-local.ini to include this line
 

date.timezone = America/Vancouver



but it doesn't do anything.

Edited by 007craft
Link to comment
6 minutes ago, 007craft said:

Can somebody explain how to set the System Timezone?  All my logs are in UTC.  System time shows UTC.  I want to change this to PST.

image.png.289e2bb4f83e79a6538ba3e97c869074.png

 

Ive tried editing php-local.ini to include this line
 

date.timezone = America/Vancouver



but it doesn't do anything.

Go to the Unraid control panel and go to settings and then date & time. 

Link to comment
15 minutes ago, blaine07 said:

Is there anyone on 25.0.1 without issue and doing good?

yep, no issues here since all the latest updates

 

and all seems to be fine here, but i only use NC for foto uploads and file browsing, sharing ... and OnlyOffice integration (OO as sep. Docker of course as its not supported in alpine, at least last time i checked)

image.png.6c9bf0abdbfd9b98e8531c995b6128ee.png

  • Like 1
Link to comment
2 hours ago, alturismo said:

yep, no issues here since all the latest updates

 

and all seems to be fine here, but i only use NC for foto uploads and file browsing, sharing ... and OnlyOffice integration (OO as sep. Docker of course as its not supported in alpine, at least last time i checked)

image.png.6c9bf0abdbfd9b98e8531c995b6128ee.png

Thank you! Will upgrade one instance later and see what happens lol. All this database issues got me scared lol

Link to comment
On 11/4/2022 at 9:16 AM, spiderben25 said:

You can check which files are deprecated by looking at swag log on the Docker tab of your unraid webui.

Then you can delete (I strongly recommend you make a backup first) them, they are located in /mnt/user/appdata/swag/nginx. The next time you will restart the swag container it will create up to date config files.

You can also do this to the nginx config files in /mnt/user/appdata/nextcloud/nginx. Same warnings here.

Of course if you made custom changes in said files you will have to make them again. An easy way to check that is to compare side by side the old and new config file, with notepad++ for instance.

Hm, it seems my setup is a bit different. I have no swag docker, mine is called NginxProxyManager, and in its log the only thing deprecated is a method called "QueryBuilder#allowEager" and "QueryBuilder#eager", which seems to not be any kinda file.

 

I tried to shut down the nginx service to see if I can then launch the webinterface, but no dice, without nginx active I get an error 400 Bad Request, on the bottom mentioning nginx, which I don't really get as it is off.


This is really frustrating because I still have no idea what's actually broken and effectively the cloud is offline for nearly a week. I should have all passwords etc to make a migration to a different docker but I'm just not sure if I can blindly follow the Nextcloud manual on the backup, I have no idea about consoles and Linux, so I don't know if the Ubuntu examples work for this :(

Link to comment
23 hours ago, alturismo said:

yep, no issues here since all the latest updates

 

and all seems to be fine here, but i only use NC for foto uploads and file browsing, sharing ... and OnlyOffice integration (OO as sep. Docker of course as its not supported in alpine, at least last time i checked)

image.png.6c9bf0abdbfd9b98e8531c995b6128ee.png

Hi,

Could you share your documentserver.subdomain.conf file? I can't get it to work since last update. 

Link to comment

Has anyone else been getting this error with the latest linuxserver nextcloud container "This version of Nextcloud is not compatible with > PHP 7.4.
You are currently running 8.0.25." 

 

I just tried to remove linuxserver/nextcloud:24.0.5 repo tag out of curiosity and unfortunately it still crashes with the above error.  

 

For  kicks I tried adding the nextcloud:25.0.1 tag, it downloaded new data but the same error  popped up. 

 

--edit-- Wild theory but would this have something to do with the Unraid OS version? 

Edited by allinvain
Link to comment
On 11/4/2022 at 1:58 PM, mrdavvv said:

Hello guys!

 

Im having a lot of trouble with the syncing of big archives in Nextcloud. It seems like its a common problem, but i have tried a lot of proposed solutions in the web, with no avail.

 

Setup:

Unraid 6.11.1

Nextcloud Server: Latest LSIO Docker V25, Maria DB LSIO Container.

Nextcloud Client: Latest APPImage 3.6.1 (Kubuntu Linux 20.04)

 

Problem:

  • Nextcloud client in desktop gives the error " 413 Request entity too large", in all my files bigger than around 500MB.
  • Web client / Android with no issues.

Attempted Solutions:

nano /mnt/user/appdata/nextcloud/nginx/nginx.conf

# Original: 
    client_max_body_size 0;

#Test 1:
    client_max_body_size 16G;


#Test 2:
    client_max_body_size 16G;
    client_body_buffer_size 400m;

 

nano nano /mnt/user/appdata/nextcloud/php/php-local.ini

post_max_size = 10G
upload_max_filesize = 10G
post_max_size = 10G
max_input_time = 3600
max_execution_time = 3600
memory_limit = 1024M

 

image.png.58e06e9ac7a32cf021a9dabdfeb1a4f1.png

 

Restarting the docker service between al the testing.

 

appreciate any help!

 

 

Solution:

Aparently the Nextcloud LSIO image uses this addres for nginx config's:

nano /mnt/user/appdata/nextcloud/nginx/site-confs/default.conf

Instead of: nano /mnt/user/appdata/nextcloud/nginx/nginx.conf

So just adjusted this line in the former and it worked:


 

    # 04-11-2022_Increase client_max_body_size, original 512MB.

    client_max_body_size 16G;

 

After restarting the instance, NX keep insisting on the 413 error. I tried renaming the files, as it has worked for me before. After renaming some files, NX just "unfreezed" and starting uploading my big files. Finally!

Link to comment

Sorry to get back onto this again, but I just can't figure out a thing. Been more than a week that Nextcloud stopped working on me.

 

Anytime I try to get to the webinterface, I get a time-out.

I tried changing the repo to 24.0.5 or 24.0.6, no avail (by now, I changed it back to latest). I did not install Nextcloud 25, as I didn't even have a chance.

I use MariaDB and NginxProxyManager, I restartet and updated all of the dockers, the logs show no error. If I try to reach Nextcloud through the local IP, it switches to the dedicated URL set in Nginx. I can't even tell which version of Nextcloud I run, I have no read-rights on the files in appdata

 

I have no idea where it fails, but it would be tremendous if anyone could help me out here, as I simply have no idea where to even look for errors :(

Edited by CameraRick
Link to comment
On 11/7/2022 at 8:41 AM, allinvain said:

Has anyone else been getting this error with the latest linuxserver nextcloud container "This version of Nextcloud is not compatible with > PHP 7.4.
You are currently running 8.0.25." 

 

I just tried to remove linuxserver/nextcloud:24.0.5 repo tag out of curiosity and unfortunately it still crashes with the above error.  

 

For  kicks I tried adding the nextcloud:25.0.1 tag, it downloaded new data but the same error  popped up. 

 

--edit-- Wild theory but would this have something to do with the Unraid OS version? 

 

I am having this same problem. Been unable to get nextcloud to work. I have tried the various update/upgrade through command line, but it won't go past version 18. Any assistance would be greatly appreciated.

Link to comment
6 hours ago, Ccheese4 said:

 

I am having this same problem. Been unable to get nextcloud to work. I have tried the various update/upgrade through command line, but it won't go past version 18. Any assistance would be greatly appreciated.

I managed to get it to work digging through some of the previous pages of this thread:

1. First, I edited the docker and changed the repository to "linuxserver/nextcloud:24.0.5". That got rid of the php error, and got the web gui for nextcloud working again.

2. Nextcloud had to finish an upgrade from version 17 to 18 that I wasn't able to complete due to the php error.

3. I went into the settings in the nextcloud web interface, and followed the instructions under "Security & Setup Warnings". Some of the recommendations will require the instance to be offline, which can be achieved by going back to the Nextcloud console and using the "occ maintenance:mode --on". You will need to turn it back off to access the web interface again after following the recommendation.

4. I tried to update again, but it errored out due to an extra .DS_Store file. Open the root console from unraid, used "cd /mnt/user/appdata/nextcloud", then "find -iname ".DS_Store*"". Use cd to navigate to each of the locations that it located that file, then "rm .DS_Store" to delete it.

7. Updater now works. I ran it in the nextcloud console with "updater.phar". I hit y after the update to start the upgrade.

8. I repeated steps 3 and 7 until I got to version 24. Occasionally it would throw an error, but it was pretty straight forward.

9. after getting to version 24, I was able to go back into the docker settings and change the repository back to "linuxserver/nextcloud". Everything still worked after that. 

 

I do wish it was more obvious that we need to keep Nextcloud up to date from within the web interface itself. As someone who's pretty tech literate but doesn't live and breath Linux stuff, it was just kind of an unnecessary headache. Not to mention that I now have a ton of new features that I had no idea existed.

  • Like 1
  • Thanks 1
Link to comment

I tried to follow your example above and try manually updating Nextcloud using it's own updater web interface:

 

"Current version is 20.0.6.
Update to Nextcloud 20.0.14 available. (channel: "stable")"

 

As you can see I'm on an old version too but not as old as yours was. 

 

The issue I'm running into is the web updater times out constantly with errors such as these:

 

"<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.20.2</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->

 

After numerous retries the update eventually went through and now I'm on 20.0.14 and was given the option to upgrade to 21.0.9

 

Not sure why these timeout errors happen but I will just stubbornly re-run the update and how it goes through as I slowly crawl my way up the version ladder. 

 

Let's hope it all goes well. If this ends up being the path forward then everyone running into the php error must follow the examples laid out here in this thread.

Link to comment
On 11/5/2022 at 9:08 AM, blaine07 said:

I am almost afraid to ask...

 

Is there anyone on 25.0.1 without issue and doing good?

I'm on 25.01 no issues that I have found, the default to a dark theme, my eyes can't handle that so i switch back but other than that. Seems to work fine as frog hair.

Edited by ijuarez
  • Like 1
Link to comment

Ok, so here is an update folks. After going through all the steps I outlined in my previous post I managed to get my Nextcloud container updated to version 24, and now the linuxserver nexcloud container  works fine without any PHP errors 😁

 

Thanks Ccheese4 for pointing me in the right direction! 

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.