The source fix worked because it separated two different things: the Nextcloud container and its persistent AppData. Removing/recreating the container did not reset the configuration that Nextcloud inherited on the next install. Once the old AppData was removed as well, the original poster confirmed that the clean reinstall worked.
That does not mean current users should delete an AppData folder blindly. Nextcloud AppData can contain configuration, database state, keys and application data depending on how the package is built. Back up anything important, inspect the current host volume mappings, and delete only the confirmed Nextcloud configuration tree if your explicit goal is a fresh start.
Why Reinstalling the Container Did Not Reset Nextcloud
Docker containers are disposable runtime instances. ZimaOS maps persistent host folders into them so configuration survives upgrades and container recreation.
Therefore reinstalling the same package can recreate a fresh container that immediately reads the same broken configuration again.
Why Portainer Did Not Fully Clean the App
The source user tried Portainer. Removing a Docker container from Portainer does not automatically delete every bind-mounted host directory. The AppData state remained outside the container lifecycle.
The Source-Confirmed Recovery Was Container Removal Plus AppData Cleanup
The community sequence was:
- uninstall Nextcloud from the ZimaOS App Store;
- identify its persistent AppData folder;
- back up anything you may need;
- remove the broken AppData if a truly clean reinstall is intended;
- install Nextcloud again.
The OP replied “worked fine,” which confirms the source procedure fixed that specific misconfiguration.
AppData May Not Be Writable from the Normal Files UI
The community reply noted that AppData was system/root-owned in the source, so the normal UI user could not delete it. That does not justify broad chmod -R 777 or changing the ownership of the entire AppData tree.
Use the current supported app-data/uninstall controls where available or a narrowly scoped admin operation on the exact app folder.
Current ZimaOS Explicitly Separates Containers and Persistent Host Paths
IceWhale's current app-storage documentation explains where app data, media and cache live and lets users inspect the host/container volume mappings.
Use the current ZimaOS app-storage model.
Nextcloud Can Be More Than One Container
Some Nextcloud packages include or depend on separate database, Redis or AIO-managed containers. If you are troubleshooting a multi-container deployment, identify every persistent database/config path before deleting anything.
Do not assume deleting one Nextcloud folder automatically resets an external PostgreSQL/MariaDB database.
Make the Destructive Step Explicit
If the old Nextcloud instance contains any files, users, shares, encryption keys or database state you may need, copy/export it before cleanup. “Fresh install” and “recover old instance” are opposite goals.
Nextcloud Clean Reinstall FAQ
Did uninstalling and reinstalling alone fix the source problem?
No. The persistent AppData kept the misconfiguration.
Did removing the AppData fix the source case?
Yes. The original poster confirmed the cleanup worked.
Should I delete the entire ZimaOS AppData directory?
No. Remove only the confirmed app-specific path after backing up anything important.
