-
Notifications
You must be signed in to change notification settings - Fork 47
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
Could not find resource firstrunwizard/js/personalsettings.js to load #1231
Comments
I get the error message also... I am running version 29.0.2, and the error does occur when visiting the “Mobile & desktop” tab. |
I have the same issue on 29.0.2 installed on TrueNAS Scale. [jsresourceloader] Error: Could not find resource firstrunwizard/js/personalsettings.js to load |
Experiencing the very same issue on Nextcloud Server version 29.0.2 in a dockerized environment. I'm using postgres as DB server and these are my environment variables of the nextcloud:apache (latest) container:
I can provide more info if needed, please just let me know. I'll subscribe to this thread to stay updated on any further info regarding it. Thanks y'all. |
Also have this issue with the latest aio. no custom settings or config for the base deployment. |
Steps to reproduce
Expected behaviour
Nothing new appears Admin Error log
Actual behaviour
Everytime a user accesses the “Mobile and Desktop” tab under personal settings, the following error is added to the log:
Server configuration
Operating system: Ubuntu 20.04
Web server: Apache 2.4 (perhaps not relevant)
Database: MySQL 8.0.36 (perhaps not relevant)
PHP version: 8.1.27 (perhaps not relevant)
Nextcloud version: 29.0.1
Where did you install Nextcloud from: Official GitHub release (updated to 29 via web-updater)
List of activated apps:
Nextcloud configuration:
Client configuration
Browser: Firefox 126.0 (perhaps not relevant)
Operating system: Ubuntu 20.04 Desktop (perhaps not relevant)
Logs
Nextcloud log (data/owncloud.log)
Browser log
This is just a copy from Nextcloud Help thread where several users (including me) reporting similar problem, it seems to be a bug.
The text was updated successfully, but these errors were encountered: