Comments (3)
@therobbot, this should be a common problem with Snapdrop with a lots and a lots of issues on the original repo.
To resolve, just try to connect after a while. This also occurs to me sometimes. For now, I can't do anything, because no one, also me, understood what's wrong.
If there is some issue resolve on the original repo, I'll update this Node version.
from node-snapdrop.
@therobbot , I think I've hobbled together a patched version that fixes your issue.
Snapdrop is written from the assumption that the clients that are seeking to connect to each other are physically on the same LAN, BUT that lan is connected to the public internet where the snapdrop server is located. It is further assumed that the LAN is connected to the internet using NAT. Basically this means that, to the snapdrop server, it appears that all clients are originating from the same IP address.
In our case, however, the server will see unique IP addresses for each client seeking to connect to each other.
My fix is derived from this patch. This patch talks about needing a STUN server. My fix does not require any extra STUN server.
https://github.com/DrBassman/node-snapdrop/
Update: opened pull request, too.
from node-snapdrop.
@therobbot , I think I've hobbled together a patched version that fixes your issue.
Snapdrop is written from the assumption that the clients that are seeking to connect to each other are physically on the same LAN, BUT that lan is connected to the public internet where the snapdrop server is located. It is further assumed that the LAN is connected to the internet using NAT. Basically this means that, to the snapdrop server, it appears that all clients are originating from the same IP address.
In our case, however, the server will see unique IP addresses for each client seeking to connect to each other.
My fix is derived from this patch. This patch talks about needing a STUN server. My fix does not require any extra STUN server.
https://github.com/DrBassman/node-snapdrop/
Update: opened pull request, too.
By using node index.js LAN
,it works now.
Thank you!
from node-snapdrop.
Related Issues (8)
- Heroku Free Plan Shutdown (hosting provider change) HOT 3
- "Connection lost"
- [Bug] "DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable" HOT 2
- Sending Messages Broken HOT 2
- .exe and .dmg server HOT 3
- ERR_TOO_MANY_REDIRECTS HOT 4
- Fix code scanning alert - Missing rate limiting
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-snapdrop.