Brand ownCloud Classic 10 with a Theme App and CSS
Replace ownCloud Classic 10 logos and tune web UI colors with a theme app, while avoiding upgrade and integrity-check pitfalls.
For ownCloud Server Classic 10, build your branding as a theme app and place it in a custom app directory so upgrades are less likely to replace it. Use that theme to replace logos and define CSS colors; there is no general built-in color picker that applies arbitrary brand colors across the web interface. The steps below cover the Classic Server web UI, not ownCloud Infinite Scale.
Verified: ownCloud Classic 10 supports themes as apps. A theme can override CSS, images, templates, and translations. The official developer manual also says the old theme setting in config.php is deprecated in Classic 10. Action: identify your product and version before changing files: this procedure is for ownCloud Server Classic 10.
Depends on your edition: ownCloud’s ownBrander service is a graphical branding option described for Enterprise customers. It can create a web theme and branded clients; access depends on an Enterprise subscription and account eligibility. Action: if you have Enterprise access, ask your ownCloud administrator or account contact whether ownBrander is enabled. Otherwise, use a theme app and validate it on a test instance.
Common misunderstanding: Infinite Scale (oCIS) uses a different web customization model, including its own configuration and theme files. Instructions for an oCIS theme.json do not apply to Classic Server themes. Action: do not copy files or configuration from an oCIS guide into a Classic Server install.
Another common assumption is that changing the logo in a settings screen changes every logo, color, and client automatically. The Classic Server developer manual describes filesystem-based theme overrides; feature availability and client branding depend on edition and method. Action: plan the login page, logged-in header, favicon, and any desktop or mobile clients as separate checks.
Back up your instance and test on a staging copy first. Record the ownCloud version, PHP/runtime packaging, app directories, web server user, and current theme-related configuration. The official manual recommends storing custom themes in a custom app directory to reduce the chance of losing them during upgrades. Action: locate your configured custom app directory, or use the documented apps-external directory where available; do not assume every package uses the same path.
A theme app needs an appinfo/info.xml file with an app ID matching its folder, a <theme/> type, and an ownCloud dependency range. The developer manual’s example uses Classic 10 as both the minimum and maximum version. Adjust this for the versions you actually support rather than copying a range blindly. Action: begin from ownCloud’s official theme-example and review its current files before adapting it.
For example, a theme directory might be named theme-acme and contain appinfo/info.xml, core/css/styles.css, and image overrides under paths that mirror the corresponding ownCloud paths. The directory name and the <id> value must agree. Action: keep the theme under version control and use a unique ID to avoid collisions with installed apps.
To override an image, preserve its relative path inside the theme. For example, the login logo’s default path is core/img/logo-icon.svg, so the theme override belongs at theme-acme/core/img/logo-icon.svg. The manual lists other image paths and notes that favicon handling should include both SVG and PNG overrides. Action: inspect the current installation’s assets and reproduce the relevant paths inside your theme instead of replacing core files.
To override colors, create core/css/styles.css in the theme. The official manual documents selectors such as #body-login for the login background and #body-public #header for the logged-in header. A minimal example is:
#body-login {
background: #17324d;
}
#body-public #header {
background-color: #17324d;
}
This changes those documented areas; it is not a complete brand palette for every app, dialog, or third-party interface. Action: use browser developer tools on your own instance to identify the intended component, then add narrowly scoped CSS rules to the theme stylesheet. Avoid broad selectors that can make text, buttons, or focus states unreadable.
Use a logo variant that fits the existing space, and check contrast for normal text, links, controls, and keyboard focus. The exact selectors and asset dimensions can vary with the installed version, theme, and apps. Action: compare your overrides with the current DOM and assets on staging rather than assuming an old selector still matches.
After placing the theme in the correct app directory and setting ownership so the web server can read it, enable it with the installation’s occ command. The official manual gives docker compose exec owncloud occ app:enable theme-acme as a Docker example; non-Docker installations should use their own supported command context. Themes can also be enabled from the Admin Apps screen where they appear among disabled apps. Action: follow the command form for your deployment and confirm the app ID matches the directory and metadata.
A private theme may not have a Marketplace signature. ownCloud documents adding its app ID to integrity.ignore.missing.app.signature when needed to avoid the missing-signature warning. This exception is specific to the unsigned private theme; it does not mean integrity checking should be disabled globally. Action: add only the theme ID to the documented allowlist if your installation reports that warning, and preserve all other integrity protections.
The theme app’s file permissions must allow the web server to read the files. Exact user and group names differ by package and host; the documentation’s www-data example is not universal. Action: check the running service’s actual account and set ownership narrowly for the theme directory.
Open the login page in a private browser window, then sign in and inspect the header, navigation, file list, settings pages, and smaller viewport sizes. Confirm the logo is sharp, text remains readable, focus indicators remain visible, and no controls disappear into the background. The manual recommends testing in a live development environment and using browser inspector tools to try CSS changes. Action: test those paths on staging first, then repeat after deployment with a clean browser cache.
If nothing changes, check that the theme app is enabled, the directory is inside a scanned app path, the relative filenames match the defaults, and the CSS selector still matches the page. Check ownCloud and web server logs for loading or permission errors. Cached CSS or browser assets may delay visible updates. Action: clear the browser cache or use a private window after confirming the files and app status; do not delete production data or disable integrity checks as a troubleshooting shortcut.
Finally, retest the theme after every ownCloud update. Core markup and asset paths may change, so custom CSS can become ineffective or conflict with a new interface. The manual establishes the theme-app approach, but it does not guarantee that every override remains compatible across releases. Action: keep a rollback copy, compare your theme against the release you are upgrading to, and remove obsolete overrides only after testing.
Replace ownCloud Classic 10 logos and tune web UI colors with a theme app, while avoiding upgrade and integrity-check pitfalls.
Assign byte-based storage limits to new ownCloud Infinite Scale users by role, with a proxy.yaml example and a safe verification checklist.
Restore ownCloud desktop syncing by checking the server hostname, certificate chain, private CA trust, and captive portal issues without disabling TLS verification.
Use the invalid-file report to identify mismatched core files or app signatures, restore the correct release files, and verify the integrity check safely.
Deploy ownCloud Infinite Scale from its official Compose example, configure domains and persistent storage, then verify TLS, containers, and first login.
Set up the S3NG driver, bucket permissions, persistent metadata storage, and upload sizing so ownCloud Infinite Scale can store file contents reliably.
Find why an ownCloud Server upload stops near completion by checking file status, quota, temporary disk space, PHP limits, and proxy timeouts.
Set AllowOverride All only for ownCloud’s web root, validate the active Apache vhost, and reload safely to restore .htaccess rules.
Enable ownCloud’s Enterprise Auditing app, route admin_audit events to a protected log file, and confirm that real user actions are being recorded.
Align Keycloak’s realm issuer, web client, and user claims to let ownCloud Infinite Scale sign users in reliably across the web and mobile clients.