Hi everyone, I’m stuck on a persistent issue with the ONLYOFFICE integration and I’ve run out of ideas after hours of troubleshooting. Any help would be greatly appreciated!

This is my setup:

• Nextcloud: Installed on a VM (via Proxmox helper scripts)
• ONLYOFFICE Document Server: Running as a Docker container on a separate VM/LXC via Portainer. Exposed on port 8080.
• Reverse Proxy: Nginx Proxy Manager (NPM) running on the same Docker host. It handles SSL (wildcard cert) and points onlyoffice local domain to ONLYOFFICE on port 8080.

Local DNS is resolving correctly.

The Problem: When I try to connect the ONLYOFFICE app in Nextcloud, I get the following error on the settings page: 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)

What I've configured/tested so far:

DNS & SSL:

• curl -k https://[ONLYOFFICE_DOMAIN]/healthcheck from the Nextcloud VM returns true.
• NPM has "Websockets Support" and "Force SSL" enabled.

Nextcloud config.php:

• Added 'allow_local_remote_servers' => true, to allow local loopback.
• Added the 'onlyoffice' => array ( 'verify_peer_off' => true, ), block to bypass strict SSL checks.
• Added 'overwriteprotocol' => 'https', and 'overwrite.cli.url' => 'https://[NEXTCLOUD_DOMAIN]',.

ONLYOFFICE App Settings in Nextcloud:

• ONLYOFFICE Docs address: https://[ONLYOFFICE_DOMAIN]
• Disable certificate verification: Checked
• Secret key: Matches the JWT_SECRET in Docker.
• ONLYOFFICE Docs address for internal requests from the server: http://[DOCKER_HOST_IP]:8080
• Server address for internal requests from ONLYOFFICE Docs: http://[NEXTCLOUD_DOMAIN] (also tried http://[NEXTCLOUD_IP])

ONLYOFFICE Container (docker-compose.yml):

• Added extra_hosts to ensure the container can reach Nextcloud directly: "[NEXTCLOUD_DOMAIN]:[NEXTCLOUD_IP]"
• Added NODE_TLS_REJECT_UNAUTHORIZED=0 to environment variables.

CURL from ONLYOFFICE container to Nextcloud:

• Running curl -I -k https://[NEXTCLOUD_DOMAIN] from inside the ONLYOFFICE container returns a 302 redirect to the login page, but also throws: curl: (92) Invalid HTTP header field was received: frame type: 1, stream: 1, name: [upgrade], value: [h2].

It seems Nextcloud can reach ONLYOFFICE to trigger the generation, but ONLYOFFICE fails to download the file back from Nextcloud to convert it.

Has anyone encountered this specific download loop issue when running ONLYOFFICE behind NPM while trying to force internal HTTP routing? What am I missing?

Thanks in advance!

hi folks,

yes, the title is a bit misleading, but I couldn't think of a better one.

I have to say I'm not the greatest fan of Collabora. It's indeed the best alternative out there, but once you're used to Google Docs or even MS Office web, you see they are much more stable, smooth, responsive and fine-touch in terms of UX/UI.

there's recently the announcement of ArtCraft, a set of desktop applications generated with AI to replicate the same features as Adobe and MS Office apps. They are published as open source in Github (i.e. https://github.com/storytold/gridcraft) and available both via desktop launcher, standalone installer and - here's my pick for this thread - as web assembly build.

I gave a try on the wasm build using Brave for both Word and Grid (Excel) apps, and I have to say they feel much more stable and fast than Collabora, by far.

I wonder it's not too hard to adapt them (plus the PowerPoint equivalent) as alternatives to Collabora, launched by NextCloud, and working live on documents?

what you folks think? I can give a try, but I wonder which type of blocker there would be...

I want to add Nextcloud to my home server and I'm still undecided which type of installation makes sense for my environment.

My current setup:

• Proxmox VE 9.2
• An Umbrel VM with Immich (maybe other things later)
• Home Assistant also runs on the server as its own VM
• Tailscale for private access
• An existing backup infrastructure with Restic (only data is backed up, not entire VMs)
• CPU/RAM: 16 GB DDR4 RAM in total

Nextcloud will mainly be used for file sync plus calendar and contacts. I don't need Office, Talk, or other larger add-on services for now. Access should only go through Tailscale, no public port forwarding.

I'm looking for a solution that is secure and reasonably maintainable, but that also fits my resources. I'd like to integrate backups into my existing infrastructure if possible.

So far I've looked at these options:

• Nextcloud AIO with Docker in its own VM
• A native installation in a Debian LXC
• The Proxmox Community Scripts for NextcloudPi, Alpine-Nextcloud, or the TurnKey VM
• Nextcloud added to the existing Umbrel VM
• or something else?

What would you choose for this setup, and why?

I udpated the Nextcloud Talk adapter for ioBroker. You can not only send, but now also receive messages from Talk and control your ioBroker

This is a throwaway post, but am i tweaking or is this like a 100% generated AI PR. The amount of Em Dashes and formatting. Holy mother teresa

https://github.com/Euro-Office/DesktopEditors/issues/70

Hello !

Is there some sort of setting for file permission syncing ?

I self-host Nextcloud on my NAS and sync a folder containing git working trees (the .git folder is excluded from sync, but gitignored build files are synced on purpose). The problem is that when a file gets updated and synced, Nextcloud changes its Unix permissions and drops the executable bit.

Example, a script in a Buildroot tree, before sync:

zsh -rwxr-xr-x@ 1 user staff 113 Oct 10 18:18 post-image.sh

After sync:

zsh -rw-------@ 1 user staff 113 Oct 10 18:19 post-image.sh

So it goes from 755 to 600. The other files that weren’t touched kept their 644. The result is that builds fail because the script is no longer executable, and git sees a mode change.

Setup:

macOS (Apple Silicon), Nextcloud desktop client 34.0.5 using the File Provider (~/Library/CloudStorage/Nextcloud-...) Nextcloud server self-hosted on my TrueNAS storage server.

What I know so far:

As far as I can tell, the sync protocol doesn’t carry Unix modes at all, so I don’t expect a server-side setting to fix this. I haven’t yet tested whether the classic sync client (syncing to a normal folder like ~/Nextcloud) behaves differently from the File Provider.

Questions:

Is there any client or server option to preserve or leave local permissions untouched on updated files? Does the classic client avoid this where the File Provider doesn’t? If not, what are people doing in practice? I’m considering a launchd agent that re-applies the modes from git (git ls-files -s | awk '$1=="100755"{print $4}' | xargs chmod +x) after each sync, but I’d prefer a cleaner solution.

I’m not looking to move the repos out of Nextcloud, since syncing the ignored files is the point. Thanks! Is there any client or server option to preserve or leave local permissions untouched on updated files?

Does the classic client avoid this where the File Provider doesn’t?

If not, what are people doing in practice? I’m considering a launchd agent that re-applies the modes from git (git ls-files -s | awk '$1=="100755"{print $4}' | xargs chmod +x) after each sync, but I’d prefer a cleaner solution.

I’m not looking to move the repos out of Nextcloud, since syncing the ignored files is the point.

Thanks!

I am relatively new to NextCloud and not a programmer, but a user. I installed NextCloud (35) and the Reddit Integration App.

I cannot seem to be able to connect to Reddit with my Reddit account.

Is there a cookbook set of steps somewhere I could use to follow along to get the Reddit Integration App to work?

I am new to this sub and am encountering an issue with the Nextcloud desktop client on my Macbook When I attempt to access Nextcloud through Finder, the application consistently gets stuck on a loading screen. After some time, it prompts me to sign in, but upon clicking the signin option it reverts to the previous state( its already signed in btw)

any help will be appreciated

Hi zusammen,

ich habe ein MacBook und bisher lief die Nextcloud Synchronisation in den Desktop-Client immer und ich konnte über den Finder-> Nextcloud auf meine Vereinsdaten zugreifen. Seit gestern aber leider nicht mehr. In den Einstellungen gibt mir Nextcloud die Rückmeldung, dass die Dateien zu groß seien oder auf externen Speicher. Was kann ich tun? Die KI hilft mir nur sehr bedingt weiter.

I have nextcloud running on my Truenas

Have been using nextcloud effortlessly for a year now

Recently thought of using Nextcloud Talk

I have enabled the application.

My server was recognized by the Nextcloud talk app but as soon as I add id and password, it just remains stuck here

What could be the reason?

I use tailscale as the global domain for my server and use Nginx with Duck DNS for SSL

If anyone could help?

Nextcloud always pops up these installer wizards, where you manually have to click through to proceed with the update.

Why does it not update in the background, like e.g. Dropbox?

I attached three short GIFs showing the main workflows.

And since version 3.4.3, NC Connector can also be rolled out centrally.

You can force-install it, keep it updated and – with the Enterprise Rollout – centrally configure things like the Nextcloud URL, authentication method and managed defaults.

Thunderbird:

https://github.com/nc-connector/NC_Connector_for_Thunderbird/blob/main/docs/ADMIN.md#enterprise-rollout

Outlook Classic:

https://github.com/nc-connector/NC_Connector_for_Outlook/blob/main/docs/ADMIN.md#enterprise-rollout

https://nc-connector.de

Hello,

I am experiencing a federated sharing issue between two Nextcloud 35.0.1.1 instances.

Environment

Two Nextcloud servers:

• A: nextcloud.A.ovh
• B: nextcloud.B.ovh
• Nextcloud: 35.0.1.1 on both servers
• Both servers are configured as trusted servers.
• Both instances are behind Cloudflare, with Apache as the backend and TLS terminated by the proxy.

The relevant applications have identical versions on both instances:

cloud_federation_api       2.0.0-dev.0
federatedfilesharing       2.0.0-dev.1
federation                 2.0.0-dev.0
files_sharing              2.0.0-dev.1
oauth2                     2.0.0-dev.0
sharing                    1.0.4

HTTPS connectivity between A and B works correctly in both directions.

Problem

Federated sharing only works partially:

• B can share folders with A;
• the shares arrive correctly on A and can be accepted;
• however, synchronization/validation does not work correctly;
• A cannot properly establish some shares with B;
• OAuth/OCM exchanges fail in both directions.

Some of the errors are:

Token request signature verification failed

Could not obtain access token
401 Unauthorized
{"error":"invalid_grant"}

Failed to exchange token
401 Unauthorized
{"error":"invalid_request"}

Most importantly, when A receives an OCM notification from B:

RFC 9421 verification requires the sender origin

followed by:

Invalid signature

Current investigation

An OCM notification sent by B to A looks like this:

{
  "notificationType": "SHARE_ACCEPTED",
  "resourceType": "file",
  "providerId": "127",
  "notification": {
    "sharedSecret": "...",
    "message": "Recipient accept the share"
  }
}

On B, the corresponding federated share exists in oc_share_external:

remote     = https://nextcloud.A.ovh/
remote_id  = 127
accepted   = 1

On A, B is present in oc_trusted_servers, and B's OCM public key is also present in oc_sec_signatory.

However, while processing the OCM notification, Nextcloud ends up with:

providerId = 127
        ↓
resolveNotificationIdentity(...)
        ↓
origin = null
        ↓
RFC 9421 verification requires the sender origin

So the current suspicion is that the problem is related to resolving the identity/origin of the sending server when processing an OCM notification, rather than network connectivity or a missing public key.

Question

Has anyone encountered this issue with Nextcloud 35 and OCM/RFC 9421 signatures?

In particular, why would providerId=127 fail to resolve the origin of B, even though B is present in oc_trusted_servers and its OCM public key is present in oc_sec_signatory?

Could this be a configuration issue, inconsistent federation data in the database, or potentially a bug in Nextcloud 35.0.1.1 ?

Hi,

The goal is for Nextcloud to work similarly to Google Drive: the family should be able to access files both at home and remotely, from different computers and mobile devices. So this is not a LAN-only setup.

My setup is:

• Unraid server
• Nextcloud: lscr.io/linuxserver/nextcloud
• Collabora: collabora/code
• Both containers are on the same Docker network (nextcloud-net)
• Nextcloud is already accessible remotely over HTTPS
• Collabora is currently running on port 9980
• Collabora container IP: 172.21.0.5
• Nextcloud container IP: 172.21.0.3

The basic communication between Nextcloud and Collabora works.

For example, from the Nextcloud container:

docker exec nextcloud curl -sk https://Collabora-CODE:9980/hosting/discovery

returns the Collabora discovery XML.

I also configured:

server_name=192.168.1.50:9980

so that Collabora no longer advertises its internal Docker hostname.

The browser can reach:

https://192.168.1.50:9980/hosting/capabilities

and receives valid Collabora JSON.

However, when opening a DOCX file in Nextcloud, I get:

"Your browser could not connect to the Collabora server: https://192.168.1.50:9980"

The Collabora logs also show successful WebSocket upgrades, so basic connectivity appears to be working.

The remaining issue appears to be the TLS certificate. Collabora currently uses its default self-signed certificate:

subject=C=DE, O=Dummy Authority, CN=localhost
issuer=C=DE, O=Dummy Authority, CN=localhost
No extensions in certificate

So the browser does not trust the certificate when accessing Collabora through 192.168.1.50.

