express-ws | WebSocket endpoints for express applications | Websocket library

Bizarre situation going on here with my websocket. It's giving me the error Error during WebSocket handshake: Unexpected response code: 200 Which for the life of me I cannot figure out why.

I've set up a very similar server with the exact same code with the exact same servers & settings. The only difference is one server has a .com TLD while the other has a .sg TLD.

I've reduced it down to the simplest form, which is the below and the error is still happening. It's on the api side for sure and not the frontend as the frontend can connect to the .com TLD.

Below is all the code that I believe is related to the problem. If you think there might be other areas please ask and I will post other areas. It's hosted on AWS Elastic Beanstalk. I've also set the SSL cert to domain.com & *.domain.com

Does anybody know why this might be happening?

The bizarre thing to me is I literally set up a server with these exact settings and it's working perfectly fine.

server.js (start point in package.json)

Our websockets are working under Http/express but when I move to https.createServer I cant get a socket connention.

FYI:The project is almost complete and we are in deep with express-ws, so we cont change the socket lib at this stage

Here is an example of my code:

I have a Node/React project in my Webstorm that won't run because of this error. I had to reinstall Windows and start fresh with my development. I got the code back into the IDE, but when I start up the Node server, I am getting the following error: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined

More context for that error:

My website runs on https/ssl (valid CA certificate) on IIS 10.0 (iisnode 0.2.21) / node/express. I am using a websocket server on top of https server (same port)

However the websocket connection works very well for CHrome and IE11. It fails only for Firefox (version 80) with error code 1006 (error details)

in Inspector / Network console, it gives the following errorerror as shown in network under inspector console

In the web.config file, I have added the following line

app.js code is as below:

In my small project, I want to build a BabyCam that can be accessed from any web browser using a Raspberry Pi Zero. For this, I would like to open a web socket using express-is to stream video to several clients. I am basing most of the video-related code on the raspivid-stream module. However, when trying to access the web socket, I get a type error for app.ws(... stating Property 'ws' does not exist on type 'Application'. Of course, I imported both the typings for express and express-ws.

I am not really sure, what the problem is as the same call in JavaScript appears work fine. Here's the code - I am glad for any help!

I've created a react project with the instructions from it's documentation, which automatically has added the App.js file to the project. My issue is that I want to use App.tsx instead of App.js. For some reason, I am not able to run App.tsx file. How can I fix this, please?

I have read this question asked here, but I couldn't use it as it didn't make any sense to me since this is my first project with react.

This is my folder structure.

It can be seen on this image, I get an error on the browser when I comment it out the App.js file.

This is the index.js file, which is not changed.

I implemented the nexmo provided example code (below) into my server. However, I'm running into an issue where if 2 callers ping my server, the second caller's binary data also streams into the same websocket endpoint; thus resulting in two binary streams into the same websocket endpoint. How could I implement nexmo so that each caller has their own websocket to connected to an agent? I believe socket.io is the solution, however I'm unfamiliar with it.

I have a node js app that receives data from a sensor device via POST requests. It also serves frontend to monitor that data. I want it to send data updates via websocket to all connected clients

Here's what I came up with:

I am creating an application(Nuxtjs) and am having troubles determining a good approach for sending data to the API(expressjs) and retrieving real-time updates. It seems that i can create "bi-di" connections with both protocals [Server Sent Events(SSE) and Axios or Websocket(WS)].

Both technologies work with most of the browsers, so i do not see a need to add additional libraries such as socket.io - For those individuals that do not have a current browser (too bad).

The application is based on user input of form data/clicks. Other users are then notified/updated with the information. At which point, the user can respond and the chain goes on(Basic chat like flow some information will be exchanged quickly while some may not or ever).

In my experience, the user flow would rely more heavily on listening for changes than actually changing the data - hence why i'm considering SSE. Unfortunately, both protocols have their flaws.

Websockets:

1. Not all components will require a WS to get/post information as such it doesn't make sense to upgrade a basic http connection at the additional server expense. Therefore another method other than WS will be required(Axios/SSR). Example: Checking to see if a user name exists
2. Security firewalls may prevent WS for operating properly
3. express-ws makes sockets easy on the API end
4. I believe you can have more than 6 concurrent connections by one user (which may be pro and con)

Server Sent Events

1. Seems like the technology is fading in favor of WS
2. Listening to the events seem to be as easy as listening to events for WS
3. No need to upgrade the connection but will have to use node-spdy within the expressjs API - This may also be a good implementation for WS due to multiplexing
4. Little more backend code to setup http2 and emit the SSEs(Ugly code as well - so functions will be made)
5. Limited to HTTP limitations (6 concurrent connections) which is a problem as the users could easily max this out(ie. having multiple chat windows open)

TLDR

The application will be more "feed" orientated with occasional posting(which can be handled by Axios). However, users will be listening to multiple "feeds" and the HTTP limitations will be a problem. I do not know what the solution would be because SSE seem like the better option as i do not need to continually handshake. If this handshake is truly inconsequential(which from everything i have read isn't the case) than WS is likely a better alternative. Unfortunately, there is soooo much conflicting information regarding the two.

Thoughts?