Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error loading webview: Service Workers are not enabled in browser. Webviews will not work.
See original GitHub issueError loading webview: Service Workers are not enabled in browser. Webviews will not work.
- Web Browser: chrome
- Local OS: windows10
- Remote OS: ubuntu20
- Remote Architecture:
code-server --version: v3.7.4
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Error loading webview: Service Workers are not enabled in ...
when I want to install a extension i just got this: Error loading webview: Service Workers are not enabled in browser. Webviews will...
Read more >Error loading webview: Error: Could not register service ...
56.2 and open webview, I get these messages: Error loading webview: Error: Could not register service workers: TypeError: Failed to register a ...
Read more >Error: Could not register service workers: SecurityError: The ...
ACTUAL RESULTS: An error notification appears at the bottom right of the editor UI, which says: "Error loading webview: Error: Could not register...
Read more >Webview API - Visual Studio Code
Webviews run in isolated contexts that cannot directly access local resources. This is done for security reasons. This means that in order to...
Read more >chrome.webviewTag - Chrome Developers
Use the webview tag to actively load live content from the web over the ... Note that if an error occurs during creation,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have exactly the same issue and I’m using https:
A probable root cause, use https instead of http if you did !