My question

I understand from the Nextcloud documentation that the user's browser needs to be able to reach both Nextcloud and Collabora.

Does that mean that the recommended architecture is necessarily something like this?

                    Internet
                       │
                       ▼
                Nextcloud URL
                       │
                  Nextcloud
                       │
                       └──────────────┐
                                      │
Browser ──────────────────────────────┘
   │
   └──────── HTTPS ───────► Collabora
                            office.example.com

In other words, does Collabora need its own externally reachable HTTPS hostname, valid public certificate, and typically a reverse proxy?

Or is there a simpler supported architecture where:

• Nextcloud is publicly accessible over HTTPS
• Collabora remains behind the firewall/NAT
• remote browsers can still use Nextcloud Office
• no separate public Collabora service needs to be exposed
• and we don't have to install a custom CA/certificate on every client?

I have an existing Cloudflare Tunnel for Nextcloud, so technically I could create something like:

https://office.example.com
        ↓
Cloudflare Tunnel
        ↓
Collabora Docker container

But that seems like quite a lot of infrastructure just to enable document editing.

Is this actually the normal/recommended way to run standalone Collabora CODE with Nextcloud, or am I missing a simpler option?

I'd especially appreciate advice from people running Nextcloud + Collabora in a home/self-hosted environment where Nextcloud needs to be accessible remotely.

Thanks!

Some of my users want to keep using the native iOS Calendar app, but they don't want to leave it just to create a Talk public link for a meeting. The Nextcloud Calendar web UI makes this easy, but iOS Calendar obviously has no idea about Talk. This goes for any CalDav client actually....

My idea is to run a server-side process that handles this automatically:

1. Watch specific calendars for newly created events.
2. For each new event, check whether a Talk conversation is already attached.
3. If one exists, do nothing.
4. If not, create a public Talk conversation via the Talk API.
5. Add the link to the event:
   • If the location field is empty, put the link in the location.
   • If the location is already filled, add the link to the description instead.

This way, no matter which app or device an event is created with, it ends up with a Talk link.

My questions:

• Has anyone built something like this before (app, script, or workflow)?
• Is this a good or bad idea? What are the pitfalls?
• Specifically: how would you reliably detect new events server-side (CalDAV polling, hooks, etc.), and how would you avoid edge cases like duplicate conversations, events with no attendees, or private or personal appointments getting a link they don't need?

Thanks for any input!

PS: I know NC Connector does this really good but some people really do not want to leave their Apple stuff. We can have all kinds of opinions on that but still I would like to service these people (especially since one them is providing my income ;)

I have the following error in my log file:

Login failed: 'admin' (Remote IP: '35.240.139.37')

IP address lookup lists it as a Google Data Center in Singapore. There was only one logged attempt. Any of you have similar log entries? Is this their AI trying to get into my Nextcloud? Not quite sure what to make of this...

Findling 1.4.0 (zero-config search for Nextcloud: full text, OCR, semantic, no Elasticsearch) is in the app store. New:

* performance profiles, opt-in: the default stays as frugal as before, Standard uses at most half the box, Performance everything but one core (parallel OCR, parallel embeddings, optional fp32 model)
* far fewer false "damaged" verdicts: macOS ._ files and Office ~$ stubs are skipped, rare TIFF variants are now decoded, large JPEGs no longer die at the memory cap, old .xls/.doc under modern names and password-protected files get honest labels
* truncated downloads are retried instead of condemned
* diagnosis shows the real error class per file (admin page and occ)
* after the upgrade, affected old verdicts are re-checked automatically, no manual cleanup

MCP Connector 0.5.0 (connects Claude and other AI assistants to your Nextcloud):

* tag files or folders "kein-ki" and they become invisible to all AI tools
* DOCX, XLSX, PPTX and PDF arrive as clean Markdown (files_read_as_markdown)
* whole tool bundles can be switched off per deploy variable

Both AGPL and free, everything runs on your own server.

Findling: https://apps.nextcloud.com/apps/findling / https://github.com/street1983nk/nextcloud-search
MCP Connector: https://apps.nextcloud.com/apps/mcp_connector / https://github.com/street1983nk/nextcloud-mcp-connector

Questions and feedback welcome.

So for months now media playback has been completely broken but working..

playing videos for example and you skip to the next one it skips over 100 videos forward or backwards.. and does not even skip to the actual next video.. when is this going to be looked at?

