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.

[nicoceledon]

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.

[KottV]

the same :(

[annonbacca]

Happen with me too. But I think its probably an auto blocking mechanism they are using.

[vanfanel]

Same here. Tried the different servers and ports with no luck. Are they locking us out? I am also in Spain.

(OS is not related to this issue as far as I understand, but I'm on Debian GNU/Linux)

[davidgfnet]

it works for me... Tried an hour ago and I could see all the offline messages people sent me.

[vanfanel]

@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...) Maybe they are locking users progressively? Using the latest github code here with no luck since yesterday.

[davidgfnet]

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).

[vanfanel]

@davidgfnet : My number is also very old and I registered via yowsup too, a year ago. So we are in the same situation.

[davidgfnet]

Not a US number for sure

[vanfanel]

Mine's a normal spanish number. 34 610 XXX XXX, not an US number.

[gynt]

I cannot connect either. I am using pidgin: 2.10.9. c2.whatsapp.net 443 Android-2.31.151-443

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. I am using whatsapp dll version from 6 september 2014 (Version 0.1).

[annonbacca]

@vanfanel

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.

[davidgfnet]

Yep, Let me add some verbose output (so we can know the reason why loging in fails) and what is happening.

[rutja76]

Here's an extract from my pidgin log (I've X:ed some information):

(16:42:35) account: Connecting to account XXXXXXXX. (16:42:35) connection: Connecting. gc = XXXXXXX (16:42:35) GdkPixbuf: gdk_pixbuf_composite: assertion GDK_IS_PIXBUF (dest)' failed (16:42:35) GLib-GObject: g_object_unref: assertionG_IS_OBJECT (object)' failed (16:42:35) waprpl: logging in XXXXXXXXXXXXX (16:42:35) dnsquery: Performing DNS lookup for c2.whatsapp.net (16:42:35) dnsquery: IP resolved for c2.whatsapp.net (16:42:35) proxy: Attempting connection to 184.173.147.53 (16:42:35) proxy: Connecting to c2.whatsapp.net:433 with no proxy (16:42:35) proxy: Connection in progress (16:42:40) util: Writing file prefs.xml to directory C:\Program Files (x86)\PidginPortable.purple (16:42:40) util: Writing file C:\Program Files (x86)\PidginPortable.purple\prefs.xml (16:42:40) util: Writing file accounts.xml to directory C:\Program Files (x86)\PidginPortable.purple (16:42:40) util: Writing file C:\Program Files (x86)\PidginPortable.purple\accounts.xml (16:42:41) util: Writing file blist.xml to directory C:\Program Files (x86)\PidginPortable.purple (16:42:41) util: Writing file C:\Program Files (x86)\PidginPortable.purple\blist.xml (16:42:41) accels: saving accels to C:\Program Files (x86)\PidginPortable.purple\accels (16:42:56) proxy: Connecting to c2.whatsapp.net:433. (16:42:56) proxy: Error connecting to c2.whatsapp.net:433 (Connection timed out.). (16:42:56) proxy: Connection attempt failed: Connection timed out. (16:42:56) connection: Connection error on XXXXXXX (reason: 0 description: Unable to connect: Connection timed out.) (16:42:56) GdkPixbuf: gdk_pixbuf_composite: assertion GDK_IS_PIXBUF (dest)' failed (16:42:56) GLib-GObject: g_object_unref: assertionG_IS_OBJECT (object)' failed (16:42:56) account: Disconnecting account XXXXXXXXXXXXXX (XXXXXXXXX) (16:42:56) connection: Disconnecting connection XXXXXXXX

[nicoceledon]

i've got this from the log

Tag: start at[from]=s.whatsapp.net Data: ...

Tag: stream:features Data: ...

Tag: challenge Data: ËÊù•66¼qJ ...

