1st of all , when I go to overview in Nextcloud , I get ton of errors There are some errors regarding your setup. WebSocket server URL is not configured. Real-time collaboration requires a separate WebSocket server. Basic whiteboard functionality works without it. For more details see the documentation ↗. Detected some missing optional indices. Occasionally new indices are added (by Nextcloud or installed applications) to improve database performance. Adding indices can sometimes take awhile and temporarily hurt performance so this is not done automatically during upgrades. Once the indices are added, queries to those tables should be faster. Use the command occ db:add-missing-indices to add them. Missing indices: "mailmessagesstrucanalyzidx" in table "mailmessages", "mailaccprovidx" in table "mailaccounts", "mailaliasaccididx" in table "mailaliases", "tablesrowsleevestid" in table "tablesrowsleeves", "systagbyobjectid" in table "systemtagobjectmapping", "mailmessagesmbiduiduidx" in table "mailmessages", "mailsmimecertsuidemailidx" in table "mailsmimecertificates", "mailtrustedsendersidx" in table "mailtrustedsenders", "mailcollidx" in table "mailcolladdresses". For more details see the documentation ↗. SQLite is currently being used as the backend database. For larger installations we recommend that you switch to a different database backend. This is particularly recommended when using the desktop client for file synchronisation. To migrate to another database use the command line tool: "occ db:convert-type". For more details see the documentation ↗. Your web server is not properly set up to resolve .well-known URLs, failed on: /.well-known/webfinger For more details see the documentation ↗. 911 errors in the logs since 1 September 2026, 10:37:12 Server has no maintenance window start time configured. This means resource intensive daily background jobs will also be executed during your main usage time. We recommend to set it to a time of low usage, so users are less impacted by the load caused from these heavy tasks. For more details see the documentation ↗. One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command occ maintenance:repair --include-expensive to perform the migrations. Some headers are not set correctly on your instance - The Strict-Transport-Security HTTP header is not set (should be at least 15552000 seconds). For enhanced security, it is recommended to enable HSTS. For more details see the documentation ↗. And ofc , error that The version you are running is not maintained any more. Please make sure to update to a supported version as soon as possible. I installed onlyoffice , because I want to have shared filed for team , but when I am trying to open file , it start to open on OnlOffice, but with error Error Failed to open the requested file.
6 replies
Chris wrote:
Hi mrga — one thing up front: that block of text on the Overview page is Nextcloud's admin housekeeping list, and none of it is what's breaking OnlyOffice. Let me separate the two. Why OnlyOffice can't open the file The "ONLYOFFICE" app you added inside Nextcloud is only the connector. Opening or editing a document still needs a separate OnlyOffice Document Server — an engine that actually loads, renders and saves the file. SparkBox doesn't install an office document server with the Cloud module (and there's no module for one), so there's nothing behind the app to talk to. When you click the file, the editor hands off to a document server that isn't running on your setup — that's exactly what "Failed to open the requested file" means. No dashboard or Nextcloud settings page can fix that on its own. The two realistic paths 1. Team sharing without OnlyOffice — works right now. Nextcloud shares files and folders natively: pick a file or folder, use the Share action, and either add team members or create a link. They can preview images/PDFs right in the browser and download the rest to edit in their own Office app. If "shared files for team" is the real goal, this is the supported path and needs no extra install. 2. Editing in the browser needs a real document server — you would run an OnlyOffice Document Server (or Collabora) yourself as a separate service, reachable over https, and enter its address plus a matching secret in Nextcloud → Administration Settings → ONLYOFFICE. That's a manual Docker deployment, not a SparkBox toggle, so I'd only suggest it if the sharing path above isn't enough. On the warning list (not the cause) Two lines are worth knowing about; the rest are cosmetic admin tasks you can safely ignore for now (indices, mimetype migrations, maintenance window, HSTS, WebSocket). - "SQLite is currently being used" — SparkBox actually provisions a MariaDB server right next to Nextcloud; this message usually means the first-run setup left Nextcloud on SQLite. Worth fixing eventually (Nextcloud runs far better on MariaDB), but it is not why OnlyOffice fails. - "the version you are running is not maintained" — that's Nextcloud 30 being an older major branch. Nothing to do on your side; it normally clears when SparkBox ships a newer Nextcloud image in a future release. If you want, tell me whether the team needs individual logins or a single share link works, and I'll write out the exact sharing steps.
mrga wrote:
Anyone manage to install Nextcloyd + Onlyoffice on sparkbox ? If you did , please share tutorials. Tnx
Chris wrote:
Good timing — this just changed. v1.6.673 (now available) adds an optional OnlyOffice Document Server to the Cloud module, which is the missing engine the ONLYOFFICE app in Nextcloud needs to actually open and edit files. It's off by default, so after updating: 1. sudo sparkbox upgrade — use upgrade, not update; only upgrade moves the box onto the new release. 2. In Cloud Storage's settings, turn on the new ONLYOFFICE toggle. 3. The Cloud Storage setup guide now documents the ONLYOFFICE app hookup steps (pointing the app at the document server and its auto-generated secret). That gives the ONLYOFFICE app something to talk to, so the "Failed to open the requested file" error should clear. The document server runs on port 8790 and is reachable the same way Nextcloud is. If you'd rather not run a document server, the native Nextcloud sharing path from my earlier reply still works for team sharing today.
mrga wrote:
Stilll didnt all good. I cant open document in Nextcloud .. Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 9.4.0.129) in onlyoffice settings
Chris wrote:
Thanks — that exact error is useful. The good news first: the Document Server is now up and Nextcloud can see it (the 9.4.0.129 version is the new engine responding), so the v1.6.673 piece is working. The remaining error means the Document Server can't pull the file back out of Nextcloud, and on a fresh setup like this that's almost always one quick setting. 1. Missing shared secret (most likely). The Document Server refuses any request that isn't signed with a secret SparkBox auto-generated when you switched it on. Open the SparkBox dashboard → Cloud Storage settings → find the row "Document Server JWT Secret" (it has a reveal/copy button — it is not in Settings → Passwords). Copy it. Then in Nextcloud go to Settings → Administration → ONLYOFFICE, paste that exact value into the Secret key field (the one marked "leave blank to disable"), and save. Nextcloud re-tests the connection straight away — if this was it, the error clears right there. 2. If it still fails after the secret: the Document Server also has to reach Nextcloud over a connection it can trust. Look at the address bar when you're logged into Nextcloud — if it shows a padlock with a "Not secure" warning (or a raw LAN address like https://192.168.x.x:8445), the Document Server refuses that certificate and you get exactly this error. The supported setup is to give Nextcloud a real padlock through the Nginx Proxy Manager and use that hostname everywhere (the guide's step 3 mentions this). Try step 1 and tell me what the ONLYOFFICE page shows after you save. If it still errors, just tell me what your address bar shows when you're in Nextcloud — https padlock, https warning, or http plus an IP — and I'll take it from there. (Noted on our side: the setup guide skipped the secret step, so this cost you an extra trip around.)
Chris wrote:
That error has a fix now, and it needed two things the guide did not tell you. Sorry it took a release to get there. 1. The secret key. After sudo sparkbox upgrade it is listed with your other passwords under Settings → Service Passwords. Paste it into Nextcloud → Administration settings → ONLYOFFICE → Secret key and save. 2. On the same ONLYOFFICE page open Advanced server settings, set "Server address for internal requests from ONLYOFFICE Document Server" to https://sb-nextcloud and tick "Disable certificate verification". That is the address the Document Server uses to fetch your file back from Nextcloud; without it that download step fails with exactly the message you posted. Save, then open a document again. The Cloud guide at https://tomsparkbox.com/guides/cloud-setup now walks through both settings. If it still errors, tell me what the ONLYOFFICE page says after you save.