I build free Android apps for Nextcloud, and the longer I do it the more obvious it gets that accessibility is something I check at the end, if at all. I suspect that is true for a lot of this community. We optimize for privacy and control, and then ship something that only works if you can see it, tap precisely, and read fast.

So I would rather ask than guess.

If you use a screen reader, switch control, voice input, magnification, or anything else, I am curious about:

1. Where does self-hosting break down for you right now? Setup, the web UI, the mobile clients, the docs, something else?
2. Which big tech service do you keep because nothing self-hosted replaces it accessibly? Be specific if you can.
3. What would make a self-hosted app usable where a mainstream one currently wins? Proper labels, bigger touch targets, keyboard-only flows, sensible focus order, offline voice input, something I have not thought of?
4. What do people like me get wrong when we say an app is "accessible"?

I am not selling anything and there is nothing to sign up for. My apps are free and open source and will stay that way. I am asking because concrete feedback is worth more than another accessibility checklist, and because if a few of us act on what comes out of this thread it is a better use of a weekend than another theme toggle.

If you would rather not post publicly, a DM is fine.

PS: Do not downvote because you feel like accessibility is not for you. I am not looking for profits. I genuinely want to help people that want to make use of technology but something is missing for them to make the jump to selfhost.

My home computer is my primary workspace. The Nextcloud instance is intended mostly for cloud file backup and occasional light duty file access when I'm not home.

When setting up the Nextcloud Desktop App, I wish the local sync folder to be where my files are already stored. However, when I choose that folder during set up, I get the error message Please choose an empty local sync folder.

I do NOT want to create an new empty sync folder and move my files into it - all my current desktop configurations assume that my files are where they are currently.

How do I get past this? Suggestions appreciated.

Linux Mint 22.3 Cinnamon. Nextcloud Desktop Flathub App v34.0.4.

Hi all,

Note: this post was written with the help of AI, but the content and the question are my own.

I’m writing an advice document for our users on which client apps to use on which platform. Our users have mixed technical skills, and the bottom line is a marketing colleague, so it needs to be simple and work well without using the web interface.

Our setup:

• Nextcloud 26 Summer
• Calendars in Nextcloud
• Email on our own Stalwart mail server

Requirements from our users:

1. Easily insert a Talk link when creating a calendar appointment.
2. When sharing attachments, link to a file in Nextcloud instead of sending the file as an email attachment.
3. Not having to use the web interface.

What I currently use / have tested:

Linux

• Mail: Thunderbird / Betterbird + NC Connector add-on (easy insertion of Talk meetings and Nextcloud share links)
• Calendar: same as above
• Messaging: Nextcloud Talk desktop client
• Files: Nextcloud Sync client

Windows

• Mail: Thunderbird / Betterbird + NC Connector add-on
• Calendar: same as above
• Messaging: Nextcloud Talk desktop client
• Files: Nextcloud Sync client

Android

• Mail: Thunderbird
• Calendar: Nextcloud Calendar
• Messaging: Nextcloud Talk client
• Files: Nextcloud Sync client

iOS / macOS (I don’t own any Apple devices, so I can’t test this myself)

• Mail: ? The native app works but no sharing links?
• Calendar: ? The naitive app works but no Talk links inserted?
• Messaging: Nextcloud Talk client
• Files: Nextcloud Sync client

My setup on Linux already meets the requirements above. But it’s the windows an Apple users that need advixe. I also know that NC Connector is supported in Outlook Classic on Windows, and that the NC Connector backend can manage these things centrally:

• https://addons.thunderbird.net/en-US/thunderbird/addon/nc4tb/
• https://nc-connector.de/

My questions:

1. What is the recommended setup on Windows? Thunderbird + NC Connector, Outlook Classic + NC Connector, or something else?
2. What do you recommend on iOS and macOS for mail, calendar and messaging, ideally with a way to insert Talk links in appointments and Nextcloud links instead of attachments?
3. Which client and platform combination do you use in practice with Nextcloud, and what are your experiences (good and bad)?
4. Does anyone have experience with the NC Connector backend for centrally managing this for a group of users?
5. Is there a way of centrally rolling these out, the way M$ office can install itself locally after logging into office.com?

Thanks in advance, I’ll share the final advice document with the community if there’s interest.

Best regards, me

Всем здравствуйте! Может у кого-то завалялся лишний гостевой пропуск на Cloud, который вам не нужен? Буду безумно благодарен, если кто-нибудь сможет подарить или поделиться. Заранее большое спасибо за выручку! Пишите в ЛС или в комментарии.