Skip to content
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]: [ERROR] files: SW registration failed: NS_ERROR_CONTENT_BLOCKED #38219

Closed
5 of 9 tasks
ChristophWurst opened this issue May 12, 2023 · 4 comments
Closed
5 of 9 tasks

Comments

@ChristophWurst
Copy link
Member

⚠️ This issue respects the following points: ⚠️

  • This is a bug, not a question or a configuration/webserver/proxy issue.
  • This issue is not already reported on Github (I've searched it).
  • Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
  • Nextcloud Server is running on 64bit capable CPU, PHP and OS.
  • I agree to follow Nextcloud's Code of Conduct.

Bug description

The files service worker doesn't work on my dev instance

[ERROR] files: SW registration failed:  
Object { app: "files", uid: "admin", level: 1, error: Exception }
​
app: "files"
​
error: Exception { name: "NS_ERROR_CONTENT_BLOCKED", result: 2153644038, filename: "https://localhost/dist/files-main.js?v=723d337d-53", … }
​​
columnNumber: 0
​​
data: null
​​
filename: "https://localhost/dist/files-main.js?v=723d337d-53"
​​
lineNumber: 2
​​
message: ""
​​
name: "NS_ERROR_CONTENT_BLOCKED"
​​
result: 2153644038
​​
stack: "71030/<@https://localhost/dist/files-main.js?v=723d337d-53:2:64822\nEventListener.handleEvent*71030@https://localhost/dist/files-main.js?v=723d337d-53:2:64666\no@https://localhost/dist/files-main.js?v=723d337d-53:2:113029\ns<@https://localhost/dist/files-main.js?v=723d337d-53:2:114507\no.O@https://localhost/dist/files-main.js?v=723d337d-53:2:113329\n@https://localhost/dist/files-main.js?v=723d337d-53:2:114521\n@https://localhost/dist/files-main.js?v=723d337d-53:2:114527\n"
​​
<prototype>: ExceptionPrototype { toString: toString(), name: Getter, message: Getter, … }
​
level: 1
​
uid: "admin"
​
<prototype>: Object { … }
ConsoleLogger.js:59:10

Steps to reproduce

  1. Run server 1399c88
  2. Open /apps/files
  3. Look at the console

Expected behavior

No errors

Installation method

None

Nextcloud Server version

master

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

No response

List of activated Apps

N/a

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

FF on Linux
Nextcloud runs on localhost with TLS

cc @skjnldsv

The SW was added in #36534

@ChristophWurst ChristophWurst added bug 1. to develop Accepted and waiting to be taken care of feature: files 27-feedback labels May 12, 2023
@szaimen
Copy link
Contributor

szaimen commented May 12, 2023

I think SW dont work with self-signed cert? cc @skjnldsv

@skjnldsv
Copy link
Member

Self signed isn't compatible for security reason, this is a browser's issue.
You can safely ignore

@skjnldsv skjnldsv added invalid and removed 1. to develop Accepted and waiting to be taken care of labels Jun 28, 2023
@ChristophWurst
Copy link
Member Author

Is there any limitation in Nextcloud when the SW doesn't run? Asking to understand if this might be an issue for instances that use self-signed certs. For my dev instance I don't care a lot.

@skjnldsv
Copy link
Member

No, it will fallback as default behaviour.
The SW is a middleware intercepting specific path for faster cache and delivery :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants