Failed to load resource: net::ERR_CONNECTION_CLOSED
See original GitHub issueI’am using gulp for run browser-sync.
var gulp = require('gulp'),
browserSync = require("browser-sync");
gulp.task('default', ['browser-sync']);
gulp.task('browser-sync', function() {
browserSync({
server: {
baseDir: "./",
directory: true
}
});
});
but google-chrome push in console
GET https://localhost:3000/browser-sync/socket.io/?EIO=3&transport=polling&t=1426265203441-31 net::ERR_CONNECTION_CLOSED
ver. browser-sync -> 2.2.3
Issue Analytics
- State:
- Created 9 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
How To Fix "ERR_CONNECTION_CLOSED" in Chrome (13 ...
The ERR_CONNECTION_CLOSED message is an error that you might see in Chrome when you try to access a website. It means that something's...
Read more >How to Fix Error Connection Closed Error in Google Chrome?
One of the popular errors is connection closed error that you will see in the browser as “Err_Connection_Closed”. This generally occurs in ...
Read more >ERR_CONNECTION_CLOSED: How to fix the connection error
Solution 1: Check internet connection and restart router if necessary · Solution 2: Reset network settings · Solution 3: Disable proxy server and ......
Read more >Guide to Fix ERR_CONNECTION_CLOSED Error on Google ...
For example, the Google Chrome error message: ERR_CONNECTION_CLOSED is one from the wide array of Google Chrome errors, which tells you that your...
Read more >How to Fix ERR Connection Closed Error in Chrome Browser
ERR Connection Closed Error in Chrome Browser · 1. Clear Browsing Data · 2. Disable Proxy Server · 3. Flush DNS and Reset...
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 FreeTop 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
Top GitHub Comments
Changed socket config, and now works
+1. Switch to https caused many problems in my dev environment. Anyway to use http in Chrome? Thanks.