Skip to content

[Bug]: [ERROR] files: SW registration failed: NS_ERROR_CONTENT_BLOCKED #38219

Closed

Description

@ChristophWurst

⚠️ 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

Activity

  1. szaimen commented on May 12, 2023

    @szaimen
    Contributor

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

  2. skjnldsv commented on Jun 28, 2023

    @skjnldsv
    Member

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

  3. added and removed
    1. to developAccepted and waiting to be taken care of
    on Jun 28, 2023
  4. ChristophWurst commented on Jun 28, 2023

    @ChristophWurst
    MemberAuthor

    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.

  5. skjnldsv commented on Jun 28, 2023

    @skjnldsv
    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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions