socket.io-p2p | WebRTC data channel communication with the socket.io API | Socket library

You problem is that you are trying to contact an nodejs server on an apache server.

This does look like this:

The problem is that Apache doesn't know how to handle the incoming Socket.io request. The simplest option now is to expand the server and let socket.io connect to another port:

So everything is the same as before.

In this example setup, you have Apache installed on a dev server (like the one you mentioned). You have access to the servers shell.

1. Transfer your files holding the express and socket.io files to the server (besides the web root directory, not in /var/www. I would recommend to put it in /home/myUserName/[productname]).

2. Make sure that nodeJS and NPM is installed on the server

3. If you didn't transfer node_modules, execute npm install to install the packages.

4. Set the port to something other than 80 - probably 3000. Remember this number.

5. Start the server as you do on your client (node index.js or something similar)

6. If you access your server now via port 3000 (http://myServerDomainOrIp:3000) you should get the same results as on the client. But you want (or have) to use the apache web server. So open in the apache web files the file which starts the socket.io client. There should be a line around this: var socket = io();. Change this to socket.connect('http://myServerDomainOrIp:3000');

So static files are serverd over apache, but the socket.io connection is established with the nodejs server.

I hope you understand a bit right know. Apache and Socket.IO is a bit complicated.