Websocket ошибка 1006

Thought this might be handy for others. Knowing regex is useful, kids. Stay in school.

Edit: Turned it into a handy dandy function!

let specificStatusCodeMappings = {
    '1000': 'Normal Closure',
    '1001': 'Going Away',
    '1002': 'Protocol Error',
    '1003': 'Unsupported Data',
    '1004': '(For future)',
    '1005': 'No Status Received',
    '1006': 'Abnormal Closure',
    '1007': 'Invalid frame payload data',
    '1008': 'Policy Violation',
    '1009': 'Message too big',
    '1010': 'Missing Extension',
    '1011': 'Internal Error',
    '1012': 'Service Restart',
    '1013': 'Try Again Later',
    '1014': 'Bad Gateway',
    '1015': 'TLS Handshake'
};

function getStatusCodeString(code) {
    if (code >= 0 && code <= 999) {
        return '(Unused)';
    } else if (code >= 1016) {
        if (code <= 1999) {
            return '(For WebSocket standard)';
        } else if (code <= 2999) {
            return '(For WebSocket extensions)';
        } else if (code <= 3999) {
            return '(For libraries and frameworks)';
        } else if (code <= 4999) {
            return '(For applications)';
        }
    }
    if (typeof(specificStatusCodeMappings[code]) !== 'undefined') {
        return specificStatusCodeMappings[code];
    }
    return '(Unknown)';
}

Usage:

getStatusCodeString(1006); //'Abnormal Closure'

{
    '0-999': '(Unused)',
    '1016-1999': '(For WebSocket standard)',
    '2000-2999': '(For WebSocket extensions)',
    '3000-3999': '(For libraries and frameworks)',
    '4000-4999': '(For applications)'
}

{
    '1000': 'Normal Closure',
    '1001': 'Going Away',
    '1002': 'Protocol Error',
    '1003': 'Unsupported Data',
    '1004': '(For future)',
    '1005': 'No Status Received',
    '1006': 'Abnormal Closure',
    '1007': 'Invalid frame payload data',
    '1008': 'Policy Violation',
    '1009': 'Message too big',
    '1010': 'Missing Extension',
    '1011': 'Internal Error',
    '1012': 'Service Restart',
    '1013': 'Try Again Later',
    '1014': 'Bad Gateway',
    '1015': 'TLS Handshake'
}

Source (with minor edits for terseness): https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent#Status_codes

At the end of the installation of the code server, you are ready to enjoy your new development workflow, and then, you see this message “WebSocket close with status code 1006”. How to solve it? Check out these answers

Note: If you are confused about what code server is, check this post which explains it.

TL;DR

Check your https connection. Your browser cannot reach your code server instance.

What is the websocket 1006 error?

The websocket 1006 error means that the connection has been closed, locally, by your browser.

If you see a close code 1006, you have a very low level error with WebSocket itself as this error is not really meant for the user. The websocket 1006 error points to a low level issue with your code and implementation.

Why do I see this error?

The main reason is that the connection was closed abnormally (locally) by the browser implementation.

It means that your browser cannot reach your remote code server.
The main issue is about your https connection to the server.

How to fix it?

You might not be sure about the process to follow in order to setup code server. I did a tutorial on how to setup code server cloud IDE platform on digitalocean using kubernetes.

If you speak french, the french version is here.

The good news is that, there are two possible solutions :

Use the –link parameter to get a temporary https

Option 1 : get the link locally

code-server --host 127.0.0.1 --bind-addr 0.0.0.0:9000 --auth password --link

Option 2 : Use ngrok

ngrok will tunnel and create an https connection to your server.

code-server --host 127.0.0.1 --bind-addr 0.0.0.0:9000 --auth password ngrok http 9000

Use wss to forward

Here is the code to perform the forwarding and solve the issue

// forward websocket (wss -> ws)
httpsServer.on('upgrade', function (req, socket, head) {
  proxy.ws(req, socket, head, {
    target: 'ws://...',
    ws: true
  })
})

You may get into a related type of issue where [[2022-01-02-how-does-code-server-works.md|code-server c]]omplains about the bindings file. The solution is in this blog post about solving binding file not found error.

Also, kubernetes and minikube are great choices to host code server.

Ubuntu 16.04, стек LAMP, для работы с websocket использую библиотеку workerman. Порт открыт в firewall (ufw). Соединение устанавливается корректно, сообщения отправляются, но при попытке чистого закрытия соединения через close как со стороны js так и со стороны сервера соединение у клиента закрывается с ошибкой 1006, без других подробностей. Еще на сервере установлен OpenVpn, но на другом порту. Есть какие-то идеи что это может быть и возможно какие-то шаги для дополнительной отладки чтобы конкретизировать/выяснить причину?

• 
  Вопрос задан
  
  более трёх лет назад
  

• 9236 просмотров

I’m using Redis + Webdis on Debian 7 32.

My issue is that all websocket connections are closed with the exit code 1006 after completing the first command (except the «SUBSCRIBE» one). For example, for this testJSON() function

function testJSON() {
  var jsonSocket = new WebSocket("ws://ip:7379/.json");
  jsonSocket.onopen = function() {
    console.log("JSON socket connected!");
    jsonSocket.send(JSON.stringify(["SET", "hello", "world"]));
    jsonSocket.send(JSON.stringify(["GET", "hello"]));
  };
  jsonSocket.onmessage = function(messageEvent) {
    console.log("JSON received:", messageEvent.data);
  };
  jsonSocket.onclose = function(messageEvent) {
    //some logging
  };
  jsonSocket.onerror = function(messageEvent) {
    //some logging
  };
}
testJSON();

i’m getting (in Firebug)

JSON socket connected!
JSON received: {"SET":[true,"OK"]}
onClose: error.code 1006

The onError event is’nt working, and after the {«SET»:[true,»OK»]} response my connection closes. GET command is’nt working too. Same behavior in Firefox and Chrome. I checked the headers, it seems they are valid.

Any suggestions?