Problem with newly created r2 API tokens

Developers Storage
1

When creating a new R2 API token with Read & Write permissions it doesn’t seem to authenticate.

I have created multiple tokens in the past with no issues.

I am using Rclone to simply list the directories within an r2 bucket.

Error:

2024/06/14 12:05:43 ERROR : : error listing: Unauthorized: Unauthorized
	status code: 401, request id: , host id: 
2024/06/14 12:05:43 Failed to lsd with 2 errors: last error was: Unauthorized: Unauthorized
	status code: 401, request id: , host id:

I have used an existing token and it works fine.

I have also tested this on another colleagues device, with a separate Cloudflare account and a new bucket, with a new API token with the same rclone version and the latest rclone.

Am I going mental?

1 Like
2

Same here using Python:

botocore.exceptions.ClientError: An error occurred (Unauthorized) when calling the PutObject operation: Unauthorized

3

Same here. Old tokens work, but newly created don’t.

I’m using CyberDuck client.

4

Seems like tokens are not synced in any way.

New tokens don’t work. Rolling existing tokens does not invalidate them - the old ones still work.

5

Thanks for reporting this issue, we are currently investigating and the status can be tracked on our status page:

2 Likes
6

Same thing here, using @aws-sdk/client-s3.

He was going crazy trying to find a mistake, but in the end, after hours, everything was fine.

I don’t have old tokens, but the current ones are not working.

7

I am having the same problem, and I have tried many times. new API tokens don’t sync.

8

It seems newly created buckets also don’t sync.
We have created a bucket but we can’t get it sync. it just keeps saying bucket doesn’t exist.

9

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