Skip to content
SHC Docs

Nextcloud

These answers used to sit on this app’s store listing. They moved here on 2026-08-17: a shopper deciding whether to install is not reading six hundred words of Q&A, and the listing page is the pitch. The knowledge is no less true for being off the storefront: it is the part you want before you commit, which is what a guide is for.

Yes. Nextcloud keeps every file in an S3 bucket, its primary object store, and the install is refused without an s3 integration or vars.s3.endpoint. SHC ships no S3 server of its own. Make a bucket at a hosted provider (Backblaze B2, Hetzner Object Storage, Cloudflare R2 or any S3-compatible service), connect its key as an s3 connection, and bind the s3 plug to it, straight with -i s3=@<connection> or through an external-s3 front. See Object storage for apps.

No. Single sign-on is optional and inert until an OIDC integration is attached. Without one you get the built-in admin account and Nextcloud’s own user management, and none of the SSO configuration is written.

Can I use MySQL or MariaDB instead of PostgreSQL?

Section titled “Can I use MySQL or MariaDB instead of PostgreSQL?”

Yes, but PostgreSQL is the default and the tested path. The MySQL variables exist for migrations from other self-hosting platforms; leaving them empty keeps Nextcloud on PostgreSQL.

What happens to my users if I move from another Nextcloud host?

Section titled “What happens to my users if I move from another Nextcloud host?”

The package detects a login app it does not own and stops, because user identifiers are derived differently by different login apps and silently switching would strand every account’s files. You then choose to adopt the existing provider (identity-preserving) or replace it.

The next start installs it again. A first start that stops inside Nextcloud’s installer, from a crash or a database connection cut mid-install, leaves a tree the upstream image cannot start from: every later start exits in its .htaccess step. Before the image runs, the package looks for exactly that state, a config.php that names a database but was never marked installed. It drops the tables that install wrote, moves config.php and the leftovers into data/.shc-partial-install-<time>, and lets the image install from scratch. It refuses, and the start fails with the reason in the replica’s log, when the database holds what only a finished install writes: an account besides the admin, the install’s own background jobs, a cron run or a login. A database left by an earlier half-finished install is cleared the same way, so a retry after a rolled-back install works too. A finished install is never touched.

Yes. This is the upstream Nextcloud image on a tracked major, with configuration and integration wiring around it. There is no fork and no patched build.