WebSocketServer | A light and high performance WebSocket Server | Websocket library

The problem was not specifying the protocol when accepting the connection. After about 20 hours working on the same bug and implementing an SSL certificate to get it to work, I changed:

If you are wanting to assign a room at connection you change the path of the url and then access it through the req object, then add it as a property on the connecting websocket.

Then you can send the roomId with any message and check that the roomId for message and the roomId for the client match before sending.

You have to call the close() method on the workers:

app created by express() doesn't have a close method. But const server = http.createServer(app);, the server has a close method.

You can start the server and listen to the connections in beforeAll and call server.close in afterAll. To achieve this, you need to export server so that the test file can get the server.

The statement inside the if (require.main === module) block will only be executed when running this script by node server.js.

E.g.

app.ts

Keep it easy.
Certs inside your application are complex - they are hard to manage and you will get problems to run your application in a modern cloud environment (start new environments, renew certs, scale your application, ...).

Simple conclusion: Dont implement any certs.

As Mike already pointed out in the comments: WebSockets are just upgraded HTTP(S) connections. A normal webserver (nginx, apache) takes care about the certs. It can be done in kubernetes (as ingress-controller) or with a "bare-metal" webserver.
Both of them should act as a reverse-proxy. This means: Your java-application doesn't know anything about certs. It has just unencrypted connections - like in your code on port 6868.
But the client will not use this port. 6868 is only internally reachable.

The client will call your reverse-proxy at the normal HTTPS port (=443). The reverse-proxy will forward the connection to your java-application.

Here some links for further information:

• nginx reverse-proxy
• nginx reverse-proxy for websocket
• tutorial for java behind reverse-proxy
• LetsEncrypt for automatic and free certs

The reason why there is no response when you connect to the websocket is because you do not have the HTTP endpoint setup in your backend express app.

When you connect to the AWS API Gateway WebSocket API, WebSocket API takes action set by your $connect integration. In your current configuration, you have set the VPC Link integration with HTTP Method Any on the target url. Thus, for your backend endpoint to be called, you need to create a HTTP endpoint and set the address of the endpoint to "Endpoint URL."

For example, let's say you have the following route set up.

NestJS Gateway by default uses an AbstractWsAdapter, not certainly sure what Adapter implements it by default.

However, I couldn't find a way to get control over the server creation without a custom adapter, and I didn't want to start another server dedicated for the websocket, but instead use the http server that is used for nest rest API.

So what I did to solve this issue is, first implement the HTTPS server in the place you bootstrap your nestjs application:

I don't have any experience with WebSocketSharp, but the docs says you can give an alternate WebSocketBehavior construction function to the AddWebSocketService<>

Let me know if it works: (else i'll remove it)

I can assume the error appeared after migration to the latest version of Webpack/DevServer, they did several breaking changes, including devServer settings. Especially for this issue try to use this code instead of contentBase: