I am brand new to both node.js and to socket.io so this could easily be a problem on my end.

When following the socket.io chat demo exactly as is posted on the current website everything works as one would expect up to the section of "Emitting events", every time I write something in the chat box the page just refreshes and the communication is never logged on the other side. Either something is incorrect or a step is not documented that should be.

Getting a 502 error on the website at: https://socket.io/demos/chat/

Hi
In a page we have those examples

var io = require('socket.io')(3000);
var redis = require('socket.io-redis');
io.adapter(redis({ host: 'localhost', port: 6379 }));

and

var io = require('socket.io-emitter')();
setInterval(function(){
  io.emit('time', new Date);
}, 5000);

But if you try to copy and paste those samples, you find out - that's doesn't work.
Process failed with

    if (!opts.socket && !opts.host) throw new Error('Missing redis `host`');
                                    ^

Error: Missing redis `host`
    at new Emitter (/home/alexander/WebstormProjects/untitled/node_modules/socket.io-emitter/index.js:60:43)
    at Emitter (/home/alexander/WebstormProjects/untitled/node_modules/socket.io-emitter/index.js:47:42)
    at Object.<anonymous> (/home/alexander/WebstormProjects/untitled/index.js:17:45)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:394:7)

Process finished with exit code 0

If we look to socket.io-emitter page on GitHub we find out that we need pass options when creating object

var io = require('socket.io-emitter')({ host: '127.0.0.1', port: 6379 });

but information on page in this page doesn't reflecting this.

For a few days now the website has been intermitently displaying the following error:

Error establishing a database connection

Result from a google search:
http://socket.io/docs/server-api

http://slack.socket.io/ probably shouldn't be a 502 error

Currently:

io.use(function(socket, next) {
  var handshakeData = socket.request;
  // make sure the handshake data looks good as before
  // if error do this:
    // next(new Error('not authorized');
  // else just call next
  next();
});

should be:

io.use(function(socket, next) {
  var handshakeData = socket.request;
  // make sure the handshake data looks good as before
  // if error do this:
    // next(new Error('not authorized'));
  // else just call next
  next();
});

From this page:

We distribute the browser client through our CDN, for free, forever.

<script src=“https://cdn.socket.io/socket.io-1.0.2.js”></script>

This link returns 404, you can test here.

Seems this is a wordpress site. So, the community can't help fix mistakes in the docs.

See : http://socket.io/docs/server-api/#socket#join(name:string[,-fn:function]):socket

There is an invalid link to : https://github.com/socket.io/socket.io-adapter in

