Hi Jonathan,
You can navigate to your account on a browser
to https://accounts.google.com/DisplayUnlockCaptcha. See
https://support.google.com/accounts/answer/2461835?hl=en for details.
Cheers,
Anash P. Oommen,
AdWords API Advisor.
On Tuesday, May 14, 2013 11:04:35 AM UTC-7, Jonathan Wu
Thanks fixed it. Thanks!
On Tuesday, May 14, 2013 5:52:00 PM UTC-7, Anash P. Oommen (AdWords API
Team) wrote:
Hi Jonathan,
You can navigate to your account on a browser to
https://accounts.google.com/DisplayUnlockCaptcha. See
https://support.google.com/accounts/answer/2461835?hl=en for
This is part of standard risk detection. The IP address your server uses
to access ClientLogin is different from the IPs that the account normally
logs in as (which is what it looks like when someone has compromised the
account). As a result you'll get the 403. You can use the CAPTCHA unlock
Hi Jonathan,
It could be that Google ClientLogin servers are seeing programmatic login
from this machine for the first time and blocking your request. Open a
browser on this machine, and login to your account and see if it solves the
issue. If your machine is indeed blocked by ClientLogin,
This is on a headless linux server. We've never had this issue with any
other account we have API access to on this machine and further, it doesn't
make sense that we would have to do this per machine per account. This
machine is using the API to do things like grab Campaign data using the
Nope. We actually have access to numerous client accounts. This particular
account is the only one with an issue on that machine.
I at first thought that the account wasn't fully authorized for API access,
but then I tried it in my local dev environment and it worked.
On Monday, April 1, 2013
Jonathan,
Any chance the machine with the issue is configured to use a proxy or is
behind a hardware firewall of some kind?
Jason
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
Hello,
We have an account (327-036-4904) where we get a 403 response when
generating a client login token on one machine, but not on another. Is
there any reason for this happening?
here is the root cause in the Java stacktrace:
Caused by:
