NextCloud sync client not working in Finder on MacOS

The Basics

  • Nextcloud Server version:
    • 35.0.3
  • Operating system and version (e.g., Ubuntu 24.04):
    • Server: TrueNAS Scale 27.0.0-RC.1
    • Client: MacOS 27.0.01
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • As long as I have had NextCloud installed
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Docker via TrueNAS apps

Summary of the issue you are facing:

I have setup NextCloud on MacOS, the sync client configuration works fine, and I am singed in. However when I try and access the files via Finder, I see a message that says Nextcloud is not signed in. When I press sign in I see authenticating for a second and then it goes back to saying NextCloud is signed out, and I get stuck on a screen that just says loading.

I don’t think this is an issue with the server, as it works fine on my Windows PC. This issue only occurs on Mac.

The NextCloud server is on my LAN, and I run a Nginx Proxy Manager server on another computer, which I am using for SSL. So in my web browser and NextCloud client, I am using nextcloud.domain.com

Steps to replicate it (hint: details matter!):

  1. Sign in to NextCloud on MacOS
  2. Open finder and navigat to NextCloud
  3. Attempt to access files or sign in. The loading message displays forever.

Finder does not use the window you already signed into. It uses the File Provider extension, and that one is failing its own sign-in. That is the flash of authenticating, then signed out, then loading forever.

In the Mac client, turn virtual files on for this account if it is off, then quit the client completely and open it again so the extension receives the account. If it still flips back, the extension is rejecting the server: same host and certificate as the client, and Nextcloud allowed under System Settings, Login Items and Extensions. Windows does not use that extension, which is why the same server is fine there.

Thank you for your response. I tried toggling the virtual files (it was already enabled, so I disabled and re-enabled it.) Unfortunately it doesn’t seem to have helped.

Do you have any suggestions on how to diagnose / fix it, I don’t think it is the certificate, as it is using Nginx Proxy Manager, so it has a standard Lets Encrypt certificate, that should be fully trusted.

I have checked all the settings on MacOS, but don’t seem to be able to see anything that looks wrong.