Can't connect to whatsapp #224
Comments
|
I've got the same problem, but i just tried with c3.whatsapp.net and c2.whatsapp.net, with port 443 and Android-2.31.151-443. I'm using debian Jessie. |
|
the same :( |
|
Happen with me too. But I think its probably an auto blocking mechanism they are using. |
|
Same here. Tried the different servers and ports with no luck. (OS is not related to this issue as far as I understand, but I'm on Debian GNU/Linux) |
|
it works for me... Tried an hour ago and I could see all the offline
messages people sent me.
|
|
@davidgfnet: in the first place, a HUGE thanks for this great piece of software! :) Can you please post the exact settings you are using? (server, port, android version...) |
|
I'll do as soon as I get home. But I don't think it matters at all... I've
been changing them and using my phone to debug and implement new features
and it always works...
Maybe (just maybe) they know when and how people activated they numbers and
block using that as discriminant. My number is really old, I activated it
using a very old version of yowsup (maybe 1 year or more).
|
|
@davidgfnet : My number is also very old and I registered via yowsup too, a year ago. So we are in the same situation. |
|
Not a US number for sure
|
|
Mine's a normal spanish number. 34 610 XXX XXX, not an US number. |
|
I cannot connect either. I have a dutch number. I registered three years ago via yowsup and reregistered 1 1/2 years ago. The server closes the connection. This started this weekend. |
|
most likely they are locking us out. Had the problem ever since I intentionally restarted it while switching ip address. Most likely its a block, my only hope its a temporary thing cause I have heard users of an alternate client "whatsapp plus" were getting blocked like randomly. So its probable they are handing out blocks based on our strange whatsapp app version numbers. Additionally at the time, I was using c2.whatsapp.net while the other numbers were using c3.whatsapp.net I registered using a rather old version of WART, and in the time I registered this number of mine that got blocked, I registered for one other number, and that number has typically been dormant, so when this number got blocked, I wasn't using the other number, and I am still able to use that number along with other numbers which I have created over time, which were made with varying versions of WART but similar whatsapp android version. I think the real issue is the blocking. |
|
Yep,
Let me add some verbose output (so we can know the reason why loging in
fails) and what is happening.
|
|
Here's an extract from my pidgin log (I've X:ed some information): (16:42:35) account: Connecting to account XXXXXXXX. |
|
i've got this from the log Tag: start Tag: stream:features Tag: challenge Tag: response Tag: failure |
|
So... It seems WA is blocking users. I recall there was some sort of
"blocked" comment on some errors (i think it was cause:blocked).
Have you guys tried to ask for a new password using WART or any tools alike?
If WART complains it is because your number is probably blocked.
|
|
I got the same log as nicoceledon, then I asked for a new password by WART and now it's working! |
|
Told yaaaaa!
Anyway, nice to hear it works for you guys.
|
|
Hmmm.... so asking for a new password fixes it? |
|
That was all! Request the password and running. @vanfanel As for the password request without a phone, i don't think you can't because they send you the code to the phone. |
|
I'm using WP7-2.31.151-443 as resource connecting to c1.whatsapp.net Thanks guys! |
|
Changing the password does not seem to work for me: I get connection timed out (as reported above) on c1, c2 and c3.whatsapp.net UPDATE: just got in using c3.whatsapp.net and port 5222 |
|
New password with WART worked for me! |
|
By timed out what you mean? You are able to use it but at some point it disconnects or you never get the chance to use it at all? |
|
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. |
|
Maybe whatsapp servers were down... just saying. I mean, behind any hostname (ie. c3) there are a bunch of servers (different IPs) so bad luck can make you ending up in a broken server. I guess the official app has a round robin mechanism so everytime there is a timeout it retries a different IP. (seems that pidgin does not do that). |
|
Actually port 443 (on c1, c2 and c3) doesn't work for me anymore since yesterday evening, and I have been using it for a year. Just retried: timed out. Only port 5222 seems to work. |
|
i've tried openwapp (in firefox os emul), and it worked |
|
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 :( |
|
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. |
|
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! |
|
Oh btw. Which is the best method to extract wa password from an android phone? I may give that i try. |
|
Yeah. No way I'm running an apk without compiling it myself, specially when it requires root access.. Not that crazy. |
|
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... |
|
@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) |
|
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. |
|
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 |
|
"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... |
|
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. |
|
You're doing a good job, you're helping people to change to Telegram :P |
|
@davidgfnet did you managed to able to see live debug log IN/OUT of whatsapp official client ? |
|
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. |
|
ah yes, sorry, reboot the phone to get Full handshake, I will try now .. maybe from cloud.. not sure 2.11.476 android Sorry should be posted on other project |
|
@davidgfnet |
|
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? |
|
See #263 |
|
My contribution: |
|
Fuck WhatsAPP, Telegram rules. |
|
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 ? |
|
now pidgin is end. good bye |
|
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? |
|
Worked for me using this: 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. |
and others
"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.
The text was updated successfully, but these errors were encountered: