Broken after update to 12.0.5

I am not an expert, but it looks like the error occurs when this file is being processed:

which has to do with caching css-files. Therefore I don’t think it has to do with the files-app.
I am sorry that my skills are not sufficient enough though to help any further.

Hi,

I had a look at your login page and opened the web console. This are the error messages, that I see:

JQMIGRATE: Migrate is installed, version 1.4.0
core.js:7:542
ReferenceError: OCA is not defined
[Weitere Informationen]
search.js:391:2

https://cloud.lefev.re/core/search/js/search.js:391:2

https://cloud.lefev.re/core/search/js/search.js:11:2
ReferenceError: OC is not defined
[Weitere Informationen]
de.js:1:1

https://cloud.lefev.re/core/l10n/de.js:1:1
ReferenceError: OC is not defined
[Weitere Informationen]
de.js:1:1

https://cloud.lefev.re/apps/files_clipboard/l10n/de.js:1:1
ReferenceError: OCA is not defined
[Weitere Informationen]
previewplugin.js:122:1

https://cloud.lefev.re/apps/files_pdfviewer/js/previewplugin.js:122:1
ReferenceError: OC is not defined
[Weitere Informationen]
viewer.js:15:3

https://cloud.lefev.re/apps/files_videoplayer/js/viewer.js:15:3
ReferenceError: OC is not defined
[Weitere Informationen]
de.js:1:1

https://cloud.lefev.re/apps/gallery/l10n/de.js:1:1
ReferenceError: OC is not defined
[Weitere Informationen]
fileinfo.js:147:1

https://cloud.lefev.re/core/js/files/fileinfo.js:147:1
ReferenceError: OC is not defined
[Weitere Informationen]
client.js:839:1

https://cloud.lefev.re/core/js/files/client.js:839:1
ReferenceError: OC is not defined
[Weitere Informationen]
contactsmenu.js:537:1

https://cloud.lefev.re/core/js/contactsmenu.js:537:1
ReferenceError: OCA is not defined
[Weitere Informationen]
theming:2:2

https://cloud.lefev.re/apps/theming/js/theming:2:2

https://cloud.lefev.re/apps/theming/js/theming:1:2

Seems this is blocking the login (and probably anything else).
I post that real quick and search for a solution for that. Just that you maybe get an idea already.

1 Like

Well yeah, for plugins that I can disable (like contacts) the error goes away (but that’s completely not normal already), but for the core files, there is nothing I can do…

I’m all for nextcloud, but if I minor update like that broke everything, it’s not ready for mass adoption.

No no, disabling the apps will not help. It’s not about the apps. Mandatory files can’t be loaded and the apps mentioned there are just indicating that.

If I understand it correctly, then
/home/cloud/public_html/nextcloud/core/js/js.js

is the file that defines the variables/ objects OC and OCA. And this js file is not processed for any reason.
I assume this file exists and is readable with correct permissions for the web server user. On github I found some OC/ NC issues describing that problem, but never with a (well documented) solution.
One reason I read about, was a misconfigured nginx and using the default nginx config helped:

Have there been any changes/ optimizations to the configs lately or do you remember making your server in any way “extra secure”?

Could you maybe post your nextcloud.log and the web server logs? I’m hoping to find another hint there.

mm no, I haven’t changed anything for a while, and I just followed the recommendations from the admin panel, nothing more. The errors are all like the one I posted earlier, about SCSScacher.php

Just found that:

Can you try commenting out „instanceid=>‘XXX‘“ and „theme=>‘‘“ and refresh your login page?

1 Like

I can confirm this issue.

  • During and after the update the buttons on the web interface were not working (therefore needed to finish upgrade through CLI)
  • One of my browsers was logged in, and still is. It seems as if the CSS files are not loaded and applied.

Commenting out instanceid and removing theme did not resolve the issue

Same here, commenting didn’t fix the problem :frowning:

Not sure it will work for you but another user reported this command solved the problem:

./occ maintenance:mimetype:update-js

Source:

1 Like

Thank you for the suggestion; did not help out…

@arvi89: did mostly same things (removed redis cache, restart all related services, …) - same outcome

Yep, doesn’t work.
I’ve deactivated pagespeed from my server, also removed the apcu and redis cache from the config, removed instance ID restarted apache, still the same problem.

Could you set the loglevel to “0” (debug), reload the page, do something on the server and post the latest logs of nextcloud.log.

And there are no log entries in the logs under
/var/log/apache2/
?

We are coming to a point, where I believe it is best to open an issue on Github:

The more we try, the more we could make it worse.

I hope you have a backup.

Tried to remove the theming app as per


but no help - reverting back might be a good idea indeed…

@Hartwin Are you willing to share your NC url?
I’d like to check if I can see the same error messages and behavior on your site.

I just noticed for the server of arvi89 that the JS debugger (Firefox web developer tools) doesn’t load anything for his site. Not an expert on that, but seems strange to me, because on my site it instantly gives me a good overview of all loaded js files.

So I’m still sticking with a potential Javascript issue.

And by the way: javascript loads the CSS files.

Nope, I really thought that for a minor version like that there wouldn’t have any problem.
What worries me is that with my logged in browser, even with everything broken, I could read that the instance was empty (while I actually have 17 GB).

Disabling theming doesn’t work, that’s the first thing I’ve tried.

@arvi89: Through the client-app I can still edit and see all data;; so it seems really an interface-issue…

1 Like

I just got a message that told me all files from my instance were deleted. Awesome. This is BS.

(but at least the files are still in my openstack bucket)

We both are using swift, which might play a role here? - I use it as primary storage; do you?

@Schmu Did you get the URL? Any thoughts or guidance? Thank you!

Yeah, that’s my primary storage too. You might be right, this might be related.