sockjs-node (Not Found) #1472

mavajee · 2018-06-05T06:17:51Z

Version

3.0.0-beta.15

Reproduction link

https://jsfiddle.net/w0jg8bdr/

Steps to reproduce

Use with nginx

What is expected?

HMR working with nginx

What is actually happening?

I use 3 version of vue cli and nginx. And each vue app have different sockjs-node path.

vue cli 10 have path 0.0.0.0:8082/sockjs-node/*** and it's work

vue cli 12 have path http://localhost.com:8082/sockjs-node/*** and it's work to

vue cli 15 have path http://localhost.com/sockjs-node/*** and it's not work. How you can see port is missing

UPD. If i run app on 0.0.0.0:8082 without nginx all work fine

maybe this commit is the reason or this

It's bug or just I not correct config my app?

mavajee · 2018-06-05T06:23:21Z

I found the trouble, in this commit line 70, if remove '?/sockjs-node', all work

mavajee · 2018-06-05T07:47:38Z

versions 10 has the best correct sockjs path to dev serve from any host name.

jkzing · 2018-06-05T08:45:56Z

Umm, it should not work like that. What is baseUrl in your vue.config.js?

mavajee · 2018-06-05T10:36:28Z

@jkzing I try use baseUrl but it not work. in ver 10 I used absolute path to work with nginx

config.output.publicPath = http://${host}:${port}/

because need all request send to webpack dev server

UPD: I try '/' baseUrl
UPD: All files on dev server located in '/'.

yyx990803 · 2018-06-05T13:54:46Z

@mavajee you should not be mutating publicPath because this value needs to be used in other places in addition to the wepback config. Use the baseUrl option.

Akryum · 2018-06-05T13:59:42Z

@yyx990803 Maybe we could check that and display the like of Don't change webpack 'ouput.publicPath' directly, use vue.config.js 'baseUrl' instead.

yyx990803 · 2018-06-05T14:17:45Z

@Akryum that would be nice although it's a bit difficult to precisely detect that

jkzing · 2018-06-05T15:33:18Z

I guess OP's usage is like having a baseUrl: 'http://localhost:8082/' in vue.config.js.

With a nginx config like:

server {
  listen 8082 default_server;
  location / {
    proxy_pass  http://localhost:8080;
    proxy_set_header Host $host;
  }
}

Then open http://localhost:8082 in browser.

In above case, current strategy to fix the socket url to '/sockjs-node' is not enough, maybe we need to fix it to 'http://localhost:8080/sockjs-node'.

mavajee · 2018-06-05T15:47:15Z

Thank you for answers. I will check it tomorrow.

What if make '/sockjs-node' url same absolute dev server url. Anyway HMR and sockjs work only with dev server

mavajee · 2018-06-06T05:58:03Z

@jkzing, hi, now it work for me, but if i put to baseUrl absolute url, I have this (just incorrect display, but all work)

vue.config.js

const path = require('path')

const host = '0.0.0.0'
const port = 8085

module.exports = {
  lintOnSave: false,
  baseUrl: `http://${host}:${port}/`,

  devServer: {
    port,
    host,
    hotOnly: true,
    disableHostCheck: true,
    clientLogLevel: 'warning',
    inline: true,
    headers: {
      'Access-Control-Allow-Origin': '*',
      'Access-Control-Allow-Methods': 'GET, POST, PUT, DELETE, PATCH, OPTIONS',
      'Access-Control-Allow-Headers': 'X-Requested-With, content-type, Authorization'
    },
  }
}

mavajee · 2018-06-06T06:35:35Z

and about historyApiFallback, just my usage situations. If use absolute url, it's will make some troubles.

jkzing · 2018-06-06T11:49:18Z

@mavajee Just FYI, if current historyApiFallback not works for you, you can still overwrite it in vue.config.js.

mavajee · 2018-06-06T12:58:28Z

@jkzing, yes I did it, i think it comment will be helpful for you

linguamatics-albert · 2018-06-13T08:39:33Z

Sorry to bother you guys again with this.

I'm finding a similar issue but I'm not so sure is related to this, so just in case I prefer to drop the comment here.

This one comes when running vue-cli-service serve --host xyz. When running it rise the webpack dev server successfully with everything, but the hot reload it won't work. A further inspection on the error log it shows that the webpack dev server cannot reach sockjs-node:

sockjs.js?9be2:1601 GET http://localhost:8080/sockjs-node/info?t=1528877926478 net::ERR_CONNECTION_REFUSED

but the webpack dev server was opening in the hostname specified by the --host flag.

In previous versions of vue-cli I was doing the same thing and I didn't got the same problem.

I've got the suspicious that this comes because here:

https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/cli-service/lib/commands/serve.js#L89

urls.lanUrlForConfig is always undefined when setting a host name through --host flag, therefore it will always spawn sockjs-node to localhost.

But maybe I'm doing something wrong. Am I missing something?

I'm suing webpak 4.12.0 which I believe that is the one that it get install when running vue create myProject

jkzing · 2018-06-13T11:35:07Z

@linguamatics-albert , It's actually a bug of serve command, it should not act like that.

As a work around, you can use devServer.public in vue.config.js to specify your host.
Which is included in this PR #1526.

srchulo · 2019-03-31T20:48:18Z

I think this issue still happens if you have a path at the end of devServer.public:

devServer: {
    host: '0.0.0.0',
    public: '0.0.0.0:8080/app',
    disableHostCheck: true
},

I can get it to work if I remove /app. As a workaround, I've done this in my vue.config.js for the vue project that's doing the proxying:

proxy: {
    '/app': {
        target: 'http://frontend_app:8081',
        changeOrigin: true,
        pathRewrite: {
            '^/app/sockjs-node': ''
        },
    }
}

This fixes the sockjs-node not found error, however, now hot reload doesn't seem to be working.

srchulo · 2019-03-31T20:56:48Z

Also, this error only started occurring for me once I upgraded to vue cli 3 from 2.

srchulo · 2019-03-31T21:05:39Z

Never mind, I thought my above solution worked, but it looks like it doesn't.

Goldziher · 2019-07-21T08:37:45Z

This error is still occuring. I'm working on a multi vue app project that is contained within an nginx layer. Whenever I try to upgrade one of the apps (all using vue-cli 3) to a newer version of the vue-cli, or run yarn upgrade on vue-cli or any of its plugins, this errors occurs.

Any suggested fix?

iamface · 2019-08-27T00:21:56Z

I used @srchulo's comment and added the following to my vue.config.js and the error went away for me using cli 3.0.

host: '0.0.0.0',
public: '0.0.0.0:8080',
disableHostCheck: true

I'm assuming this only occurs to the dev server and does not happen in production build?

amravazzi · 2019-10-19T16:37:10Z

I'm having a kind of different problem. I'm using apollo-client and getting this error in console, twice every time I reload the page:

WebSocket connection to 'ws://localhost:8082/sockjs-node/355/xgym14in/websocket' failed: Unknown reason

Here is my vue.config.js:

module.exports = {
  baseUrl: 'http://localhost:8082/',
  devServer: {
    public: 'localhost:8082',
    host: 'localhost',
    port: 8082,
    disableHostCheck: true,
    headers: {
      'Access-Control-Allow-Origin': '*',
      'Access-Control-Allow-Headers': 'Origin, X-Requested-With, Content-Type, Accept'
    }
  }
}

I spent 2 days searching in Google, but couldn't find anything useful. Any help?

chanlito · 2019-10-26T08:50:22Z

@amravazzi same here.

marcoippolito · 2020-01-23T12:37:02Z

In Ubuntu 18.04.03 Server Edition and with vue@2.6.11, I'm getting these error messages, when deploying my starting-page of webapp with vue.js:
GET https://192.168.1.7:8081/sockjs-node/info?t=1579780726858
net::ERR_SSL_PROTOCOL_ERROR
GET https://192.168.1.7/sockjs-node/info?t=1579780726857
net::ERR_CERT_COMMON_NAME_INVALID

This is my vue.config.js file :

module.exports = {
  productionSourceMap: false,
  pluginOptions: {
    i18n: {
      enableInSFC: true
    }
  },
  devServer: {
    host: '192.168.1.7',
    hot: true,
    disableHostCheck: true
  }
}

How to solve the problem?

Monakiel · 2020-05-16T12:04:19Z

I used @srchulo's comment and added the following to my vue.config.js and the error went away for me using cli 3.0.
host: '0.0.0.0',
public: '0.0.0.0:8080',
disableHostCheck: true
I'm assuming this only occurs to the dev server and does not happen in production build?

1 year later but I had trouble finding a solution too. And yours worked. Thanks!

RodrigoBertotti · 2021-09-18T18:19:32Z

@jkzing, hi, now it work for me, but if i put to baseUrl absolute url, I have this (just incorrect display, but all work)

vue.config.js

const path = require('path')

const host = '0.0.0.0'
const port = 8085

module.exports = {
  lintOnSave: false,
  baseUrl: `http://${host}:${port}/`,

  devServer: {
    port,
    host,
    hotOnly: true,
    disableHostCheck: true,
    clientLogLevel: 'warning',
    inline: true,
    headers: {
      'Access-Control-Allow-Origin': '*',
      'Access-Control-Allow-Methods': 'GET, POST, PUT, DELETE, PATCH, OPTIONS',
      'Access-Control-Allow-Headers': 'X-Requested-With, content-type, Authorization'
    },
  }
}

It worked
thank you!

colorfulyang · 2022-09-20T08:25:19Z

I've got the same problem with @marcoippolito,I wanna know how did you solve this problem at last.@marcoippolito

yyx990803 closed this as completed Jun 5, 2018

jkzing mentioned this issue Jun 5, 2018

fix(cli-service): make sockjs url fixed with hostname #1476

Merged

jkzing referenced this issue Dec 5, 2018

fix: fix hmr in docker + support devServer.public with protocol

da38ed4

ChristianKienle mentioned this issue Apr 16, 2019

Fix publicPath SAP-archive/fundamental-vue#288

Open

haoqunjiang mentioned this issue May 27, 2021

HMR requests are directed to 192.168.x.x, regardless of current host (e.g. localhost) #6491

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

sockjs-node (Not Found) #1472

sockjs-node (Not Found) #1472

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!