Can't seem to be successful in authorising acd_cli again #559

Closed
Originn opened this Issue May 13, 2017 · 29 comments

Comments

Projects
None yet

Originn commented May 13, 2017

I have been trying to mount acd_cli on 16.04 ubuntu headless EC2. I have been successful on the first attempt, and the computer froze after trying to upload. I have created a new instance and tried to reinstall acd_cli, but now I get the following message after moving the oauth file to .cache/acd_cli.-

Press a key if you have saved the "oauth_data" file into "/root/.cache/acd_cli".

17-05-13 20:54:24.508 [CRITICAL] [acdcli.api.client] - Error getting endpoint data. Response: {"message":"Rate exceeded"}
Traceback (most recent call last):
File "/usr/local/bin/acd_cli", line 9, in
load_entry_point('acdcli==0.3.2', 'console_scripts', 'acd_cli')()
File "/usr/local/bin/acd_cli.py", line 1646, in main
acd_client = client.ACDClient(CACHE_PATH, SETTINGS_PATH)
File "/usr/local/lib/python3.5/dist-packages/acdcli/api/client.py", line 46, in init
self._load_endpoints()
File "/usr/local/lib/python3.5/dist-packages/acdcli/api/client.py", line 63, in _load_endpoints
self._endpoint_data = self._get_endpoints()
File "/usr/local/lib/python3.5/dist-packages/acdcli/api/client.py", line 80, in _get_endpoints
raise Exception
Exception

re installation does not help.

it is an amazon issue #550

yep same for me

M0V3 commented May 13, 2017 edited

Wait some hours, maybe a day.
We had this the last time about 24 days ago and it is an amazon api problem.

cpare commented May 13, 2017 edited

Same here - this appears to be an Amazon issue as my setup has been working for weeks:

cpare@raspberrypi:~$ /usr/local/bin/acd_cli -v sync
17-05-13 18:56:29.567 [INFO] [acd_cli] - Plugin leaf classes: TestPlugin
17-05-13 18:56:29.569 [INFO] [acd_cli] - TestPlugin attached.
17-05-13 18:56:29.570 [INFO] [acd_cli] - Settings path is "/home/cpare/.config/acd_cli".
17-05-13 18:56:29.571 [INFO] [acd_cli] - Cache path is "/home/cpare/.cache/acd_cli".
17-05-13 18:56:29.579 [INFO] [acdcli.api.client] - Initializing ACD with path "/home/cpare/.cache/acd_cli".
17-05-13 18:56:29.588 [INFO] [acdcli.api.oauth] - AppspotOAuthHandler initialized
17-05-13 18:56:34.844 [INFO] [acdcli.cache.schema] - DB schema version is 2.
Getting changes17-05-13 18:56:34.849 [INFO] [acdcli.api.metadata] - Getting changes with checkpoint "CLKBx5fAKxoA".
17-05-13 18:56:34.850 [INFO] [acdcli.api.backoff_req] - POST "https://cdws.us-east-1.amazonaws.com/drive/v1/changes"
Traceback (most recent call last):
  File "/usr/local/bin/acd_cli", line 9, in <module>
    load_entry_point('acdcli==0.3.2', 'console_scripts', 'acd_cli')()
  File "/usr/local/bin/acd_cli.py", line 1680, in main
    ret = args.func(args)
  File "/usr/local/bin/acd_cli.py", line 774, in sync_action
    ret = sync_node_list(args.full, args.to_file, args.from_file)
  File "/usr/local/bin/acd_cli.py", line 149, in sync_node_list
    file=to_file if to_file else None)
  File "/usr/local/lib/python3.4/dist-packages/acdcli/api/metadata.py", line 51, in get_changes
    raise RequestError(r.status_code, r.text)
acdcli.api.common.RequestError: RequestError: 429, [acd_api] no body received.

spuniun commented May 14, 2017 edited

I am able to mount my ACD with rclone just fine so it doesn't appear to be an API issue on Amazon's end.

M0V3 commented May 14, 2017

Confirmed, rclone works.

Harrdy commented May 14, 2017

same here, get "no body received." and "Rate exceeded" errors with acd but rclone still works

Hello, i can confirm the issue too.

"acdcli.api.common.RequestError: RequestError: 429, [acd_api] no body received.
17-05-14 09:34:06.223 [WARNING] [acdcli.acd_fuse] - Error getting account quota data. Cannot determine total and available disk space."

Same issues since yesterday evening :( Does everyone know, how to fix it? Maybe with a workaround?
Or do we really have to wait that Amazon fix it?

madyoda commented May 14, 2017

It almost sounds like acd_cli got revoked. @yadayada ?

image

SchnorcherSepp commented May 14, 2017 edited

maybe it's amazon reaction to
#549 (comment) or this #416

I wonder if you are right @SchnorcherSepp. It's possible they believe it to be an issue specific to acd_cli (I wonder if it could even be a caching bug in App Engine), and have cut off access. Either way, the fact they still aren't giving open access to the API makes this a bit of a pain. I'd be happy to use my own security profile if they'd damn well let me.

madyoda commented May 14, 2017 edited

@chrisgavin I guess we can ask @yadayada if they see anything in the Amazon console or w/e regarding the tensile-runway-92512.appspot.com.
Makes sense what you're saying - though.

<style></style>
Error
 

Over Quota

This application is temporarily over its serving quota. Please try again later.

Confirming the acd_cli error.

Em31Et commented May 14, 2017

acd_cli used cache to minimize api call, but rclone spam API.
It is no sense to ban acd_cli.

madyoda commented May 14, 2017

@Em31Et It does make sense to, atleast, temporarily ban acd_cli. See #549

@Em31Et It seems likely the ban was due to the recently reported security concern (okay it was reported a while ago but it seems Amazon is only now paying attention). I can't really blame Amazon for protecting customer data first and asking questions later.

Contributor

zmwangx commented May 14, 2017

It does make sense to, atleast, temporarily ban acd_cli.

My personal security profile, which should have nothing to do with acd_cli, also appears to be banned. Which makes no sense at all.

madyoda commented May 14, 2017

@zmwangx Huh. This is interesting, because rclone isn't revoked. Does your security profile make any references to acd_cli?

Contributor

zmwangx commented May 14, 2017

The name is unfortunately acd_cli... But banning profiles based on the name sounds incredibly stupid.

madyoda commented May 14, 2017

@zmwangx I agree, but maybe it's a blanket ban type situation until they figure out what exactly is causing #549 (possibly related) ?

Contributor

zmwangx commented May 14, 2017 edited

It's my security profile used only for myself. They can easily verify who's signed in with that profile, so cross-contamination is impossible unless I intentionally look into owning other people's files.

Also, anyone unaware of this project could have called their security profile acd_cli. It's not exactly an imaginative name.

They can probably check which software was used to access ACD anyway given that acd_cli sets a custom user agent. It's possible they banned based on that. Seems stupid though, given that the method for using a custom security profile should prevent any access tokens or refresh tokens from leaving your machine.

Contributor

zmwangx commented May 14, 2017

Not a user agent issue. I commented out the user agent patching part. Same thing.

I'll try to manually issue authorization requests after lunch to make sure that my security profile is indeed banned. I'll report back (sorry about the spam in advance).

Contributor

zmwangx commented May 14, 2017

Oh I just realized @chrisgavin was talking about software that was used to access ACD with the custom user agent. Yeah that's possible.

yadayada added the oauth label May 25, 2017

Owner

yadayada commented May 25, 2017

Please delete your oauth data and try again.

yadayada closed this May 25, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment