4 hours ago, Professor Oak said:

My nextcloud server has been having a lot of issues lately. My unraid server had all of its cores pegged to 100% from the nextcloud container and I saw this in the error.log file. What would be causing this and how can I get my server back to functioning properly?

It may not be the same issue, but when I upgraded to last week's LSIO image, I had two cores pegged at 100% due to a PHP process.

I checked the Admin dashboard shortly after updating, and the security checks never stopped loading. I think it was the security checks that kicked off some process that wasn't ready to be run so shortly after the update.

I restarted the Docker container and everything has been fine since.

This looks different to my error, but it might be worth restarting to see if it's related.

I updated to the latest version of Nextcloud and I have an issue that I can't figure out how to fix. It will start and work like normal, but when I am on the iPhone app, I go to the Media tab and some photos load but then it gets to a section where it does not load and it freezes the whole container.

Has anyone else experienced this? I will restart the container and it will start working again.

On 3/11/2026 at 1:15 AM, Tucubanito07 said:

I updated to the latest version of Nextcloud and I have an issue that I can't figure out how to fix. It will start and work like normal, but when I am on the iPhone app, I go to the Media tab and some photos load but then it gets to a section where it does not load and it freezes the whole container.

Has anyone else experienced this? I will restart the container and it will start working again.

I have the same problem. I access Nextcloud through the web using my own domain, and when I go to the Photos or Memories section, I get the same issue as you. Did you find any solution? Thanks.

I think you're getting throttled. Check your Nextcloud logs to confirm.

I had an issue with my (third party) Photos app on Android being throttled by the Nextcloud intrusion detection.

The only solution I found was to whitelist my local network. It's a blunt solution, but it allowed me to use the photos app (at least its initial sync) from my local LAN without issue. I didn't have the time to figure out how to solve it properly.

You can set it via Administration Settings > Security.

Edited April 1Apr 1 by jademonkee

On 10/12/2025 at 9:25 PM, kSmKcW9XJ1yCN2ejHX3s said:

Hello, i have the same problem

i set as docker parameter /mnt/user/daten/daten/ -> Container Path: /mnt/daten
In administrator settings i configured "external storage", available for all people.
With my user (kai) logged in from Android Phone and i configured automatic picture upload.
These Pictures have owner nobody and permission 640. What i expected and need was owner "kai" and permission 660 or 666.


Does anybody have a hint, how i can change this behavior?

i will anser me by myself.

i found out, that right for users and groupds are ok, but ACL were blocking
getfacl on the files:
group:users:---
getfacl on the directory:
default:group:users:---
so i changed it for the folders, were i automatically upload pictures from Nextcloud android App to this:
setfacl -m g:users:rw on the files:
group:users:rw-
setfacl -d -m g:users:rw on the directory:
default:group:users:rw-

first test was ok now.

Running into a Tailscale hook issue. When running tailscale within the container, I'm getting a 0.0.0.0:443 bind error; 443 in use. in the nextcloud container logs. I assume this is because both Tailscale Serve and Nextcloud are using this internal port mapping.

I cannot change the internal port of Nextcloud (443). I tried changing the Tailscale Serve Port to 8443, but the same issue persisted. I can get it to work by changing the Tailscale Serve Protocol Port to 80 (default is 443); but then you get the http warnings, which defeats the purpose of a tailscale serve DNS address I'd think.

What is my best solution to get this working properly with Tailscale sidecar/hook. (I have other containers successfully deployed using tailscale hook, but none of them run a default internal port 443)

21 hours ago, mikescott said:

Running into a Tailscale hook issue. When running tailscale within the container, I'm getting a 0.0.0.0:443 bind error; 443 in use. in the nextcloud container logs. I assume this is because both Tailscale Serve and Nextcloud are using this internal port mapping.

I cannot change the internal port of Nextcloud (443). I tried changing the Tailscale Serve Port to 8443, but the same issue persisted. I can get it to work by changing the Tailscale Serve Protocol Port to 80 (default is 443); but then you get the http warnings, which defeats the purpose of a tailscale serve DNS address I'd think.

What is my best solution to get this working properly with Tailscale sidecar/hook. (I have other containers successfully deployed using tailscale hook, but none of them run a default internal port 443)

Figured this out for anyone having a port binding conflict in future with tailscale hook and a container both listening on 443. Despite me changing the port mapping variable, you have to toggle on Advanced View and also update the Web UI: https://[IP]:[PORT:8443] part as well. Once I did this, everything worked.

