Errors thrown by use of electron.net.request
See original GitHub issueUnder electron 1.6.2 I tried running installExtension in the renderer process, but it threw all sorts of errors which appeared to be related to the use of electron.net.request (if I changed https://github.com/MarshallOfSound/electron-devtools-installer/blob/master/src/utils.js#L13 to use http.request it worked fine).
I switched to running installExtension in the main process in the app.on('ready' event handler, that works great.
I’m not sure if there’s a bug here regarding the use of electron.net.request or if the documentation just needs updating to indicate where to run installExtension
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Electron - throws ERR_FAILED when making requests using Net
I am using Electron 8 and making a internet connection check by making a request to api. The connection check was made every...
Read more >"certificate-error" app event should emit when "net" requests fail
The certificate-error event is not actually emitted when net requests are made. Setting a BrowserWindow's window.location to any https address ...
Read more >net - Electron
The net module is a client-side API for issuing HTTP(S) requests. ... Trying to use the module before the ready event will throw...
Read more >Error Handling in ElectronJS - GeeksforGeeks
In this tutorial, we will look at Error and Exception handling in an Electron application using the electron-unhandled external npm package.
Read more >chromium-net-errors - npm
Chromium network errors for Electron and Chromium-based JavaScript environments. Latest version: 13.0.0, last published: 2 years ago.
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

Same error here
@Polarisation Dayum, I had those errors on one machine a few weeks back but couldn’t figure out what was causing it. Guess it was
networking from the renderer process causing the issues on a machine that hadn’t used Electron before. Will investigate that issue upstream 👍