Service account with encrypted remote?

Help and Support
1

Hey,

So I've got service account credentials working I think. I pass the drive service account file and impersonation via the command line. However, this is while listing my encrypted remote. Does the actual remote it connects to (the non encrypted one) need to also have the service file set in config?

2

You add the service account stuff to the type = drive backend only.

3

So I make duplicates of the "drive" one with the service file parameters and then duplicates of the crypt one referencing the individual drive remotes ?

4

That is correct (assuming you want to keep a non service account access method)

5

Hey so i got things like listing a remote working but uploads still don't start? They stall at 0. Its definitely using the service account as I made a new "drive" remote and didn't have to login but still no upload progress. What am I doing wrong?

6

Share a log with -vv and we can look at the output.

7

2019/05/19 10:24:07 DEBUG : rclone: Version "v1.46" starting with parameters ["rclone" "copy" "ATEST" "GEnc1:test3" "--stats=2s" "-vv"]
2019/05/19 10:24:07 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2019/05/19 10:24:09 DEBUG : pacer: Rate limited, sleeping for 1.502358294s (1 consecutive low level retries)
2019/05/19 10:24:09 DEBUG : pacer: low level retry 1/10 (error googleapi: Error 403: User rate limit exceeded., userRateLimitExceeded)
2019/05/19 10:24:10 DEBUG : pacer: Resetting sleep to minimum 100ms on success
2019/05/19 10:24:10 INFO : Encrypted drive 'GEnc1:test3': Waiting for checks to finish
2019/05/19 10:24:10 INFO : Encrypted drive 'GEnc1:test3': Waiting for transfers to finish
2019/05/19 10:24:10 DEBUG : pacer: Rate limited, sleeping for 1.30516586s (1 consecutive low level retries)
2019/05/19 10:24:10 DEBUG : pacer: low level retry 2/10 (error googleapi: Error 403: User rate limit exceeded., userRateLimitExceeded)
2019/05/19 10:24:10 INFO :
Transferred: 0 / 391.708 GBytes, 0%, 0 Bytes/s, ETA -
Errors: 0
Checks: 0 / 0, -
Transferred: 0 / 2091, 0%
Elapsed time: 3.2s
Transferring:
BLANKED

^C2019/05/19 10:24:11 DEBUG : pacer: Rate limited, sleeping for 2.273233675s (2 consecutive low level retries)
2019/05/19 10:24:11 DEBUG : pacer: low level retry 1/10 (error googleapi: Error 403: User rate limit exceeded., userRateLimitExceeded)
2019/05/19 10:24:12 INFO :
Transferred: 0 / 391.708 GBytes, 0%, 0 Bytes/s, ETA -
Errors: 0
Checks: 0 / 0, -
Transferred: 0 / 2091, 0%
Elapsed time: 5.2s
Transferring:
BLANKED

2019/05/19 10:24:12 DEBUG : pacer: Rate limited, sleeping for 4.501346449s (3 consecutive low level retries)
2019/05/19 10:24:12 DEBUG : pacer: low level retry 1/10 (error googleapi: Error 403: User rate limit exceeded., userRateLimitExceeded)

8

Is that the whole log? Looks like you are out of quota for the day.

9

Yeah. I stopped it after that. Running before with same settings / command is the same but longer.

Why would I bet out of quota for the day while using a service account? I thought that was the point.

10

Any account still has a 750GB limit each day if it's a user account or a service account.

11

I just created this service account tho.
Did I make it wrong?

I know my main user has reached their upload limit for the day.

When I create a service account, there is an option to like assign it to a user. Do I select one of my other user accounts and then use impersonation?

12

I am not sure how avoiding the limits works as it isn't something I think is a good thing to do.

I'm sure someone else can chime in.

13

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.