[Support] Linuxserver.io - Nextcloud


4868 posts in this topic Last Reply

Recommended Posts

2 hours ago, j0nnymoe said:

The well-known info needs to be added to the nextcloud nginx config and not the swag config. We've already updated this and mentioned it in the changelog for nextcloud.

 

I thought I was a little blind, couldn't find this changelog.  But there it was:

 

Quote

25.02.21: - Nginx default site config updated for v21 (existing users should delete /config/nginx/site-confs/default and restart the container).

 

Perfectly recreated with the new entries - and nicely commented too!

Link to post
  • Replies 4.9k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Application Name: Nextcloud Application Site: https://nextcloud.com/ Docker Hub: https://hub.docker.com/r/linuxserver/nextcloud/ Github: https://github.com/linuxserver/docker-nextcl

Here's my list of instructions....    Use them at your own risk.....   If upgrading to v12 please see here:   ##Turn on maintenance mode docker exec -it nextcloud occ m

Thanks, fixed for me as well, and I also added this line add_header Referrer-Policy no-referrer always; to appdata/nextcloud/nginx/site-confs/default   And now I have a green

Posted Images

Anyone else getting this error when trying to update?

 

Initializing

Current version is 21.0.0.
Update to Nextcloud 21.0.1 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-21.0.1.zip
Open changelog ↗
Retry update

Check for expected files

The following extra files have been found:

.DS_Store

._.DS_Store

._remote.php

 

Link to post

@carnivorebrah @BVD Thanks! same time I found it myself be testing, I got a message for your answers 😅

 

By digging around and testing I also found the post with the changelog @BoxOfSnoo is refering to

 

grafik.png.c20c15c9ba1d6b07aaf678e68fb5fc8e.png

https://docs.linuxserver.io/images/docker-nextcloud

Removing that file and recreate it was new for me. Never had any issues with my old config before. Last couple updates went fine until today.

 

Renaming the "default" file in "/config/nginx/site-confs" and restarting the docker at first wasn't the solution. Looks like Nextcloud is reading every file in that path when started up. Docker log showed the following and the web ui never came up.

 

grafik.png.ba91a9b187f8231660d1f4a748703dc2.png

 

So I removed the old default file from that path, restarted the docker and tada, Nextcloud was back and the errors are gone

 

BUT

 

with resetting the file, the  "Strict-Transport-Security“-HTTP-Header"  setting also was reset and had to be uncommented again. Same happened for "client_max_body_size" which i had configured to 10G before, by default it is set to 512M now. An upload with a 2GB testfile went trough. Weird 🤨

 

Link to post

Hey all, I got myself in a quite a bit of a trouble..

 

I tried to update Nextcloud to the latest stable build through the UI, but it failed.

 

I was able to get everything fixed with the help of this:

and then manually moving the files from the Backup folder to their correct locations.

 

 

But! There was another update. I thought, surely this time it would work.

It didn't.

 

I tried to do the update through the terminal again, but this time around, I'm stuck in a "Internal server issue" page.

In the log, there is one particular error that keeps showing up:
 

Quote

  "url": "/apps/dashboard/",
  "message": {
    "Exception": "TypeError",
    "Message": "Argument 1 passed to Icewind\\SMB\\BasicAuth::__construct() must be of the type string, null given, called in /config/www/nextcloud/apps/files_external/lib/Lib/Backend/SMB.php on line 82",
    "Code": 0,
    "Trace": [
      {
        "file": "/config/www/nextcloud/apps/files_external/lib/Lib/Backend/SMB.php",
        "line": 82,
        "function": "__construct",
        "class": "Icewind\\SMB\\BasicAuth",
        "type": "->"
      },

 

 

I've battled with this for hours now, and it's getting late. I'm hoping I can get this fixed through the weekend, since my team is going to need to use Nextcloud again next week.

 

 

Any help would be greatly appreciated!

Link to post

image.thumb.png.662a8f3888ad90f17f9d5a432dfe939c.png

After attempting to update NC from 21.0 (I think) to 21.0.1 via web updater, I got an error.  I retried through the command line but I can't seem to get past this point.   Now I'm stuck at loop of either "In Maintenance Mode" or "Nextcloud will be updated to version 21.0.1" Any ideas?

Link to post

So I updated to 21.0.1, and it become slower when first opening the file tab or the other main tabs like dashboard, or when opening the settings page where you check for updates. When files tab first is open, its as normal tho. When switching tabs, I think it also uses more CPU than it did before.
Anyone know the reason?

Link to post
4 hours ago, REllU said:

Hey all, I got myself in a quite a bit of a trouble..

 

I tried to update Nextcloud to the latest stable build through the UI, but it failed.

 

I was able to get everything fixed with the help of this:

and then manually moving the files from the Backup folder to their correct locations.

 

 

But! There was another update. I thought, surely this time it would work.

It didn't.

 

I tried to do the update through the terminal again, but this time around, I'm stuck in a "Internal server issue" page.

In the log, there is one particular error that keeps showing up:
 

 

 

I've battled with this for hours now, and it's getting late. I'm hoping I can get this fixed through the weekend, since my team is going to need to use Nextcloud again next week.

 

 

Any help would be greatly appreciated!

 

That's calling out the SMB PHP module, which I'd assume is an installed plugin - if you uninstall the plugin prior to your upgrade, do you still have issues?

Link to post

The Phone region thing, if you dont find it in config as I did, open the nextcloud console from docker menu and use this command:

occ config:system:set default_phone_region --value="NO"

Replace NO with the code for the country you are in.

Link to post
9 minutes ago, Mihle said:

So I updated to 21.0.1, and it become slower when first opening the file tab or the other main tabs like dashboard, or when opening the settings page where you check for updates. When files tab first is open, its as normal tho. When switching tabs, I think it also uses more CPU than it did before.
Anyone know the reason?

 

Right after an update, the cache will usually need to be rebuilt, as the DB indices are updated and the existing cache is essentially no longer 'valid' (the cache doesn't get it's existing contents updated). I'd give it some time and re-evaluate.

 

As to the phone details, you can configure them manually as well within config.php (same place you put the DB connection information etc) 👍

Edited by BVD
Link to post
11 minutes ago, BVD said:

 

Right after an update, the cache will usually need to be rebuilt, as the DB indices are updated and the existing cache is essentially no longer 'valid' (the cache doesn't get it's existing contents updated). I'd give it some time and re-evaluate.

Ah, ok, I will do that then.

Quote

 

As to the phone details, you can configure them manually as well within config.php (same place you put the DB connection information etc) 👍

The problem was that I did not find it in that file... I dont know why. After i used the command, a line got added to the end of that config tho, or I was blind, its on the last line now tho.
Its faster to just use that command anyway, if you do it straight away and dont do like me and first open the cofig, then dont find it, then find the command on internet and then do it.

 

OR you could just probably add the line yourself completely.

Edited by Mihle
Link to post
6 hours ago, bastl said:

Renaming the "default" file in "/config/nginx/site-confs" and restarting the docker at first wasn't the solution. Looks like Nextcloud is reading every file in that path when started up. Docker log showed the following and the web ui never came up.

 

grafik.png.ba91a9b187f8231660d1f4a748703dc2.png

 

So I removed the old default file from that path, restarted the docker and tada, Nextcloud was back and the errors are gone

Thank You! that is what I did wrong. Seems like the name of the file dont matter for Nextcloud, I now moved the old renamed file one step up in the file structure and it worked :)

Quote

BUT

 

with resetting the file, the  "Strict-Transport-Security“-HTTP-Header"  setting also was reset and had to be uncommented again. Same happened for "client_max_body_size" which i had configured to 10G before, by default it is set to 512M now. An upload with a 2GB testfile went trough. Weird 🤨

 

Just curious, what do the "Strict-Transport-Security“-HTTP-Header" do? Dont seem like that one even was in my old file.

Edited by Mihle
Link to post
7 hours ago, BVD said:

 

That's calling out the SMB PHP module, which I'd assume is an installed plugin - if you uninstall the plugin prior to your upgrade, do you still have issues?

 

How would I uninstall said plugin without the Nextcloud UI? 🤔

 

And you said "prior to your upgrade", are you suggesting it'd be possible to downgrade to the last version? (If it is, I'd gladly stick with 21.0.0 for a while)

 

