Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Specified protocol was not requested by the client.

See original GitHub issue

I’ve been using RemixD with great success lately but it looks like the most recent commit caused a bug, at least on my end. Here is the full error log:

Wed Jul 08 2020 09:45:13 GMT-0400 (Eastern Daylight Time) Remixd is listening on 127.0.0.1:65520
/usr/local/lib/node_modules/remixd/node_modules/websocket/lib/WebSocketRequest.js:289
            throw new Error('Specified protocol was not requested by the client.');
            ^

Error: Specified protocol was not requested by the client.
    at WebSocketRequest.accept (/usr/local/lib/node_modules/remixd/node_modules/websocket/lib/WebSocketRequest.js:289:19)
    at WebSocketServer.<anonymous> (/usr/local/lib/node_modules/remixd/src/websocket.js:43:33)
    at WebSocketServer.emit (events.js:209:13)
    at WebSocketServer.handleUpgrade (/usr/local/lib/node_modules/remixd/node_modules/websocket/lib/WebSocketServer.js:217:14)
    at Server.emit (events.js:209:13)
    at onParserExecuteCommon (_http_server.js:603:14)
   at onParserExecute (_http_server.js:543:3)

If I can discover the root of the bug, I’ll make a PR.

Issue Analytics

State:
Created 3 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

sidkocommented, Jul 20, 2020

The above worked for me. Note that I could not get it to work without reinstalling remixd. The steps I took were:

$ npm install -g remixd 
$ remixd -s . --remix-ide https://remix.ethereum.org/
// close the terminal and re-open
$ remixd -s . --remix-ide https://remix.ethereum.org

1reaction

jamesBsmythcommented, Jul 13, 2020

Try reinstalling and causing a rejection error once. For some reason worked for me.

To cause the error, I hosted remixd to serve a bad URL (for example, I put an extra “/” at the end). After causing this error, I restarted remixd with a working URL and was able to reach my files on the remix IDE.

Top Results From Across the Web

Error: Specified protocol was not requested by the client ...

Try constructing it as: var ws = await WebSocket. connect("ws://192.168.0.107:8080/", protocols: ['echo-protocol']); var s = IoWebSocketChannel ...

Specified protocol was not requested by the client. #10 - GitHub

I am trying to connect to a nodejs websocket server using libuwsc and I get the error "Specified protocol was not requested by...

[nodejjs] [websocket] Specified protocol was not requested by ...

this means you have to create a connection at client side like this: var connection = new WebSocket('ws://127.0.0.1:3000', 'echo-protocol');

Specified protocol was not requested by the client. Flutter and ...

It seems that IoWebSocketChannel ignores the protocols parameter. Try constructing it as: var ws = await WebSocket. connect("ws://192.168.0.107:8080/", ...

[workaround] How to define the protocol in websocket in webGL

Only the webgl implementation has standard not a protocol definition. ... error : Error: Specified protocol was not requested by the client