Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. ![]()
The Basics
- Nextcloud Server version (e.g., 29.x.x):
32.0.6
- Operating system and version (e.g., Ubuntu 24.04):
docker v32
- Web server and version (e.g, Apache 2.4.25):
docker v32
- Reverse proxy and version _(e.g. nginx 1.27.2)
nginx
- PHP version (e.g, 8.3):
docker v32
- Is this the first time you’ve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
after update from v32.0.5 to v32.0.6 but not sure this problem is related to update
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
docker-compose
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
no
Summary of the issue you are facing:
I had an update three days ago on my docker container of Nextcloud from 32.0.5 to 32.0.6. After that I received some problems in of the team folders (group folder) that the folders that have external sharing cannot shows the files.
In admin config page all the permission was granted to the team folder (Write/Share/Delete) but in files section all of these permission was blocked in main group folder. I granted all the permission to the related folder here:
Advanced permissions for Team folder
| Read | Write | Create | Delete | Share | |||
|---|---|---|---|---|---|---|---|
then the external shares worked but some users tried to remove lots of folders inside team folder. I think the desktop sync app did the deletion automatically.
The question is why the sync apps tried to remove the contents inside the team folder and how can I prevent this? at the moment I blocked the Delete permission on the team folder and restore the files.
Steps to replicate it (hint: details matter!):
-
Update NC v32.0.5 to v32.0.6
-
changed the advanced permissions for team folder
-
Some files automatically removed by desktop sync app
Log entries
Nextcloud
Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.
there is not logs for this in nesctloud.log and also I checked activity_logs table in database and there was no logs there.
Web Browser
If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.
PASTE
Web server / Reverse Proxy
The output of your Apache/nginx/system log in /var/log/____:
PASTE HERE
Configuration
Nextcloud
The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):
PASTE HERE
Apps
The output of occ app:list (if possible).
Tips for increasing the likelihood of a response
- Use the
preformatted textformatting option in the editor for all log entries and configuration output. - If screenshots are useful, feel free to include them.
- If possible, also include key error output in text form so it can be searched for.
- Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.