search

sigalor / whatsapp-web-reveng

Reverse engineering WhatsApp Web.
MIT License
6.1k stars 802 forks source link

New socket address, still doesn't work after updating it #205

Open tulssinep opened 5 years ago

tulssinep commented 5 years ago

The new socket comes without the "w1" in the URL. It's only wss://web.whatsapp.com/ws now.

However, after scanning the code, nothing happens. Relaunching everything and then opening the index.html gets to

click to connect to API connected to API. Click to connect to backend [got message api-connectBackend, meta, connected] connected API to backend. Click to let backend connect to to WhatsApp Connecting to WhatsApp [Errno 8] nodename nor servnae provided, or not known [sending resource_gone] Connection of backend to WhatsApp failed. Timeout. Click to try again

tulssinep commented 5 years ago

This is the output I'm getting when it fails/ I'm clicking to try again

got message  { command: 'backend-connectWhatsApp', from: 'client', type: 'call' }
123456789,{"command":"backend-connectWhatsApp","from":"api2backend","type":"call"}
{u'from': u'api2backend', u'command': u'backend-connectWhatsApp', u'type': u'call'}
[Errno 8] nodename nor servname provided, or not known
sending {"type": "resource_gone", "resource": "whatsapp", "resource_instance_id": "abc123456789", "from": "backend"}
WhatsApp backend Websocket closed.
got message  {
  type: 'resource_gone',
  resource: 'whatsapp',
  resource_instance_id: abc123456789,
  from: 'backend'
}