Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8196949
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T05:38:10+00:00 2026-06-07T05:38:10+00:00

using node.js and socket.io to serve websockets does socket.io need to be listening on

  • 0

using node.js and socket.io to serve websockets

does socket.io need to be listening on port 80 – the real port for websockets, or can it be proxied to a different port, eg, port 8011, on the server?

the browser, using websockets, talks through 80/http. on the server haproxy redirects websockets to node.js.

right haproxy directs to 127.0.4.11:80. this works fine, but this requires sudo to run node.js.

would rather redirect to localhost:8011, but do not know if socket.io needs to actually be on port 80 to support websockets correctly.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-07T05:38:12+00:00Added an answer on June 7, 2026 at 5:38 am

    WebSockets (and Socket.IO) can run on any port; most developers will develop their servers on a high-numbered port specifically to avoid running as root in development. Furthermore, the Socket.IO wiki has a page on ports and which ones work for various firewall software.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm interested in using Node.js as a socket server for stream-based communication with tens
Here's my problem: I have server A, running node.js and using socket.io for communicating
I am using Node.js with socket.io to implement websockets in one of my pages.
I'm using Node.js and Socket.io. I've written an application which can send JavaScript snippets
I'm using node.js and socket.io and doing a server/client thing. On my Server, is
I'm using node.js and socket.io and doing a server/client thing. On my Server, is
I am using socket.io to connect to my node server using the following script:
When using socket.IO in a Node.js server, is there an easy way to get
I have a socket.io server using redis called server.js that fires up a node
I have created a small server for communication using node.js and socket io Server:

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.