question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Conflict when webpage also uses Socket.io

See original GitHub issue

Browser-sync v0.5.7 works perfectly if I proxy the PHP server. But when using with my nodejs server from the command line (browser-sync --proxy "localhost:5000" --files "public/asset/css/*.css", where my NodeJS site runs under localhost:5000), the webpage looks as following:

browser-sync-nodejs

Issue Analytics

  • State:closed
  • Created 10 years ago
  • Comments:14 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
simshanithcommented, Sep 10, 2014

Submitted some pull requests from my personal account.

1reaction
shakyShanecommented, Feb 14, 2014

BrowserSync has not yet been tested to work with web-sockets.

If you disable options.ghostMode.links then it will work for you until this gets fixed

ghostMode: {
    links: false
}
Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting connection issues | Socket.IO
You are trying to reach a plain WebSocket server; The server is not reachable; The client is not compatible with the version of...
Read more >
How to fix browser-sync & socket.io conflict? - Stack Overflow
I mainly use Gulp with browser-sync inside an Aurelia CLI project, while the backend is NodeJS with Koa . The version of socket.io@1.6.0...
Read more >
Web Sockets - A brief explanation | by Jacob Friesen | Medium
There is a lot of details like conflict resolution, efficiency (in ... We use Socket.io which also has server side extensions though that...
Read more >
Avoiding WebSockets conflicts - Node.js Web Development
Avoiding WebSockets conflicts An error, Cannot find context with specified id undefined, can be thrown by Puppeteer. According to an issue in the...
Read more >
409 Conflict - HTTP - MDN Web Docs
The HTTP 409 Conflict response status code indicates a request conflict with the current state of the target resource.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found