Tag: response Data: M(ÀÙCˆhq ...

Tag: failure Data: ... Tag: not-authorized Data: ...

[davidgfnet]

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.

[cassiodoroVicinetti]

I got the same log as nicoceledon, then I asked for a new password by WART and now it's working!

[davidgfnet]

Told yaaaaa! Anyway, nice to hear it works for you guys.

[vanfanel]

Hmmm.... so asking for a new password fixes it? Is there a way to receive the new password without a phone? I haven't the number I use with this lib anymore.

[nicoceledon]

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.

[davidgfnet]

I'm using WP7-2.31.151-443 as resource connecting to c1.whatsapp.net But I think the problem is the password, so... I think i will close this. So far recommentations are: as usuarl try a fresh install/config, try my resource, try different hostnames and if that does not work, ask for a new password.

Thanks guys!

[rutja76]

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

[gynt]

New password with WART worked for me!

[davidgfnet]

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?

[rutja76]

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.

[davidgfnet]

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). On top of that they are kicking people using non-official clients such as WA+, that could be another reason... I don't know why people is so dumb not to migrate to Telegram.

[rutja76]

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.

[KottV]

i've tried openwapp (in firefox os emul), and it worked then, re-registered with yowsup, and whatsapp-purple connected flawlessly...

[mlopezgva]

I have same prolem here since 04:00 GMT (approx.), but can't run yowsup in this machine, I'll have to wait 'to return home. :(

[davidgfnet]

Use WART instead (it's a Windows Application), you only need .NET I think

[dequis]

@davidgfnet you might want to keep this one open so people don't open new ones

(they will do anyway, but hopefully less)

[mlopezgva]

Last WART version requests a PIN via SMS, and I have currently no access to this line. I've tried with an older version, but it throws and error. :/

[davidgfnet]

Ehm Manuel, you'll need the phone number. You just cannot get a new password without that SMS. I mean, it is impossible otherwise.

[mlopezgva]

hmpf... I'll have to borrow a terminal, since mine is broken... Before that I've never needed the phone, just my number. :(

thanks for the response, nonetheless. I'll try later to get my registration using yowsup.

[davidgfnet]

I seriously doubt that assertion. You always need a phone to verify that you own that number, otherwise I could use your phone.

[codingr]

Changing the password worked for me. Thanks.

[salvattore001]

i have just installed the plugin for the first time. got a password from WART. tried different hostnames. always get the error "server closed the connection". what else could i try?

[davidgfnet]

Make sure the phone number is the "correct" one. Many people get it wrong.

[salvattore001]

i got an SMS from WART. so it is supposed to be the correct number? in case.. how i know which is the correct number?

[davidgfnet]

I mean make sure to write the number in the right format. International prefixes may be written as +XX or 00XX for instance.

[salvattore001]

tried 54 and +54 still no luck :( the number is from argentina

[seenutn]

I tried to register again with yowsup-cli I had earlier and yowsup-cli itself failed (The issue I encountered was same as https://github.com/tgalal/yowsup/issues/353). I downloaded the fresh yowsup-cli from github, requested the password and with that password the pidgin is working properly with whatsapp. Thanks to tglal and davidgfnet.

[dequis]

tried 54 and +54 still no luck :( the number is from argentina

Also try 549 (as in 54911... instead of 5411...) . I have no idea why it needs a 9 sometimes, but it does.

[davidgfnet]

Luckily for you there are some Argentinean users :D I just committed a change which should help debugging. It should clearly state "not-authorized" in case the password (or the phone) is incorrect.

[salvattore001]

adding the 9 worked! it seems that the 9 means it is a cell phone.. thanks!

[githubtefo]

We are from Argentina too. Since 4 days ago my girlfriend's account has the message "Server closed the connection". We tried to put "00", "+" with/without the "'9" with no results. Even we changed the Resource and nothing. She is living in another country so we cannot receive the sms code for restarting the account. Is there any other way to solve this? She is having problems to contact with her family and friends because all people use this f%&"¬ protocol! I hate The Corporation. Sorry but I'm so angry. Thanks david for your fight on the implementation of open communication protocols. C'mon, this is XMPP! Thanks.

[davidgfnet]

Hold on, if you have the SIM no matter in which country you are, you can still receive the SMS. And I'm pretty sure whatsapp forced a password update or something...

[eksperimental]

@davidgfnet how do i get a more verbose output on linux? i' m using pidgin -d > ~/debug.log 2>&1

thanks

[davidgfnet]

If you want to get a full WA protocol trace on linux you can compile the plugin using "make debug". This will print loads of stuff on stdout.

[eksperimental]

@davidgfnet thanks