that has been configured (see Server#adapter above), defaulting to
socket.io-adapter.

The github page should have http://socket.io/ for the URL field.
And it wouldn't hurt if the README.md linked to http://socket.io/ ✔️

Hey! Thanks for a great library.

Here are some undocumented features from the API that could be mentioned on http://socket.io/docs.

• Namespace#in is like Socket#in but namespaced
• Namespace#emit is like Socket#emit but for a namespace (or room in a namespace)
• Socket#handshake provides various useful bits of info

There are more (Namespace#adapter, for instance).

Overall, I think socket.io's documentation would be much nicer if there was a complete list of all public members & methods in a single location. Right now, the API is partially documented over these three pages: "Server API", "Client API" and "Rooms and namespaces" and they are more like prose than a reference. I often end up having to go spelunking in the source code to see the exact shape of the API.

The DefinitelyTyped TypeScript definition file for socket.io is very useful (though it lacks some minimal comments) but it's incomplete too, probably because it was built from the documented API rather than ground truth.

Anyway, I hope you'll take those comments under consideration, and once again, thanks for all the amazing work!

The slack link in the top nav bar has the title '$count users of online of $total' where the 'total' variable is returning undefined. The issue seems to be here

Hello,

Thank you for this tools, I made it work on localhost, but I would like to make it work on my production server (Apache) with SSL activated and within a subfolder

example
mywebsite.com/websocket

Thanks

For example, path option is not documented, so I had to peruse the socket.io-client codebase to find the option.

This is not optimal. Please add all options.

On http://socket.io/get-started/chat/ the "Emitting Events" section displays some sample code for the client side that includes:

<script src="http://code.jquery.com/jquery-1.11.1.js"></script>

Since a lot of beginners are going to be reading this guide we probably shouldn't give such bad advice, opting instead for https. Incidentally the example code in https://github.com/socketio/socket.io/tree/master/examples/chat is correct; it's just the website that's out of date.

If a certain client is not ready to receive messages (because of network slowness or other issues, or because they’re connected through long polling and is in the middle of a request-response cycle), if they doesn’t receive ALL the tweets related to bieber your application won’t suffer.

Should change to:

... if it doesn’t receive ALL ...

On the demo http://socket.io/get-started/chat/ in the section titled Integrating Socket.IO,

res.sendfile('index.html');

generates the error: express deprecated res.sendfile: Use res.sendFile instead index.js:6:9

It can fixed by replacing the line with

res.sendFile(__dirname + '/index.html');    

https://cloudup.com/c5pAnGgulN7

I don't know if this belongs here, but there's a typo at get-started/chat/
I'm using Google Chrome Version 35.0.1916.114 m
Under Intergrating Socket.io:

Now in index.html I add the following snippet before the </body>:

It is supposed to be right?

... yet github seems to be up to 1.7.2. This is confusing, to say the least...

Perhaps the button could say, "Download Socket.io"...

Although the page at http://socket.io/download/ has a link to your CDN that specifies 1.4.5... It'd be nice to have a consistent story.

502 Bad Gateway

nginx/1.5.11

No AAAA records are returned:

# dig cdn.socket.io AAAA +short
d2vgu95hoyrpkh.cloudfront.net.

Since the CDN endpoint seems to use CloudFront, fixing this should be as easy as enabling IPv6 on the CloudFront distribution (d2vgu95hoyrpkh.cloudfront.net).

I get following error: "502 | An error occured with your deployment." trying to access https://socket.io

• link in header is broken
  • is slack.socket.io
  • should be socket.io/slack
• signup form is broken on socket.io/slack is also broken

The page http://socket.io/docs/client-api/ wouldn't display anything at all.

The problem seems to be here:

 <script type='text/javascript' src='http://socket.io/wp-includes/js/jque
           End of file reached when inside an attribute value. Ignoring tag.

http://socket.io/docs/rooms-and-namespaces/#custom-namespaces
In the example below :
console.log('someone connected'):
A colon is used instead of a semi-colon.

Same issue : http://socket.io/docs/rooms-and-namespaces/#joining-and-leaving

io.to('some room').emit('some event'):

Hey 👋

I think it would be nice to add search to the documentation and tutorials, since it's quite a bit faster than going through different pages.

At Algolia we offer DocSearch as a free option for community to search within documentation. If you agree I'd like to set it up here.

Enjoy your day ❇️

Hello,

I am getting error as site cant be reached on accessing the portal. http://54.255.140.142:3000/

Kindly suggest.

Chrome browser

The room link in this section is a dead link. Should most likely be changed from: http://new.socket.io/docs/rooms-and-namespaces/ -> http://socket.io/docs/rooms-and-namespaces/

GET http://slack.socket.io/socket.io/?EIO=3&transport=polling&t=LVesgWJ
XMLHttpRequest cannot load http://slack.socket.io/socket.io/?EIO=3&transport=polling&t=LVer5WW. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://socket.io' is therefore not allowed access. The response had HTTP status code 502.

GET http://chat.socket.io/socket.io/socket.io.js net::ERR_INCOMPLETE_CHUNKED_ENCODING

Uncaught ReferenceError: io is not defined(…)

The polling error pair repeats and later on there's also
GET http://platform.twitter.com/widgets.js net::ERR_NAME_RESOLUTION_FAILED

Because this is in a code block, it's spitting out ', for example, instead of &' (assuming that was the intent).

Showing up in Chrome Version 40.0.2214.111 (64-bit), currently up-to-date.

I want to:

• Report a bug

Current behaviour

While browsing the socket.io website, the Slack button in Header shows number 42 first(which is the no. of users who are currently online on slack), then in 2-3 seconds, it shows the actual no. of users who are online on slack. This problem persists on every refreshing or loading of the webpage as Header is viewable all the time, so this looks very odd to see 42 first and then the actual no. of users.

I've tried to run the website on other browsers (chrome, microsoft edge and in android phones also) but the problem is same. I am attaching the pic also.

Steps to reproduce (if the current behaviour is a bug)

I tried to debug the code then I found out that 42 is actually a constant to the slack button, which always popup first then the correct no. of users come up.
I found it here:
home.js

But, I didn't understand, why you did this? Due to UX or is it a bug?
Should I submit a PR after refactoring it?

Expected behaviour

On loading or refreshing the page, the slack button should only show the number of users who are currently online instead of 42 at first.
It should be like this:

Setup

• socket.io website

Link not found when directing away from https://socket.io/get-started/chat/ , under the 'Emitting Events' subsection, to the url:
https://socket.io/blog/introducing-socket-io-1-0/#binary

Receiving 503 "The deployment is currently unavailable."

In the docs, the section about using socket.io with Express 2.x is called "Using with the Express Framework"

This leads to confusion, and should be renamed "Using with Express 2.x".

Hi I came to verify how to connect to socket.io while writing a stackoverflow answer

When I last used the project, there were obvious examples showing the minimal code required on server and browser.

I now only see the server example. Even after navigating to Get Started, Demos and Docs I do not see a usage example for how to source and instantiate the io object.

On these pages :
http://socket.io/docs/logging-and-debugging/
http://socket.io/docs/faq/

The left sidebar is hidden. It's not hidden for the others links.
We lose the navigation.

Error establishing a database connection: Looks like http://socket.io is currently offline.

Hello,

After spend a lot of time trying to make a cluster with socket.io + socket.io-redis I would like to share my experience with the community and my suggestion is to add a new section in the site called "Unofficial examples" to share this kind of projects. To make this cluster work was a difficult experience for me and I found a lot of people with the same problems.

In this section the authors of open source projects could share some links with solutions explaining more about socket.io and details about that.

What do you think ?

There is a typo in http://socket.io/get-started/chat/:

Let’s refactor our route handler to use sendfile instead:

app.get('/', function(req, res){
  res.sendFile('index.html');
});

sendfile should be written without a capital: sendFile gives an error (very confusing for a beginner) :)

The official website seems to be down for a long time..
ERR_CONNECTION_TIMED_OUT

npm should never be capitalized.
It is captilized here and twice on the "download" page which doesn't seem to be in the repository.

HTTP 502 error is received.

Hello,

Thanks for this Repo!

Is it possible to start multiple chat rooms and how?

The element's text overflows at certain viewports on line 8 of sample code.