Thank you for the answer!

Link to post

 

You'll just have to restore your backup is all, if you find no way to manually remove the plugin - though I'd assume theres a php file somewhere that you could edit out the reference to it manually to address. Youd have to do a little poking around in that one though, restoring your backup would definitely be far simpler and quicker

Link to post
7 minutes ago, BVD said:

 

You'll just have to restore your backup is all, if you find no way to manually remove the plugin - though I'd assume theres a php file somewhere that you could edit out the reference to it manually to address. Youd have to do a little poking around in that one though, restoring your backup would definitely be far simpler and quicker

 

I'll look through some files, in case I'll find the correct one that has the reference in it.

 

I'd be more than happy to just restore my old backup though, but I'm just not sure how to do that? Is there a command for it that you put in the terminal, or..? (I'm sorry, I've just built my first server some months ago. All of this is rather new to me)

Link to post

I'm going to assume you've probably not taken a backup prior to the upgrade then, as it's not something that's automatically done... I'll try to take a look in the morning to see where the plugin/hub configuration is loaded from - I've an idea that you could simply remove that file from the directory and restart the container in order for it to be regenerated, but I'm not certain and it's about 0130 here. Will try to remember to check it out once I wake up

Link to post
4 minutes ago, BVD said:

I'm going to assume you've probably not taken a backup prior to the upgrade then, as it's not something that's automatically done... I'll try to take a look in the morning to see where the plugin/hub configuration is loaded from - I've an idea that you could simply remove that file from the directory and restart the container in order for it to be regenerated, but I'm not certain and it's about 0130 here. Will try to remember to check it out once I wake up

Update proccess includes a backup.. It stores it in /data/updater-randomhash/backups/nextcloud-backupedversion

Link to post
11 hours ago, Mihle said:

Just curious, what do the "Strict-Transport-Security“-HTTP-Header" do? Dont seem like that one even was in my old file.

Quote from Wikipedia:

Quote

HTTP Strict Transport Security (HSTS) is a web security policy mechanism that helps to protect websites against man-in-the-middle attacks such as protocol downgrade attacks[1] and cookie hijacking. It allows web servers to declare that web browsers (or other complying user agents) should automatically interact with it using only HTTPS connections, which provide Transport Layer Security (TLS/SSL), unlike the insecure HTTP used alone. HSTS is an IETF standards track protocol and is specified in RFC 6797.

https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security

Link to post
On 2/26/2021 at 11:13 AM, skois said:

Right now this link is dead. I'll check it later. 
here is the new issue i created. If you want you can do a comment there with your steps. and if you have the error still.
https://github.com/linuxserver/docker-nextcloud/issues/189

 

Edit* Check the issue for the solution.
TL?DR? Update docker, delete /config/nginx/site-confs/default, restart docker, Go to Settings > Overview, (for chrome) Press F12 and while having dev tools open right click refresh button and click emtpy cache and hard reload.

 

Thank you so much, these steps are what I needed to remove my last errors and get back to all checks passed.  Much appreciated!

 

Link to post

Updated to Nextcloud 21 yesterday through the terminal. Everything went fine and there are no errors in any of the log files. Regardless I get the following message:

 

image.png.3801e3285bdb16389bc454761c1cdfda.png

 

I have checked the logs in on the Docker Icon and the following locations:

 

/mnt/appdata/nextcloud/log/nginx

/mnt/appdata/nextcloud/log/php

 

 The console still works fine and happily accepts commands.

 

Any ideas of what is wrong would be much appreciated.

Link to post
17 hours ago, Ntouchable said:

Updated to Nextcloud 21 yesterday through the terminal. Everything went fine and there are no errors in any of the log files. Regardless I get the following message:

 

image.png.3801e3285bdb16389bc454761c1cdfda.png

 

I have checked the logs in on the Docker Icon and the following locations:

 

