Euro-Office

Euro Office Document Server - a sovereign, European document server for browser-based editing of text documents, spreadsheets and presentations. It is a maintained fork of the OnlyOffice Document Server, so it speaks the same WOPI and OnlyOffice APIs and plugs straight into OpenCloud (and Nextcloud/ownCloud). Use it to edit .docx / .xlsx / .pptx and .odt / .ods / .odp files right in your browser, without any desktop office suite. This is a thin wrapper (github.com/junkerderprovinz/euro-office) around the official image. It lets OpenCloud show the editor under OpenCloud's own address, serves https out of the box for other clouds, and replaces the vendor's start page with one that shows what to enter in OpenCloud. This is not a standalone app. It is the editor behind a file server: you point your cloud (e.g. the OpenCloud container) at it and edit the files stored in that cloud. On its own it only shows its start page. How it fits together (with OpenCloud): • Install this container. Set a JWT secret below and remember it. • Click the WebUI button. The page that opens says whether the editor is ready and lists the three OpenCloud fields. • In the OpenCloud template set "Web office suite" = euro-office, "Office document server URL" = http://[THIS-SERVER-IP]:9900 (the address the WebUI button opened) and "Office WOPI secret" = the same value as the JWT secret here. • The New button in OpenCloud now offers documents, spreadsheets and presentations, and existing Office files open in Euro Office. OpenCloud shows the editor under its own address, so there is no certificate to accept. This needs the OpenCloud container from version 1.4.0 on. Seafile: • In the Seafile template set "Web office suite" = euro-office, "Office document server URL" = http://[THIS-SERVER-IP]:9900 and "Office JWT secret" = the same value as the JWT secret here. This needs the Seafile container from version 1.1.0 on. • Seafile loads the editor straight from Euro Office. If you open Seafile over https, use the https address here instead, as described for Nextcloud below. • Euro Office needs about 5 GB of memory while it starts. With a lower memory limit it may never finish starting. Nextcloud or ownCloud: • They load the editor straight from Euro Office, so give them the https address, https://[THIS-SERVER-IP]:9943 (HTTPS Port under Advanced View), and accept the certificate warning once on every device. Euro Office creates that certificate itself on the first start; "Own certificate" below avoids the warning. First start: • The document server bundles its own database and converter and takes a minute or two to come up on the very first start. Its start page says when it is ready. • Leave the "Database" and "Logs" fields under Advanced View blank. Neither is required, and mounting a fresh empty folder over either one hides a directory the image ships pre-built, which stops the container from starting (see Troubleshooting below). Security / reverse proxy: • Keep "Enable JWT" = true (the default). The JWT secret signs every request between your cloud and the editor, so never leave it blank. • With OpenCloud, Euro Office needs no reverse proxy and no port opened to the outside: OpenCloud passes it through. Only OpenCloud has to be reachable. • "Allow self-signed upstream" is true by default because OpenCloud on Unraid serves a self-signed certificate. Set it to false only when your cloud has a valid certificate. Own certificate: • Put the certificate and its private key into the Certificates folder (default /mnt/user/appdata/euro-office/certs), then set "TLS certificate" = /certs/cert.pem and "TLS private key" = /certs/key.pem under Advanced View. Unraid's combined *_Unraid_bundle.pem works too: copy it in and enter that one file in both fields. The key must not be passphrase-protected. • After Apply the container log shows "SSL enabled with cert=/certs/...". If it still names /var/www/euro-office/Data/certs, one of the two paths is wrong and Euro Office fell back to its own certificate. Troubleshooting - container loops "PostgreSQL ... is not accessible or does not exist": • Your "Database" field under Advanced View has a path in it. Open the container's Edit page, switch on Advanced View, clear the "Database" field completely, then Apply. The bundled, already-initialised database takes over and the container starts normally within a minute. Troubleshooting - container loops "Starting nginx nginx ...fail!": • Your "Logs" field under Advanced View has a path in it. The image keeps its log tree at /var/log/euro-office/documentserver, so mounting an empty folder over /var/log/euro-office hides it, nginx cannot open its error log there, and the entrypoint aborts before the editor comes up. Open the container's Edit page, switch on Advanced View, clear the "Logs" field completely, then Apply. • The logs are not lost by clearing the field - the Unraid log button on the container still shows everything the server prints. Troubleshooting - documents open blank, or the browser says "this content is blocked, contact the site owner": • The OpenCloud container is older than 1.4.0. Older versions let the browser load the editor straight from Euro Office, and an http address is then blocked as mixed content. Update OpenCloud, or use https://[THIS-SERVER-IP]:9943 and accept the certificate warning in every browser. • Or OpenCloud uses a proxy.yaml of your own. Then it does not pass the editor through, and its log says so at startup; use the https address as above. About Euro Office: • Euro Office is an open, sovereignty-focused document server developed in Europe as an OnlyOffice-compatible fork. Because it is API-compatible, any guide for "OnlyOffice Document Server + OpenCloud/Nextcloud" applies here as well. Project: https://github.com/euro-office/documentserver This is an independent, community-maintained Unraid packaging and is not affiliated with the Euro Office project.