New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Files app no longer displays files after upgrade #43302
Comments
That red propfind is not a good sign. Can you check your browser console Network tab to see why (and what HTTP code) transactions are failing? Also, if you haven't already, make sure to restart Apache/PHP after the upgrade. |
Additional details.
|
Ok. We need the details of that 500 error. They'll be in your However your logging is probably messed up because this is invalid syntax:
Just remove it; or set it to
Fix that, restart Apache, reproduce, check your |
I have done what you have instructed. Only log output given is below.
|
Your Redis service is offline. This is a configuration matter, not a bug. If you need help troubleshooting, ask for it in the Nextcloud Help Forum: https://help.nextcloud.com |
Would need to add a few points here to clarify and align this issue with others facing the same problem.
|
Bug description
After ugrading from 28.0.1 to 28.0.2, i no longer can create/upload anything within the Files app. External mounts no longer load although the connectivity checks are green.
Steps to reproduce
Expected behavior
There shouldve been no functional/operational changed to the files application
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 22.1 to 22.2)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
The text was updated successfully, but these errors were encountered: