-
Notifications
You must be signed in to change notification settings - Fork 27
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]: Logreader shows blank part of the page #1078
Comments
I thought I saw something similar in the forum, but it is old and not the same problem. |
read the comment section of #1073 for a temporary fix. It will be fixed in 28.0.1 p.s. duplicate |
Sound like you did not configure NGinx correctly, can you make sure you configured your Nginx to serve
No it is not that one is about an error causing "Internal server error", this is fixed with 28.0.1. |
For those who employ caddy, add this to your
|
Bug description
After Update from Nextcloud 27.4 to 28 the Logreader is blank.
The instance is running on kubernetes and uses the arm images.
The Developer Tools show NS_ERROR_CORRUPTED_CONTENT when loading apps/logreader/js/logreader-main.mjs?v=1b0952dc-0. Chrome (with zero cache and cookies) does the same as Firefox.
Never the less the logreader-main.mjs has the same md5sum as in the zip.
Steps to reproduce
As this is not a new instance I dont know all circumstances, but I would suggest the following:
1.Install nextcloud 27.4.1 and update to 28, while using the docker image at least.
Expected behavior
Logreader is visibel after update.
Installation method
Community Docker image
Nextcloud Server version
28
Operating system
Other
PHP engine version
PHP 8.3
Web server
Nginx
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: