[Support] Linuxserver.io - Nextcloud

[dius]

I updated my Nextcloud docker container today, and now I am not able to connect to it.  This is the error I get:

 

 

Where should I look in order to try to diagnose this problem? I don't see any errors in the log file.

 

Any help would be greatly appreciated.

Edited January 24 by dius

[Archonw]

Do you always connect to your nextcloud via IP adress vor do you use a domain?
It seems there is a ssl certificate error. If you hit advanced you should be able to click in something like go to IP adress unsecure...


Gesendet von meinem Pixel 6 Pro mit Tapatalk

[dius]

Thanks @Archonw for your help.

 

In answer to your question, I always use a domain.

 

If I click on Advanced and try to go to the site I get this error and can't go any further.

 

Edited January 27 by dius

[itskamel]

On 12/9/2022 at 11:12 PM, blaine07 said:

In Unraid file manager who does it show has ownership of Nextcloud app data? What is its read write rules?

 

 

how do you get it to show you the permissions? mine doesnt show folder permissions. do i have to enable it somewhere?

[Kilrah]

7 hours ago, itskamel said:

how do you get it to show you the permissions? mine doesnt show folder permissions. do i have to enable it somewhere?

They are there but the change dialog hides them...

 

[dius]

Since there doesn't seem to be any way to fix what has broken on my Nextcloud installation, I was wondering if I could simply remove it, then add it again.  Would that solve my problem?  

 

For the benefit of anyone reading this, my Nextcloud service was working fine.  I always accessed it using a domain.  Just a couple of days ago, I was notified that there was an update to my Nextcloud docker so I went ahead and updated it.  Nextcloud starts just fine.  There are no errors in the log, however I can no longer access it.  It doesn't  matter if I use the domain or the IP address.  The result is the same. It appears that there may be some kind of certificate issue but I have no idea how to debug it it and fix it.  My thinking is that I may just remove it entirely from my Unraid server, then download and install a new one.  I may lose all of my configurations, and may have to figure out how to get Collabora working again, but that may get me back up and running.

 

Any other recommendations?

 

Any help would be greatly appreciated.

[sonofdbn]

@dius I'm having the same problem. Nextcloud was working fine, today after updating recently my Windows client can't access Nextcloud (which I access via a domain).

 

No errors that I could see in the log but there were these lines:

**** The following active confs have different version dates than the samples that are shipped. ****

**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
/config/nginx/nginx.conf
/config/nginx/site-confs/default.conf

cont-init: info: /etc/cont-init.d/85-version-checks exited 0

 

I don't know much about nginx but I think it's the application that allows the accessing via the domain. So maybe there's a problem here?

[dius]

@sonofdbn

I don't think those lines are significant.  I have seen them from the very first time I started using Nextcloud.  There definite differences in the config files, but that is due to your local setting etc.  I don't know enough about the config options to know if there are any significant changes.  I tried using the new sample config files, but it didn't make any difference.

 

It looks like there may be an incompatible certificate now, but I have no idea how to figure that out.

[sonofdbn]

OK, thanks for that info @dius. Now, I'm very hazy about exactly what it does, but I use Swag (previously Letsencrypt) in conjunction with Nextcloud. The Swag logs seem to be constantly writing this line:

nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3

Maybe that points to something that's relevant to the problem.

[dius]

I wish I knew more about how this worked.  I am seriously thinking about just deleting Nextcloud from my UnRaid server and starting over, but I'm not sure if that will solve anything.  I'd like to get some other opinions first before I take such a drastic step.

[alturismo]

12 hours ago, sonofdbn said:

Maybe that points to something that's relevant to the problem.

exactly, take a look at the last 20 posts in the swag support thread, been handled there already ...

 

14 hours ago, dius said:

I don't think those lines are significant.  I have seen them from the very first time I started using Nextcloud. 

that is not always true as you see upper, from time to time you should update those config files ...

 

here there was ~ 1 year time now until it really broke it, manual changes in the conf wont give this note, its the header (date versioning) which triggers the update notification ... so sometimes it makes sence to compare and update them

 

or wait until it crashes and then read the logs from all in the chain (in the upper case swag) and fix it.

[sonofdbn]

Thanks so much! Got Nextcloud working again.

 

What I did after reading the Swag support thread and after stopping Swag:

1. Went to my Swag folder in /mnt/appdata

2. Went to the nginx sub-folder

3. Renamed ssl.conf to ssl.conf.old and nginx.conf to nginx.conf.old (in case something went wrong)

4. Made a copy of ssl.conf.sample and named the new file ssl.conf

