search

ash47 / OmegleMiddleMan

Lets you connect strangers to each other, and intercept messages AKA Man in the Middle Attack
233 stars 60 forks source link

Getting a "socket hang up" error when trying to start #32

Closed Mcmarc00 closed 6 years ago

ash47 commented 6 years ago

Is this in the chat log? Sounds like it's having issues talking to the omegle servers.

is the main website working for you? if so, restart omegle middle man and try it again?

Mcmarc00 commented 6 years ago

Its in the CMD window and the chatlog, Omegle site is working fine for me and have tried several restarts.

ash47 commented 6 years ago

Is there a full stack trace?

ash47 commented 6 years ago

Or, just a screenshot of the console?

Mcmarc00 commented 6 years ago

Not very helpful https://imgur.com/cGE5YyU

ash47 commented 6 years ago

That's pretty helpful -- it's not even finding ANY servers :O

ash47 commented 6 years ago

Can you run "node --version" in your console and tell me what version it says you have?

Mcmarc00 commented 6 years ago

v7.2.1 All was fine yesterday and I'm not sure whats changed.

ash47 commented 6 years ago

Would you please visit the following page and tell me what it says?

http://omegle.com/status?nocache=lol

Just paste the contents here?

Mcmarc00 commented 6 years ago

{"count": 12573, "antinudeservers": ["waw3.omegle.com", "waw2.omegle.com", "waw1.omegle.com"], "spyQueueTime": 1.792900013923645, "rtmfp": "rtmfp://p2p.rtmfp.net", "antinudepercent": 1.0, "spyeeQueueTime": 0.3693000078201294, "timestamp": 1528850062.623993, "servers": ["front22", "front15", "front8", "front12", "front7", "front20", "front18", "front16", "front17", "front32", "front13", "front28", "front19", "front3", "front31", "front29", "front6", "front21", "front24", "front26", "front1", "front30", "front23", "front10", "front11", "front14", "front27", "front5", "front9", "front2", "front25", "front4"]}

ash47 commented 6 years ago

I just made a commit to make the server selection code more robust -- do you want to pull down a new copy, and see if it's fixed? / Tell me what the console says if it doesnt work?

Mcmarc00 commented 6 years ago

Exactly the same as before

ash47 commented 6 years ago

Can you try and update your NodeJS: https://nodejs.org/en/download/current/

Make sure you run node --version to ensure it was actually updated -- let's just cross off the obvious issues if we can...

Mcmarc00 commented 6 years ago

Node updated fine to v10.4.1 but the issue is still there

ash47 commented 6 years ago

Ok, I've upgraded it to use TLS -- hopefully that will provide a much more stable connection, let me know if that helped?

Mcmarc00 commented 6 years ago

Yup that got it working again, thanks very much.

ash47 commented 6 years ago

Sweet, got a few little improvements there, thanks for the feedback :)