"Solved" macOS File Provider stuck on “You need to authenticate” even though Nextcloud is connected — check Local Network permission

📱 Desktop & mobile clients 💻 Desktop
, ,
1

macOS Nextcloud File Provider stuck on “You need to authenticate” — Local Network permission issue

Summary

I ran into a Nextcloud Desktop problem on macOS where the Nextcloud account itself was connected, but Finder’s Nextcloud location stayed stuck in an authentication state and would not show the files correctly.

The important clue was that macOS File Provider reported:

needs-auth: yes
NSFileProviderErrorDomain Code=-1000
You need to authenticate before accessing this item.

At first this looked like a Nextcloud account/server authentication problem. It was not.

The macOS system log showed the Nextcloud FileProviderExt process being blocked before it could reach the server:

unsatisfied (Local network prohibited)
Network is down
failed to connect 1:50

So the failure was happening on the Mac, at the Local Network / File Provider layer, before a normal HTTPS request could reach the Nextcloud server.

Environment

  • Apple Silicon MacBook Pro
  • macOS 27.0 (Build 26A428)
  • Nextcloud Desktop Client 4.0.11
  • Nextcloud Server 33, Docker (nextcloud:33-apache)
  • Server accessed over the local LAN using HTTPS (192.168.x.x)
  • macOS File Provider / Virtual Files enabled

Symptoms

  • Nextcloud Desktop showed the account as connected.
  • Finder showed Nextcloud under Locations.
  • Finder kept asking for authorization / authentication.
  • The File Provider domain stayed in:
needs-auth: yes
  • Opening the Nextcloud location produced:
You need to authenticate before accessing this item.
  • Reinstalling Nextcloud did not solve it.
  • A full DFU restore / clean macOS installation did not solve it by itself either.

This was useful because it ruled out a normal damaged Nextcloud installation or leftover client files.

How I diagnosed it

1. Check File Provider state

Run:

fileproviderctl dump com.nextcloud.desktopclient.FileProviderExt 2>&1 | \
  egrep -i 'needs-auth|auth|error|state|nextcloud'

The important output in my case was:

needs-auth: yes
NSError: FP -1000 "You need to authenticate before accessing this item."

2. Watch the macOS File Provider logs

Run:

log stream --style compact --level debug \
  --predicate 'process == "fileproviderd" OR process == "FileProviderExt" OR process == "Nextcloud" OR subsystem CONTAINS[c] "FileProvider"'

Then open Finder → Nextcloud and reproduce the problem.

The key lines were:

FileProviderExt ... unsatisfied (Local network prohibited)
FileProviderExt ... Network is down
FileProviderExt ... failed to connect 1:50

That was the turning point: the File Provider extension was being denied local-network access by macOS.

Fix that worked for me

  1. Open:

    System Settings → Privacy & Security → Local Network

  2. Make sure Nextcloud is enabled.

  3. Quit Nextcloud completely.

  4. Restart the Mac.

  5. After restart, launch Nextcloud normally from Applications.

  6. Open Finder → Locations → Nextcloud.

After doing this, the account authenticated successfully and the File Provider started working normally.

Important detail

In my case, Nextcloud was already shown as ON in Local Network settings, but the File Provider logs still said:

Local network prohibited

So the UI permission state and the effective permission used by FileProviderExt appeared to be out of sync. A reboot/relaunch allowed the File Provider authorization to recover.

I did not need to reset the Nextcloud server, change the server account password, modify Docker, or replace the File Provider extension manually.

How to verify the fix

After Nextcloud is working, run:

fileproviderctl dump com.nextcloud.desktopclient.FileProviderExt 2>&1 | \
  egrep -i 'needs-auth|error|state'

The main thing to check is that the domain is no longer stuck in an authentication failure.

You can also check whether macOS is still blocking the extension:

log show --last 3m --style compact \
  --predicate 'process == "FileProviderExt"' | \
  grep -i "Local network prohibited"

If no new Local network prohibited entries appear while opening the Nextcloud location, the network-permission layer is no longer blocking the File Provider.

Why this can be confusing

The Nextcloud Desktop application and the macOS File Provider extension are separate processes.

The main Nextcloud application can appear connected while the File Provider extension is still unable to reach the same server. In that situation Finder may report an authentication problem even though the actual failure is lower in the macOS network/privacy layer.

That is why repeatedly changing the Nextcloud password or reinstalling the server may not help.

What I would check before reinstalling anything

If you see the same problem, check these first:

  1. System Settings → Privacy & Security → Local Network → Nextcloud = ON
  2. fileproviderctl dump ... for needs-auth: yes
  3. macOS logs for Local network prohibited
  4. Restart the Mac and relaunch Nextcloud normally

If the logs show Local network prohibited, I would investigate macOS Local Network permission before changing anything on the Nextcloud server.

Notes for Nextcloud developers

This case may be worth improving in the client UI. Finder reported an authentication error, while the lower-level failure was actually:

Local network prohibited

A clearer client-side message such as “Nextcloud File Provider does not currently have Local Network access” would make this much easier to diagnose.

1 Like