Errors in browser console, requests to /sockjs-node/info?t=1555629946494

Question

I created a new site using vue-cli. I'm using the development server to serve the page. When I view the page in my browser, I see two types of errors show up in my browser console:

GET http://172.31.7.153:4000/sockjs-node/info?t=1555922702538 net::ERR_CONNECTION_TIMED_OUT
GET http://localhost:4000/sockjs-node/info?t=1555922708541 net::ERR_CONNECTION_REFUSED

I'm not sure what it means, or how/why it's being called, and it shows up repeatedly about every 5 seconds.

score 52 · Accepted Answer · answered Apr 22 '19 at 08:57

52

I finally fixed it using the devServer.public configuration option.

Below is my vue.config.js file:

module.exports = {
    devServer: {
        disableHostCheck: true,
        port: 4000,
        public: '0.0.0.0:4000'
    },
    publicPath: "/"
}

I got my answer from reading this.

answered Apr 22 '19 at 08:57

Blaine Lafreniere

3,451
6
33
55

1

Thanks for the tip ! – roroland Jun 03 '20 at 21:21
1

Just as a clarifying note the vue.config.js file does not exist by default, you might need to create it at your project root dir – Richard Jan 05 '21 at 18:24
For more info, check [here](https://webpack.js.org/configuration/dev-server/#devserverdisablehostcheck) and [here](https://stackoverflow.com/a/53631238/6736591) – Nakamoto Mar 19 '21 at 01:09
See Nakamto's answer below for a simpler, better version – tog22 Oct 29 '21 at 02:48
It's so frustrating that, as far as I can tell, this config option isn't listed in the documentation. – Nathan Jones Oct 25 '22 at 21:38

Nakamoto · Answer 2 · 2021-03-19T01:33:37.703

31

To disable this warning just the config host: 'localhost' is needed.

module.exports = {
  devServer: {
    host: 'localhost',
  },
};

Create this file vue.config.js if not exist at root.

Note: The disableHostCheck config is officially discouraged.

More info:

edited Mar 19 '21 at 01:33

answered Mar 19 '21 at 01:19

Nakamoto

1,293
14
17

score 2 · Answer 3 · answered May 03 '21 at 18:05

2

I fixed this with the following vue.config.js file:

module.exports = {
  devServer: {
    host: '0.0.0.0',
    https: false,
    port: 8080,
    public: 'http://0.0.0.0:8080'
  },
}

answered May 03 '21 at 18:05

HyperActive

1,129
12
12

score 2 · Answer 4 · answered Dec 20 '21 at 15:04

2

For me this worked in vue.config.js:

module.exports = {
    devServer: {
        public: 'localhost'
    },
}

I also tried to use host like Nakamoto suggested but then the site was not loading anymore.

answered Dec 20 '21 at 15:04

Mano Meter

21
3

score 0 · Answer 5 · answered Sep 17 '21 at 17:45

I know it's a remote case and it does not apply to the OP, yet I bumped into this question and several similar ones after making the silliest mistake: did you turn your Webpack (or other) compiler on?

I wish I had found the hint so I thought I would leave a small life jacket.

[ Background: I missed noticing having forgot to run my npm run serve (it could have been yarn start). At the beginning of my coding session I did not launched Webpack's bash script, so I wasted quite some time trying to figure our what I could have done wrong last night. It had nothing to do with my code. ]

Errors in browser console, requests to /sockjs-node/info?t=1555629946494

5 Answers5

Linked