FAQ: WebSockets Tutorial: Chatroom - Create a WebSocket Client

This community-built FAQ covers the “Create a WebSocket Client” exercise from the lesson “WebSockets Tutorial: Chatroom”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Learn WebSockets

FAQs on the exercise Create a WebSocket Client

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!
You can also find further discussion and get answers to your questions over in #get-help.

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head to #get-help and #community:tips-and-resources. If you are wanting feedback or inspiration for a project, check out #project.

Looking for motivation to keep learning? Join our wider discussions in #community

Learn more about how to use this guide.

Found a bug? Report it online, or post in #community:Codecademy-Bug-Reporting

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

I’m stuck on this - after completing Exercise 4 (Create a WebSocket Client) unlike the video I still have an error message ‘No Websocket connection’ in the chat app. The console is showing an error but I can’t locate the cause?

I’ve seen comments on StackOverflow about Google Chrome not liking unsecure ws connections to local hosts but i also get the same result in Safari. Anyone able to help me out?

Had this issue when I switched to websocket connection in Exercise 4:
Error: listen EADDRINUSE: address already in use :::8080

The solution for me was here:

for windows:
in VS terminal, type: ]
netstat -ano|findstr “PID :8080”
then :
taskkill /pid [enterPidHere] /f
then retry:
node server.js