Closed jlguardi closed 9 years ago
It looks like your numbers are blocked. Use existsrequest.py to see the reason why you cannot login.
No, the number is not blocked. I've tried in an official whatsapp and works.
While the register with yowsup I get:
status:' ok '
kind:' free '
pw:' xxxxxxxxxxxxxxxxxxxx= '
price:' 0,89 $'\342\202\254' '
price_expiration:' 142746xxxx '
currency:' EUR '
cost:' 0.89 '
expiration:' 144148xxxx '
login:' 34xxxxxxx '
type:' existing '
EDIT: So now I am getting the same problems. But only when I am using SendClient while the yowsup-cli demo is not affected. I guess WA rolled out an intern update. Maybe they block auth tries when they are not in line with 'special conditions'.
SOLVED: by re-registering and changing the password in the config file with the one received as a response to the second step of registration.
Still with the same problem here using the yowsup-cli demo.
Anything related to the options in the config file?
Cheers.
Here is a little Update from what I noticed. SendClient is working again (without doing anything - that confirmed my theory) But right now I am having two sample_apps. One of them is working correctly the second one is still getting auth errors. I guess I messed something up in the code though it worked before.
@jlguardi Did you manage to register your number again? And is it visible to other users in the official WhatsApp client?
I've got 2 numbers with this issue. Both were working until I've restarted my applications. So WA didn't close the connection. After this restart, both return 'not-authorized'. One of them keeps in this status. However, the other is working after a reregistration with yowsup and no more errors have been detected. Both are visible from official WA. @blackjack4494 I get this error with my app and also with yowsup-cli, echo-client or send-client
@jlguardi How long ago did you register these two numbers?
No working one on april'14. The other one on sept'14.
It actually does not matter when you registered your numbers as long as you pay after the first free year.
@jlguardi hmm. Did you restart your server/sytem where it is running on? I can try to give you a little sample app where you have to edit just the number and password. I can post it later (in like 6hours?) What happens when you use :yowsup-cli demos -c config -y :/L ??
No, my server is workin for 5 months without restart. All reports are get with "yowsup-cli demos -y".
I'll try your app. Thx
I had some SIM Cards blocked today... All of them were using the same App. Some (3 of 10) got banned....
I was not sending SPAM. I´ve used in a Passive way (providing automated answers, when asked), like a FAQ.
Tried re-register, but failed.
Tried with Whatsapp Official Client, but it is said that the number is unauthorized to use Whatsapp.
Any of you with the same problem?
I've got the same problem in centos. When I try to login i get next:
Type /help for available commands
Traceback (most recent call last):
File "/usr/bin/yowsup-cli", line 5, in
@jlguardi did you solved the problem? I'm having the same issue.
@pcandrews In fact I needed to reregister 3 lines of 10. These lines are the older ones registered between april'14 and Aug'14. No more incidentes by the moment.
@ssafronov it seems not to ne the same. Your issue seems a communication problem not an authorization one.
I have the same issue
Re-registration did not solve the issue for me,
While the cli-demo does work (yowsup-cli demos -y -l NUMBER:PASSWORDHASH=
),
my run.py program does not (following the sample app tutorial).
Did I missed some other solution than registrating them again?
Is there a Layer which I missed?
.
For refence, my stacktrace, which is long and ugly, sorry:
DEBUG:yowsup.layers.network.layer:Disconnected, reason: Authentication Failure Traceback (most recent call last): File "run.py", line 54, in <module> stack.loop() #this is the program mainloop File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/stacks/yowstack.py", line 174, in loop File "/opt/python3.4/lib/python3.4/asyncore.py", line 208, in loop poll_fun(timeout, map) File "/opt/python3.4/lib/python3.4/asyncore.py", line 153, in poll read(obj) File "/opt/python3.4/lib/python3.4/asyncore.py", line 87, in read obj.handle_error() File "/opt/python3.4/lib/python3.4/asyncore.py", line 83, in read obj.handle_read_event() File "/opt/python3.4/lib/python3.4/asyncore.py", line 442, in handle_read_event self.handle_read() File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/network/layer.py", line 48, in handle_read ################### File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/network/layer.py", line 55, in receive def __init__(self): File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/__init__.py", line 55, in toUpper File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/stanzaregulator/layer.py", line 28, in receive if tg_peer in tg_wa: File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/stanzaregulator/layer.py", line 48, in processReceived ################### File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/__init__.py", line 55, in toUpper File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/auth/layer_crypt.py", line 63, in receive File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/__init__.py", line 55, in toUpper File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/coder/layer.py", line 35, in receive if wa_peer in wa_tg: File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/__init__.py", line 55, in toUpper File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/__init__.py", line 160, in receive File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/__init__.py", line 101, in receive File "/home/luckydonald/wa-tg-bridge/virtualenv_3.4.3/lib/python3.4/site-packages/yowsup2-2.2.78-py3.4.egg/yowsup/layers/auth/layer_authentication.py", line 65, in handleFailure yowsup.layers.auth.autherror.AuthError: not-authorized
Well, as always, updating to the newest source code version can fix stuff. See #754 and fix 6345f77. The old password might still work.
I´m having the same problem as rodrigofaillace. I have a number that was blocked by WhatsApp.
Error message: "Authentication Error: not-authorized"
yowsup2 upgrade does not solve the problem.
Any solution?
did you also ran the setup again?
Yes. It was working and has stopped with this error message. I´ve already tried the yowsup2 upgrade without success.
Thanks.
On Tue, Jul 28, 2015 at 11:32 PM, Luckydonald notifications@github.com wrote:
did you also ran the setup?
— Reply to this email directly or view it on GitHub https://github.com/tgalal/yowsup/issues/652#issuecomment-125813978.
Atenciosamente, Rodney A. Ramos
I had the same problem and received this message: general: Login Failed, reason: not-authorized Auth Error, reason not-authorized
Getting the same issue. When running the demos cli I can send/receive messages but with a run.py or layer.py the error is yowsup.layers.auth.autherror.AuthError: not-authorized. Running latest version of yowsup
anybody can help me with this?
Parsing config: config.yaml
Traceback (most recent call last):
File "C:\Users\Yuana\Desktop\whatsapp-email-bridge-master\WhatsAppEmailForwarder.py", line 617, in
Since this morning, all my numbers report an error during Login. No change in credentials or code was performed.
I attach the log detail. This log was gotten with yowsup-cli of master branch download some minutes ago:
Has someone any solution or suggestion?