I guess this was first container I've had to change the port mapping on, so I thought the Web UI path under Advanced View would have updated automatically to match the WebUI port mapping configured in the template, but it does not. Lesson learned.

Edited May 1May 1 by mikescott

On 6/24/2025 at 2:50 AM, Geck0 said:

Why would you move it, when you can just rename the folder?

I've only briefed through this, so some of it may be assumption. I've pulled back from responding on this thread as I've realised people want the answer, but don't want to look for it. I started like you, and learned from mistakes and trial and error.

1. Always have backps of important data. Don't know why you would want cloud storage backup, which goes against the idea of having NC in the first place. To answer your question though, yes you can backup to cloud storage, you don't connect it through Nextcloud, you use a utility like rClone and script it to backup to the cloud.

2. It sounds like you're not familiar with Nextcloud's workings. So, upgrading from 27 to 30 will be slightly difficult for you, as the database needs an upgrade as well between 29 and 30 if I recall. You can do it, by searching through this forum. It was raised this year, as a few people were having problems.

3. You can keep your configuration, as long as you retain your config.php file, which doesn't get overwritten when you upgrade.

4. When you upgrade, you do it by changing the docker's lable to the desired version. I would suggest doing this first and stepping through the major versions. You don't have to upgrade every single release. But, when you get to v.30 you will need to upgrade your database's tables, which people have strugled with. So, if you're going to upgrade, only go up to v29 first by upgrading versions. ie. v 27 ---> v.27.5 ---> v 27.9---> v. 28 ---> v 28.5 ----> v 28.9 ---> v 29 ---> v 29.9 (whatever the last version is of 29). Hopefully, you get the idea.

5. (Alternatively), you can drop your NC and your database, delete the appdata folders for both from your appdata folder and start again at v30. What I can't tell you is if you're going to have to update the tables manually anyway. So, you might as well do point 4 and learn something.

6. You're not going to lose your data during an upgrade, unless you do something stupid. NC references your data, it does't manipulate it. What would it mean to you, if you lost the data now? If you think you would have that sinking feeling, where your balls are in your throat, then it means something to you. So, back it up. Drives fail all the time, unRaid has redundency, but thats not the same as a backup and you can still lose your data.

7. There have been several instances on this thread where people don't know how to upgrade correctly and its been responded to many times. I suggest you go and look at those first, search under my username because I've responded to examples like this several times.

8. If you're really concerned, then create a second instance of NC and database, with the lastest version, referencing a new data folder. Once that is up and running, you can move your data over from old folder to new folder and tell NC to re-scan the files. You won't have any data from your calendar, deck, messenger, etc as that's in the old database, but if your only concerned about your files, then you could start there. After that's done, you can drop your old NC and Dataase from docker and appdata.

9. Be careful of bad advice.

Almost after close to an year or so , with the help of chatgpt , i was able to upgrade from 27 to 33 .. Thanks for your guide , i was able to follow it to the core .. updated each version . Chatgpt helped me check the DB after every update and also asked me to check the logins , admin page etc. The update ran pretty neatly.
I was able to do this because i purchased a 16TB hdd recently and was about to add it to the pool , then thought instead of external hdd , i will use this hdd to backup. Backup did take lot of time . Chatgpt was fed with your post.. it created all the needed commands to backup all important things , verify it as well. We didnt backup preview cache , as it was huge and took so much time because of small size files.

Now all that is good , IT also me helped me clear few admin errors like HTHS , localization error and redirect errors.

Thanks for the guide you provided.

If anyone is interested , i can ask chatgpt to create the list of commands and how i did .

Nextcloud adding Redis. (Due to recommendations in the Security and Setup Warnings).

Installed Redis and edited Nextcloud's config.php.

Added the following lines to the config.php.

<?php

$CONFIG = array (

'memcache.local' => '\\OC\\Memcache\\Redis',

'memcache.locking' => '\\OC\\Memcache\\Redis',

'redis' =>

array (

'host' => '192.168.1.10',

'port' => 6379,

),

But when I stop and start Nextcloud, I just get the following error:

The server encountered an internal error and was unable to complete your request.

It is supposed to be easy to integrate. :-) What am I missing?

5 hours ago, RaidPC said:

Nextcloud adding Redis. (Due to recommendations in the Security and Setup Warnings).

