meaningless message: "This directory is unavailable, please check the logs or contact the administrator"

nextcloud / server

☁️ Nextcloud server, a safe home for all your data

https://nextcloud.com

GNU Affero General Public License v3.0

26.92k stars 4.01k forks source link

meaningless message: "This directory is unavailable, please check the logs or contact the administrator" #26220

Open ferdiga opened 3 years ago

ferdiga commented 3 years ago

NC 20.0.4

Please name the directory which is not available.

Nothing is in the logs, even though all content log boxes are checked.
the admin will not be able to help without knowing the directory.

chylex commented 2 years ago

I just ran into this, it turned out to be external storage that I disconnected a long time ago and forgot to remove from my NC account (I never had the external storage synced via the desktop client, so I didn't notice until the website stopped working).

The message is not helpful at all, and neither are the docker logs. All I got was:

"PROPFIND /remote.php/dav/files/chylex/ HTTP/1.0" 500 1824 "-" "<User Agent>"

No actual error message saying what went wrong, the only indication that made me suspicious it might've been the external storage was the /dav/ folder.

joshtrichards commented 1 year ago

This code no longer exists in NC27 as a result of the Files Vue migration.

Thatoo commented 9 months ago

Well I do face this same issue on Nextcloud : 27.1.4 when I try to reach a public shared link of a heavy folder on a slow internet connection. In Firefox console log, I get the following error : PROPFIND https://MYDOMAIN.tld/nuage-nextcloud/public.php/webdav/ [HTTP/2 500 Internal Server Error 114ms]

A single file shared link do works and a shared heavy folder link on a high speed internet do work also.

joshtrichards commented 9 months ago

A 500 error means that an error is logged in the Nextcloud Server logs (or, in some cases, upstream of your Nextcloud Serer, such as if your proxy or similar is having a problem external to Nextcloud). Please check your nextcloud.log (or equivalent) from around the same period.