Jotta Cloud stopped working after rclone upgrade - empty token found

Hi @ncw,

Thanks for your quick reply. I did not copy the conf file. I have generated each conf separately, selecting "yes" on the "Do you want to create a machine specific API key" question per machine.

I am guessing maybe the issue is related to the token expiration (not really due to both machines accessing).I have realized I can have a resource mounted in both machines and working for some time. After token expires is when I lose access on both machines.

I have tested updating the conf in only one machine (not accessing from the other) and after the token expires ("expiry":"2019-05-29T15:15:32.101468656+02:00") I am not able to access again at 15:45 receiving the error on rclone mount log:

2019/05/29 15:42:26 ERROR : jottacloud root 'newapproach/test': Statfs failed: Get https://www.jottacloud.com/jfs/jotta_username: oauth2: cannot fetch token: 400 Bad Request
Response: {"error":"invalid_grant","error_description":"The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client."}

Any clue?

Rclone should refresh the the token when it expires using the refresh token.

I run integration tests with Jottacloud once per day and I've never had this problem there.

I wonder if it is because of your long running mount somehow.

I just merged a new auth scheme for Jottacloud - can you have a go with that?

https://beta.rclone.org/v1.47.0-088-g11264c4f-beta/ (uploaded in 15-30 mins)

If that still doesn't help then please please make a new issue on github and we can get the Jottacloud maintainer to take a look.