Machine system clock is incorrect ??

[saintthor]

why cause this? the password is right.

i run this in a remote machine which is in another timezone.
===================


$ python appcfg.py download_app -A djdqbbs -V d2 ./djdq
09:48 AM Host: appengine.google.com
09:48 AM Fetching file list...
Email: saintthor
Password for saintthor:
Invalid username or password.
Email: saintthor
Password for sain...@gmail.com:
Invalid username or password.
Email: saintthor
Password for saintthor:
Invalid username or password.

Error: Machine system clock is incorrect.

[Mihail Russu]

 - Has it ever worked?

 - Have you tried the obvious - making sure the time on your systems is correct?

Quick googling shows some other possible reasons like:

 - You might be in a "Viewer" or some other role that does not allow what you are trying to do.

 - Enabling the "access less secure apps" option in account settings which doesn't really sound right, instead I would try to add the --oauth2 parameter to authenticate via browser.

Have you checked these?

[saintthor]

it hasn't worked. it is the first time i try to download via a remote system.


the time seems correct. you see in the infos it is 9:48 AM UTC 0. about 10 mins later i posted here at 12:00:47 PM UTC+2.

 - You might be in a "Viewer" or some other role that does not allow what you are trying to do.

maybe. i try this on koding.

 - Enabling the "access less secure apps" option in account settings which doesn't really sound right, instead I would try to add the --oauth2 parameter to authenticate via browser.

i connect to the host via ssh, there is no browser to use --oauth2.

在 2015年2月4日星期三 UTC+8下午7:20:50，Mihail Russu写道：

[saintthor]

it is caused by the google security setting. even in my local system can not usr appcfg.py before turns the setting off.

在 2015年2月4日星期三 UTC+8下午11:01:57，saintthor写道：

[Mihail Russu]

Sorry, missed your messages. There are two other options besides enabling the "less secure" setting:

1. Enable two-factor authentication and generate an app specific password which you will use for GAE only.

2. Use --oauth2 parameter to generate a token. Since you're doing this on a remote machine without a browser - it's still possible  with the --noauth_local_webserver (see more).

Thanks,

Mihail.

[Marcial Roman]

As announced before community support is moving to Stack Overflow. [1] 

I will recommend you to post this specific question on Stack Overflow. Simply post your question tagging it with "google-app-engine", and a member of our support team or a member of our global developer community will respond shortly after.

Happy coding!

[1] https://groups.google.com/forum/#!topic/google-appengine/Z6XN_64cA7w

[Alex Martelli]

On Monday, February 9, 2015 at 11:13:23 PM UTC-8, Marcial Roman wrote:

As announced before community support is moving to Stack Overflow. [1] 

Yes, that was the decision three years ago -- but we're going to do things slightly differently going forward.

StackOverflow (SO) is about **software development** questions, with some further constraints -- see http://stackoverflow.com/help/on-topic .  The SO community understandably does *not* appreciate questions that are not about SW development -- in particular, questions about system and network administration have their own site within the same "stackexchange" family -- ServerFault (SF).

Many technical questions about App Engine are indeed about SW development and perfectly appropriate for SO -- great!

*But* a few technical questions are instead about system and network administration -- and, for those, SF is the right place.

And of course some questions are not welcome on either site -- for example, quoting from the FAQ above, "Questions asking us to recommend or find a book, tool, software library, tutorial" are not welcome there.  For those kind of questions, this Google Group is therefore the best place to ask!

 

I will recommend you to post this specific question on Stack Overflow. Simply post your question tagging it with "google-app-engine", and a member of our support team or a member of our global developer community will respond shortly after.

I would consider this specific question to be most likely a system administration one -- thus more appropriate for Server Fault (with the same tag).  We do sponsor and monitor tags "google-app-engine", "google-compute-engine", and "google-cloud-platform" on both SO and SF.  Yes, I do need to change https://cloud.google.com/support/ , which does not mention ServerFault; I'm working on that:-).

To me, it's part of acknowledging that we don't only have a *developer* community -- there's also a community of *system administrators*, some of whom may also be developers, but not necessarily all of them -- likely a smaller community, but highly professional and fully deserving of our support and recognition.  (The issue looms larger for other Google Cloud Platform products, like Google Compute Engine, where the ratio of developer vs sysadm questions is also larger than for App Engine; but it makes sense for GAE, too!-).

Happy coding!

...and happy system-administering, too!-)

Thanks,

Alex