/mnt/appdata/nextcloud/log/nginx

/mnt/appdata/nextcloud/log/php

 

 The console still works fine and happily accepts commands.

 

Any ideas of what is wrong would be much appreciated.

 

I got the same error when I updated to 21.0.1, and for me, it turned out to be the "external storage" application (which I'm using to get access to SMB shares in the Nextcloud app)

 

I got this fixed by simply removing the "files_external" folder found in:

\\YourServer\appdata\nextcloud\www\nextcloud\apps\

However, now I can't see the External Storages- application within the appstore of NC, so I'm trying to figure out how to re-install said app in order to access the SMB shares once again.



EDIT!

Haven't done a-lot of testing yet, but I think I got everything to work now!

 

Ok so, I downloaded the tar/zip file for NextCloud 21.0.0 from their website:

https://nextcloud.com/changelog/#latest20

 

I then manually moved two folders into the NextCloud installation folder.

So, in your Unraid server, navigate to:

 

\\YourServer\appdata\nextcloud\www\nextcloud\apps\files_external\

1. You see a folder named "lib" in there, remove it.

2. Open your tar/zip file you just downloaded, navigate to the same folder, and move the "lib" folder from the tar/zip file to replace your removed "lib" folder.

3. Do the same to the "3rdparty\icewind" folder.

likeso.thumb.PNG.8be4c840885ea332d82845eb8fe92471.PNG

And that seemed to do the trick for me!

 

Sorry for the bad explanation, I'm just getting a bit tired at this point, hah!

Edited by REllU
Link to post
9 hours ago, REllU said:

 

I got the same error when I updated to 21.0.1, and for me, it turned out to be the "external storage" application (which I'm using to get access to SMB shares in the Nextcloud app)

 

I got this fixed by simply removing the "files_external" folder found in:

\\YourServer\appdata\nextcloud\www\nextcloud\apps\

However, now I can't see the External Storages- application within the appstore of NC, so I'm trying to figure out how to re-install said app in order to access the SMB shares once again.



EDIT!

Haven't done a-lot of testing yet, but I think I got everything to work now!

 

Ok so, I downloaded the tar/zip file for NextCloud 21.0.0 from their website:

https://nextcloud.com/changelog/#latest20

 

I then manually moved two folders into the NextCloud installation folder.

So, in your Unraid server, navigate to:

 

\\YourServer\appdata\nextcloud\www\nextcloud\apps\files_external\

1. You see a folder named "lib" in there, remove it.

2. Open your tar/zip file you just downloaded, navigate to the same folder, and move the "lib" folder from the tar/zip file to replace your removed "lib" folder.

3. Do the same to the "3rdparty\icewind" folder.

likeso.thumb.PNG.8be4c840885ea332d82845eb8fe92471.PNG

And that seemed to do the trick for me!

 

Sorry for the bad explanation, I'm just getting a bit tired at this point, hah!

Hi REIIU

Explanation was perfect. Worked for me ... once I realised you specifically need to use the 21.0.0 files you mentioned.

Thank you very much for sharing your solution.

Ntouchable

 

Link to post

hello everyone, my first post here and new to unraid. 

hope I'm posting right,

I'm trying to setup a nextcloud docker on unraid with reverse proxy, and I tried to update from gui. after upgrade it tells me "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 researched already but I'm a noob and can't get forward.

I'm stucked, any help would be appreciated

nextcloud.log updater.log

Link to post

Not sure if the is the correct place to ask but my UNRAID Nextcloud is suddenly broken and will not connect.  I get this error "This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.15."  Nextcloud is a good app and would hate to have to remove it.  Anyone have any answers to this problem?

Link to post
9 hours ago, tcm2Lions said:

Not sure if the is the correct place to ask but my UNRAID Nextcloud is suddenly broken and will not connect.  I get this error "This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.15."  Nextcloud is a good app and would hate to have to remove it.  Anyone have any answers to this problem?

There might be a couple of hundred post about the same issue in this thread, so a search would be welcome 😉

In short, you haven't updated nextcloud in a long time.

Link to post

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.