5. Made a copy of nginx.conf.sample and named the new file nginx.conf.

6. Restarted Swag.

 

NOTE: I didn't have any customisations in the ssl.conf and nginx.conf files.

(I can't claim any credit for this - all taken from the Swag support thread)

[vitis]

On 12/12/2022 at 11:01 PM, gzibell said:

Oh it totally works. The learn more says, "It is highly recommended to restrict WOPI requests to the IP addresses of the Collabora servers that are expected to request files from the Nextcloud installation. This can be done by setting the Allow list for WOPI requests option from the Office admin settings."

 

So I think it means someone could use WOPI to grab files from my nextcloud instance without permission and I need to only allow ip's that should be allowed to access wopi.  I tried local IP's and that didn't work.  Assuming it would have to be my public or cloudflare proxied ip but haven't tried those yet

 

Did you sort this out? I tried in the allow list these - local docker network IP, server IP, my public IP and IPs from my Cloudflare proxied domain. All of those got me rid of the warning but Collbora was not working.

 

Solution:

Add all Cloudflare IPs to the allow list

Source: https://github.com/nextcloud/all-in-one#notes-on-cloudflare-proxytunnel

Edited January 29 by vitis
Solution found

[tazire]

I'm interested in using one of my raspberry pi's as a quick spin up backup server. I'm just curious if anyone is doing anything similar or is it even possible?

 

I have backups to B2 etc but I'd like to be able to just spin up the raspberry pi and practically instantly be back up and running again. 

[dius]

8 hours ago, sonofdbn said:

Thanks so much! Got Nextcloud working again.

 

What I did after reading the Swag support thread and after stopping Swag:

1. Went to my Swag folder in /mnt/appdata

2. Went to the nginx sub-folder

3. Renamed ssl.conf to ssl.conf.old and nginx.conf to nginx.conf.old (in case something went wrong)

4. Made a copy of ssl.conf.sample and named the new file ssl.conf

5. Made a copy of nginx.conf.sample and named the new file nginx.conf.

6. Restarted Swag.

 

NOTE: I didn't have any customisations in the ssl.conf and nginx.conf files.

(I can't claim any credit for this - all taken from the Swag support thread)

Wow! I was only having problems accessing Nextcloud, so it never occurred to me to look at Swag.  I followed these instructions, and also update my customized Nextcloud  conf files and now everything is working.  Thank you @sonofdbn for pointing this out to me.

 

I'll try to remember to update the appropriate config files going forward.

[Kilrah]

9 hours ago, tazire said:

I'm interested in using one of my raspberry pi's as a quick spin up backup server. I'm just curious if anyone is doing anything similar or is it even possible?

 

I have backups to B2 etc but I'd like to be able to just spin up the raspberry pi and practically instantly be back up and running again. 

In theory you can IF all your services have ARM images available, you make docker-compose files or such to spin up containers in a way that matches your setup, you don't have too many services because RAM on a Pi is limited, and... you're patient, since most stuff will run atrociously slow on a Pi.

 

You can get used business PCs for $50 (cheaper than a Pi these days)  that will run circles around a Pi and would be able to run your usual OS.

Edited January 28 by Kilrah

[tazire]

14 hours ago, Kilrah said:

In theory you can IF all your services have ARM images available, you make docker-compose files or such to spin up containers in a way that matches your setup, you don't have too many services because RAM on a Pi is limited, and... you're patient, since most stuff will run atrociously slow on a Pi.

 

You can get used business PCs for $50 (cheaper than a Pi these days)  that will run circles around a Pi and would be able to run your usual OS.

cheers for the response. The particular pi would be solely to run nextcloud & mariadb... just the vital containers for nextcloud to continue to function. I wouldnt need onlyoffice or any of the other addons for this. Its just to keep it going should my server ever go down for whatever reason. I would have swag/NPM on its own pi also so I can keep the load to just nextcloud related. I could also go the k3 route as I have 4 pi 4 4gb's that I have been playing with.   

 

Both my nextcloud and mariadb are linuxserver (obviously!) repo images. So if they support arm it should be as simple as setting them up on my pi and have the unraid files rsync to the pi? 

Edited January 29 by tazire

[Kilrah]

21 hours ago, tazire said:

Both my nextcloud and mariadb are linuxserver (obviously!) repo images. So if they support arm it should be as simple as setting them up on my pi and have the unraid files rsync to the pi? 

For the files yes, for the DB maybe / maybe not, don't know if the way the data files' structure depends on CPU arch on mariadb so it might need exporting/importing. 

[Archonw]

I did this the opposite way. Restore my mariadb dump from my pi to an x86 docker version. So it should also work the other way round.

Gesendet von meinem Pixel 6 Pro mit Tapatalk

[DrBobke]

Hi everyone, I have been running an own Nextcloud instance for over a year, protected by a reverse proxy SWAG, setup like SpaceInvader one's channel.  Everything has been working great (except for last week, when I also had an issue with SWAG, which luckily was sorted thanks to this forum above here!).

 

However, I am sharing a lot of photos and personal videos with family and friends and I often get the feedback that they can't download things from my Nextcloud, which is larger in size (it appears that anything below around 2Gb is fine, but above it times out). I did read some comments on the forum, that it would be SWAG which is the bottleneck, but there doesn't seem to be a solution. So I am using Nextcloud, MariaDB, DuckDNS and Swag.  So not sure where the issue lies, but I want to solve this quickly.

 

Anyone else that has this issue and maybe some kind of explanation why this is happening/how to solve it?

 

Thanks in advance,

best regards,

DrBobke

[avinyc]

On 2/1/2023 at 8:12 AM, DrBobke said:

Hi everyone, I have been running an own Nextcloud instance for over a year, protected by a reverse proxy SWAG, setup like SpaceInvader one's channel.  Everything has been working great (except for last week, when I also had an issue with SWAG, which luckily was sorted thanks to this forum above here!).

 

However, I am sharing a lot of photos and personal videos with family and friends and I often get the feedback that they can't download things from my Nextcloud, which is larger in size (it appears that anything below around 2Gb is fine, but above it times out). I did read some comments on the forum, that it would be SWAG which is the bottleneck, but there doesn't seem to be a solution. So I am using Nextcloud, MariaDB, DuckDNS and Swag.  So not sure where the issue lies, but I want to solve this quickly.

 

Anyone else that has this issue and maybe some kind of explanation why this is happening/how to solve it?

 

Thanks in advance,

best regards,

DrBobke

 

Look in your proxy configuration file "nextcloud.subdomain.conf"

 

You can increase the file size limit.  Mine shows as follows "proxy_max_temp_file_size 2048m"

 

Change it to 4096m if you just want to double it to 4gb, or set any higher number and see if that helps resolve your timeouts.

Edited February 2 by avinyc

[DrBobke]

On 2/2/2023 at 2:35 PM, avinyc said:

 

Look in your proxy configuration file "nextcloud.subdomain.conf"

 

You can increase the file size limit.  Mine shows as follows "proxy_max_temp_file_size 2048m"

 

Change it to 4096m if you just want to double it to 4gb, or set any higher number and see if that helps resolve your timeouts.

Thanks a lot for your comment and apologies for the late reply. I have been looking in my nextcloud and under appdata, but I can't seem to find the nextcloud.subdomain.conf file. Is this under appdata --> Nextcloud --> ??

 

Looking forward to your reply and hoping to solve this issue. 🙂

 

Best regards,

 

Robert Smits

 

[Kilrah]

15 minutes ago, DrBobke said:

I have been looking in my nextcloud and under appdata, but I can't seem to find the nextcloud.subdomain.conf file. Is this under appdata --> Nextcloud --> ??

They said "in your proxy configuration file" so that would be the config file for nextcloud in swag if that's what you're using.

[levster]

I am having issues syncing my nextcloud files by constantly getting the "No connection to Nexctloud at https://... Timeout". I cannot get into the WebUI nor does the desktop application work until I restart the docker.  Once the docker is restarted, the WebUI and the desktop app work fine, for some time, and then the entire process repeats. This seems to happen when I am syncing large files. Can anyone point to where I should troubleshoot?

 

Thanks,

 

Lev

 

[levster]

On 2/20/2023 at 5:12 PM, levster said:

I am having issues syncing my nextcloud files by constantly getting the "No connection to Nexctloud at https://... Timeout". I cannot get into the WebUI nor does the desktop application work until I restart the docker.  Once the docker is restarted, the WebUI and the desktop app work fine, for some time, and then the entire process repeats. This seems to happen when I am syncing large files. Can anyone point to where I should troubleshoot?

 

Thanks,

 

Lev

 

 

I noticed that when my Nextcloud docker is active, the overall load on the server CPU is in the 70 - 90 %. There is tremendous amount of outbound traffic, and some disks show 10,000,000 to 100,000,000's reads! And they go nonstop, even when the remote clients crash and the Nextcloud WebUI stops responding. As soon as I restart the docker, the server activity drops precipitously, and disk utilization also stops. Also, I noticed that if I manually exit out of all remote clients, the server activity does NOT stop. There is still high disk and CPU utilization.