Using with socket.io and express

[brunobg]

I'm having an issue:

• Give an expressive description of what is went wrong
  Starting an ExpressPeerServer in a server that runs express and socket.io breaks socket.io. Apparently both use the same port and this wrecks havoc, but this used to work with previous versions.

• Version of peer you're experiencing this issue
  0.5.3

• Nodejs version?
  v10

• Platform name and its version (Win, Mac, Linux)?
  Linux. Also, socket.io 2.3.0.

• Nice to have: a repository with code to reproduce the issue
  Sorry, don't have

• If you're getting an error or exception, please provide its full stack-trace as plain-text or screenshot
  There's no error. socket.io starts, but app.use('/peerjs', peerserverSSL); breaks socket.io connections.

This used to work with "peerjs-server": "^0.2.9", but broke after updating to current.

Is this a bug or is peerjs now incompatible with socket.io? If incompatible, any suggestions for a workaround? Create a new peerjs server without using express perhaps? Thanks

[brunobg]

so if anyone runs into this: no, you cannot run with express and socket.io at the same time. peerjs now seems to use the same websocket attachment to express than socketio. run a separate peerserver.

[aniket-banyal]

Hi. I am facing the same issue. Please can u explain a but more about how to run a separate peerserver. Thanks!

[brunobg]

@Dummy26 Create it directly like https://github.com/peers/peerjs-server#create-a-custom-server

[muratkemaldar]

I am having issues because of this combo as well. I am running my Express App on Heroku and I only have a single port which I can use. This is why I would like to use the ExpressPeerServer and not a separate one.

Where do you deploy your app when you have a port for your Express Server and one for the Peer Server? @brunobg

EDIT:
I now decided to to run a separate Heroku App with a PeerServer.

[lmf-git]

Same problem too, I'm not willing to use two different websockets just due to the laziness of the developers of this project.

[brunobg]

This issue should be locked. I'm the OP of this issue. This is not a bug and I understand very well why it was implemented like this.

If someone reaches this from Google, final guideline:

• peerjs and socketio use websockets attach to express the same way. It's not viable to change that.
• you can easily create a PeerServer with its own websocket, with no other drawbacks. It's well documented here: https://github.com/peers/peerjs-server#create-a-custom-server It's literally two extra lines.
• I posted a PR which was accepted and allow you to create a websocket with all the https options supported by nodejs. It didn't at the time I created this issue, which was a limitation to what I needed to do.

I won't post anymore on this issue.

[peerjs-bot]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.