Installed Redis and edited Nextcloud's config.php.

Added the following lines to the config.php.

<?php

$CONFIG = array (

'memcache.local' => '\\OC\\Memcache\\Redis',

'memcache.locking' => '\\OC\\Memcache\\Redis',

'redis' =>

array (

'host' => '192.168.1.10',

'port' => 6379,

),

But when I stop and start Nextcloud, I just get the following error:

The server encountered an internal error and was unable to complete your request.

It is supposed to be easy to integrate. :-) What am I missing?

Here is my redis

'memcache.local' => '\\OC\\Memcache\\APCu',

'memcache.distributed' => '\\OC\\Memcache\\Redis',

'memcache.locking' => '\\OC\\Memcache\\Redis',

'redis' =>

array (

'host' => '192.168.1.127',

'port' => 6379,

'password' => 'xxxx',

),

I think you miss the password

Edited June 3Jun 3 by deadnote

Appreciate the idea, but my install of Redis from the Community Apps, the "Official Redis" did not have a field for a password. I saw a video where one version does require a password; but this one does not.

Then check your networking setup actually allows them to talk to each other

8 hours ago, deadnote said:

Here is my redis

'memcache.local' => '\\OC\\Memcache\\APCu',

'memcache.distributed' => '\\OC\\Memcache\\Redis',

'memcache.locking' => '\\OC\\Memcache\\Redis',

'redis' =>

array (

'host' => '192.168.1.127',

'port' => 6379,

'password' => 'xxxx',

),

I think you miss the paddword

I added a static IP to the Redis docker and it now "appears" to work. It opens and there is no longer a security & setup warning about Transactional File Locking. Outside of that I assume it is working, not sure how to tell for sure.

But in my config.php, I have an entry 'apps_paths' =>. Seems to be misplaced now. Where does it go.

Attached are my original config and the modified one.

Looks fine, you just didn't indent the new block the same way

Hello! I've been running Nextcloud for a while now.

For some time now (2 months) Nextcloud becomes unreachable after ~2days (no error in Container logs), CPU goes to 100%.

After Container Restart everything works fine again (with CPU at normal level, Nextcloud reachable).

any ideas why this would happen?

best regards

On 5/29/2026 at 7:37 AM, pika said:

Hello! I've been running Nextcloud for a while now.

For some time now (2 months) Nextcloud becomes unreachable after ~2days (no error in Container logs), CPU goes to 100%.

After Container Restart everything works fine again (with CPU at normal level, Nextcloud reachable).

any ideas why this would happen?

best regards

I also have this issue since updating

I've been seeing issues with my disks spinning up and after using the Files Activity tool it looks like Nextcloud (News app) is causing it. It seems like the NC apps create and use a "appdata_<some_id>" directory in the /data container, which (best I can tell) is used for temporary application data with a lot of reads and writes. Since the /data folder is also for all of the user data, I have it mapped to my array, which is the reason for the disks to keep spinning up.

I did some digging and it looks like the NC AIO container has a "NEXTCLOUD_DATADIR" environment variable that can be set to address this.

https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir

I tried setting that with this container but it doesn't work. Anyone tried this or have any suggestions? I know I could use a different news reader, but it seems like this affects all of the NC apps. :)

NEXTCLOUD_DATADIR is about specifying another location for the whole "/data" folder so won't help you.

You can just add an extra mount to the container for the specific dir you want somewhere else.

Edited June 26Jun 26 by Kilrah

Thanks @Kilrah . I was considering that , but according to this post, that folder name is random and I'm not sure it it might change, so mapping it might be a problem (at some point).

Nextcloud community

What is the appdata_ocpom4nckwru directory?

Its a quick fix to keep app related data (such as configuratin files or caching) in data/ since data/ has user ids as sub folders, adding an appdata folder would make a user appdata owner of that di

Its a quick fix to keep app related data (such as configuratin files or caching) in data/

since data/ has user ids as sub folders, adding an appdata folder would make a user appdata owner of that directory. So they simply append a random hash at the end.

6 hours ago, urmyboyblue said:

I was considering that , but according to this post, that folder name is random and I'm not sure it it might change, so mapping it might be a problem (at some point).

It is random at creation but it won't change. You can see it matches the instanceid in your config.php.

Ah gotcha. Thanks again @Kilrah ! I'll try the extra mount and see how it goes.