"Content Unavailable" when opening an SMB share on iPhone

By Isaac Griffiths, developer of SMBDrop ·

You add the server in the Files app, it connects, you can see the list of shares, and then you tap one and get this:

Content Unavailable. The folder contents could not be displayed because of an unknown error.

Sometimes the message ends "because the connection to the server timed out" instead. Either way, the login worked and the folder didn't. Apple doesn't document what this error means, so everything below comes from user reports in Apple Community threads and NAS forums, ordered by how often I found each cause. Work down the list.

1. A stale session after sleep or a network change

This is the most common one. The phone left your Wi-Fi for a while, switched networks, or the server dropped the session, and the Files app is still holding on to a connection that no longer exists. One person in "Samba share not accessible from files.app" said that if they're off the local network for several minutes and come back, they get Content Unavailable. Another, in "Content Unavailable after switching networks", said the only fix they'd found was rebooting the phone.

Fix:

  1. Open Files → Browse, find the server under Shared, and tap the Eject button next to it.
  2. Reconnect with ⋯ → Connect to Server. The server should be listed under Recent Servers.
  3. If it still fails, restart the iPhone and try again. One Reddit user said a reboot helped them about 80% of the time.

2. The account can sign in but can't read that share

The server accepts your username and password, lists the shares, and then refuses to open one because the account has no permission on it. That shows up as Content Unavailable rather than a clear "access denied".

Fix: eject, then reconnect as Registered User with a normal, non-root account that has at least read permission on that share. The Unraid and TrueNAS guide walks through creating the right kind of user on both.

3. The server only allows a protocol version the iPhone won't use

An r/ios user whose server was restricted to SMB3 only got Content Unavailable (back on iOS 13). The same kind of mismatch usually shows up as "Operation not supported" when you connect, which is covered in the can't connect to server guide.

Fix: on the server, allow SMB2 as the minimum and SMB3 as the maximum. That's what Synology recommends. On Samba, if you want an SMB3-only policy, one Ask Different answer suggests server min protocol = SMB3_02 rather than SMB3, which defaults to the newest dialect. Don't lock it to the newest dialect only.

4. You're connecting over a VPN

A user on Cisco AnyConnect could log in but couldn't open folders (Apple Community thread). Over a VPN, routing and name resolution go through the tunnel, and Synology warns that SMB clients on a VPN "cannot resolve server names correctly".

Fix: connect to the server's IP address on the VPN, not its name. If you're at home and a VPN is on, it can also block local network access unless it supports split tunnelling, so try with the VPN off. Reaching your NAS over Tailscale covers the remote case properly.

5. An iOS bug

Some versions of iOS have simply broken Files SMB connections for a while:

Fix: update iOS. If you're on one of those versions, updating is the first thing to try before changing anything on the server.

6. A folder with a huge number of items

One MacRumors user had a folder with around 1,600 subfolders that showed "0 items" in the Files app but listed fine in third-party apps. If only one very large folder fails and the others open, that might be what you're seeing. Splitting it into subfolders, or opening it in another app, are the options.

A quick checklist

  1. Eject and reconnect. Restart the phone if that doesn't help.
  2. Sign in as a normal user, not root, admin built-ins or Guest.
  3. Check that user can read the share from another device.
  4. Use smb:// plus the IP address, not the name.
  5. Set the server to Min SMB2, Max SMB3.
  6. Turn off any VPN when you're at home.
  7. Update iOS.

If your problem is the opposite (folders open fine but you can't save anything), see the read-only share fix.

Where SMBDrop fits

Disclosure: I make SMBDrop. It sends photos, videos and files from your iPhone to an SMB share and can import files back. It connects to the same server, so permission, protocol and VPN fixes on the server side still apply; it won't fix a share your account can't read. Like any third-party app it needs Settings → Privacy & Security → Local Network turned on to reach your NAS. Once you've entered the address and sign-in, Find Shares lists the shares that account can see, which is a quick way to confirm the permissions are right. It's £9.99 once, no subscription, no account, iOS 17 or later.

Other errors? See "Socket is not connected", or start from what the Files app's Connect to Server can and can't do.

FAQ

What does Content Unavailable mean in the iPhone Files app?

Apple doesn't document it. In user reports it usually means the Files app connected to the server but couldn't open a share or folder. Reported causes include a stale session, an account without permission on that share, a protocol mismatch, or a VPN.

Why does Content Unavailable go away after I restart my iPhone?

Restarting the iPhone, or ejecting the server in Files and reconnecting, can restore access after sleep or a network change.

Can I use the root account to connect to my NAS from iPhone?

Usually not. TrueNAS says root and built-in accounts can't access SMB shares, and Unraid's root account can't access network shares either. Create a normal user with permission on the share.

Which iOS versions had SMB bugs in the Files app?

Users reported problems on iOS 15.4 and 15.4.1, on iOS 17.0 to 17.2 (reportedly fixed in 17.2.1), and on iOS 18.7.9 (fixed in 18.7.10 according to the original poster).

More guides

Try SMBDrop

Send original photos, videos and files from your iPhone straight to your own SMB share. One purchase, no account, no subscription.

Download SMBDrop on the App Store £9.99 once · no subscription · iOS 17+