Can't connect to whatsapp

[codingr]

"xxxxxxxxxx disconnected Server closed the connection"

This message appears when I start pidgin. It worked perfectly 24 hours ago. I have tried setting server as c.whatsapp.net, c2.whatsapp.net, c3.whatsapp.net, changing port to 443 and 5222, resource Android-2.11.151-443 to Android-2.31.151-443... with no luck.

I've read some spanish guys who are suffering the same problem.My OS is Windows 7 with SP1, just in case.

[TerrificTT]

Firstly kudos for such a great software which has helped me a lot. But as of late i'm stuck with this message "Server closed the connection". Tried all the tweaks but no progress. Even changing the password was of no use.

[githubtefo]

Thanks david for yor answer! But for some reason she cannot use her argentinian number in Brasil with roaming. Useless mobile companies... Now she buy a Firefox OS smartphone with a brasilian number and use ConectA2. So I'd like to ask you if it is possible to open the account with 2 different devices and applications, or whatsapp network will kick her account? Thanks guys!

[axel21a]

@TerrificTT look here #178

[davidgfnet]

Only one device connected at a time. Whatsapp rules.

[TerrificTT]

Debugging pidgin gave this and there seems to be nothing supernatural out here...then what may be the cause...(I have changed the password 20th time still it gives this response)..it was working fine till a week ago but now it shows "Server closed the connection"... (14:03:05) account: Connecting to account XXXXXXXXXXXX. (14:03:05) connection: Connecting. gc = XXXXXXXXXXXX (14:03:05) whatsapp: logging in XXXXXXXXXXXX (14:03:05) dnsquery: Performing DNS lookup for c3.whatsapp.net (14:03:05) autorecon: done calling purple_account_connect (14:03:05) dns: DNS child 11358 no longer exists (14:03:05) dns: Created new DNS child 11366, there are now 1 children. (14:03:05) dns: Successfully sent DNS request to child 11366 (14:03:05) dns: Got response for 'c3.whatsapp.net' (14:03:05) dnsquery: IP resolved for c3.whatsapp.net (14:03:05) proxy: Attempting connection to 50.22.225.69 (14:03:05) proxy: Connecting to c3.whatsapp.net:5222 with no proxy (14:03:05) proxy: Connection in progress (14:03:05) proxy: Connecting to c3.whatsapp.net:5222. (14:03:05) proxy: Connected to c3.whatsapp.net:5222. (14:03:09) connection: Connection error on XXXXXXXXXXXX (reason: 0 description: Server closed the connection) (14:03:09) account: Disconnecting account XXXXXXXXXXXX (XXXXXXXXXXXX) (14:03:09) connection: Disconnecting connection XXXXXXXXXXXX (14:03:09) connection: Destroying connection XXXXXXXXXXXX (14:03:14) util: Writing file accounts.xml to directory /home/t/.purple (14:03:14) util: Writing file /home/t/.purple/accounts.xml dns[11366]: nobody needs me... =(

[joshuakraemer]

I have the same problem. I have sent a new request with yowsup, but get "status: fail, reason: blocked".

[davidgfnet]

In that case the only option left is begging the whatsapp team. It worked for me with two numbers. Also another one got unblocked after some time (I think it might be weeks).

[CleberMetal]

Hi, I have the same problem than joshuakraemer. When I sent new request using WART-1.7.3.0, I got the answer: "status: fail, reason: blocked". The news: I tried too from a new mobile number that I never had used before, and I got "SMS Sent". Is it possible the WhatsApp server's blocked my mobile numbers? Do you have some tip? Tks

[dequis]

Yes, it means exactly that, your number is blocked. And like david said, "the only option left is begging the whatsapp team". Go send them an email to the support address.

[joshuakraemer]

Let me add this. I registered my number for the first time with yowsup, then used it for some regular chatting with a few friends for one week, then my account was blocked. The reason for blocking may be that I registered the number with yowsup and not the official client. I think it is advisable to add a hint in the readme that this might happen.

[dequis]

No, registering through yowsup should be perfectly okay. Pretty much everyone registered their numbers with third party apps, yowsup is no different from the rest.

[rutja76]

I got my number blocked as well. Cannot login even after installing the official app on my mobile: "Your number is no longer allowed to use our service" (http://www.whatsapp.com/faq/en/general/23154266). I guess they are kicking out people who use whatsapp through third-party applications. As written in the above linked FAQs, "Using an automated system or an unauthorized / unofficial client application to send messages through WhatsApp" is in violation of their terms of service.

[davidgfnet]

I agree with dx, all activators are the same those days (exact same implementation on most of them). Maybe I'm really lucky :D

[Jeronimo17]

I also have been banned 2 days ago, I'm using the user-agent S40-2.12.67 I check from time to time here http://www.whatsapp.com/s40/OptWhatsApp.jad.

I do not upgrade in time on this occasion, it may be that the cause of the ban or that I have sent pictures and always the same thumbnail is sent...

Should be checked version of the user-agent to connect

[davidgfnet]

Oh now that you mention! The thumbnail! It is a very easy way to detect this particular plugin. I think I'll fix this ASAP. Profile picture is another thing we should get fixed too. Thanks for the heads up

[Cybernetic1]

Does it mean that if my number is blocked by Whatsapp, there's no way to revive it? I e-mailed them and they simply pointed to this answer :(

[annonbacca]

Just got another number blocked. Feeling miserable cause I can't try reactivating the number via SMS, lost the SIM card. Anyways this happened to me on a number registered using the latest WART and has only been used on pidgin.

I think, the blocking mechanism takes place during logging on stage (Connection to server) so if a number has been running for weeks on end, non-stop with continuous internet connection, you are less likely to be banned whereas those that happen to run it on a choppy bad internet connection with lots of disconnects would face eventual block. Like the checking mechanism for fake client, I suspect runs on a random basis, so its possible to connect and disconnect a couple of times to the hour but eventually a trace would happen and the number could get blocked.

I am not sure as for the latest whatsapp, but I was running mine using one of the old dlls which doesn't have any of the read receipt capability. So far, my other accounts which were registered using the official client are still running, and I do switch them on pidgin from time to time, and so far no problem.

And yes, the ones made using the official client have profile picture and status messages adjusted so they don't just appear as blank profile with an equally blank status or the default, "Hey, I am on whatsapp" message.

The other final thing I would like to add is that the WART client uses an unknown fixed google account (or probably none at all) while the whatsapp official for android has a tie in with a unique google account (which is used mainly for push notification), its how they know if the same user has resurrected a deleted account on the same number, in addition to the user identifiable information such as phone contacts and IMEI + MAC. I suppose the iOS based Apple phones has a tie in with iCloud. So, I suppose it won't be hard for them to eventually spot all those that do not have a distinct google/iCloud account, or all those that are registered to a single account.

Finally, I would like to take this opportunity to thank DavidGF for creating a fantastic software that allows me to use Whatsapp on PC. Thank you man, most appreciate it.

[davidgfnet]

I'm kinda lazy those days but in the past I used to implement everything by capturing real Wa traffic from my phone. So... Pcap traces are more than welcome!

[davidgfnet]

Oh btw. Which is the best method to extract wa password from an android phone? I may give that i try.

[dequis]

https://github.com/mgp25/WhatsAPI-Official/wiki/Extracting-password-from-device

[davidgfnet]

Yeah. No way I'm running an apk without compiling it myself, specially when it requires root access.. Not that crazy. Thanks anyway. I might decompile it and give it a look

[Red-Hell]

Same problem here. Account banned yesterday morning. I've also tried installing whatsapp under android emulator and says that my number is banned.

I hope they will unban my account...

[dequis]

@davidgfnet the 'bash' section in the same page provides a do-it-yourself method

BTW the situation in this ticket is looking pretty bad. Maybe creating a 'whatsapp web' client isn't a bad idea after all... I wrote some notes about it, only good enough as an introduction/overview, but there's plenty of stuff left to reverse to achieve a working third party client for that. It's also completely different from this plugin... And I mentioned it there, but there's a restriction to only one web client at the same time (the others get in a pause-like mode, and gotta implement a way to takeover the mutex)

[davidgfnet]

Yeah thanks, I managed to get my pwd but it's very tricky to eavesdrop it since the client usually reconnects using the simplified handshake mechanism instead of doing a full handshake. I haven't still figured out whether we can decrypt that. What you say sounds interesting but IMO this defies the whole purpose of all of this which is getting rid of the official client. The main consumers of this plugin seem to be people not having an smartphone at all.

[Red-Hell]

In fact, David, I haven't a smartphone ad I don't want it (I don't want to pay for another internet connection ad I can't use something touch, I prefer keys).

But David, you have to be proud of your plugin, also if it lacks of something, if the only way that the WA team has to block other program is blocking the account.

In another system you will have only to register again, but change the phone number is not really easy...

EDIT: no way, my number is still blocked, I've checked with official client on an android emulator

[Red-Hell]

"Hi,

Your WhatsApp account has been banned because your activity on WhatsApp is in violation of our Terms of Service.

We cannot comment on the individual reasons that have led to your account ban. However, the following actions provide examples of activity that will result in an account becoming banned:

bla bla as written in faq

Please review our Terms of Service to learn more about the appropriate uses of WhatsApp.

We currently do not have a repeal process in place for unbanning your account."

Now I really doesn't need a smartphone...

Sorry David, but you will have to write this on the homepage of this projet, to use this plugin at risk of ban...

[davidgfnet]

Well... People usually accept the ToS without reading them. I agree I could explicitly warn people but come on, they are grown up, it's time to assume responsibilities.

[Jeronimo17]

You're doing a good job, you're helping people to change to Telegram :P

[assegaf]

@davidgfnet did you managed to able to see live debug log IN/OUT of whatsapp official client ? how to do this in simple way ? maybe something mismatch different mechanism between official and this api. thanks

[davidgfnet]

Extract your pass. Make sure WA connects using a full handsake (see my net-tools repo). Use wireshark with the freshly extracted password. Make sure to kill the app (just reboot the phone to make sure) and start using watsapp on your phone.

[assegaf]

ah yes, sorry, reboot the phone to get Full handshake, I will try now .. Update : after force close WA, remove cache, reboot, still sending The auth BLOB handshake Challenges key. I wonder where android client get this blob handshake key..

maybe from cloud.. not sure I will try from Beginning simcard register

2.11.476 android

Sorry should be posted on other project

[namoplasta]

@davidgfnet When installed whatsapp-purple from the source code, is still maintained Android-2.11.151-443, and only works on Android-2.31.151-443, I think this must be updated in git. Only worked with me at the port 5222, think it should be a warning in the plugin to set this port if the 433 does not work.

[marga-personal]

I got one account blocked back by the end of February, I wrote to request an unblock and they replied saying that I was using an unauthorized program and that they wouldn't unblock.

I'm now having a somewhat similar but different problem with a different number. It frequently disconnects with the "Server closed connection" message, but then it reconnects fine. It just doesn't stay connected long, sometimes it's seconds, sometimes it's minutes. Sometimes after reconnecting I get the backlog, sometimes I don't. :-/

I've tried changing servers and resource, but that doesn't seem to make any difference.

Any tips on how to get a more stable connection?

[davidgfnet]

See #263

[gabriel-tandil]

My contribution: After Whatsapp lock my account, and after pray to whatsapp support to unlock my numbers, with negative response on several occasions. Wait several weeks, I went back to try and my numbers works again. Anyway... Telegram rule Fuck that whatsapp

[namoplasta]

Fuck WhatsAPP, Telegram rules.

[dektiram]

i use pidgin whatsapp for 2 moths, everything work well. But since 2015-07-21 my account was "not-authorized". I've try to change password using WART and I get new password. But it's not give solution, my account still not-authorized. I try to use new number and register it via WART, but the same problem is happend. Is that any change in whatsapp rule ?

[ikbalenjino]

now pidgin is end. good bye

[ViBE-HU]

i'm tried to setup wa plugin but i guess i did something wrong or just impossible to make it work. i have a Nokia N9 with Whatsup. my number is already registered and it cannot connect with my phone if i authorise my number with the wa plugin and reverse. how can i setup both client to not de-authorise each other when i connect?

[rodpmaia]

Worked for me using this: c3.whatsapp.net 5222 Android-2.31.151-443

rutja76 commented on 24 Feb

Yes, timed out, it started yesterday evening. Now, I have to admit that I don't know whether changing password with WART has nothing to do with that. But I've tried c1, c2 and c3 servers and I was timed out an all of them on port 443, which I've been using all the time without any problems until yesterday evening. After changing password with WART I was still timed out, so I tried changing port to 5222 as it was mentioned in the first post of this thread. Only at that point I was able to login on c3 server (haven't tried the other ones) using Android-2.31.151-443 as resource.

PS: for timed out I mean "Connection timed out." I put an extract of the log here above.