Hubic stops working after auto token refresh

What is the problem you are having with rclone?

Hubic backed stops working after auto token refresh.

I create hubic backed, verify that it works.
It works until the token auto-refreshes.

Then it stops working and gives error below.

What is your rclone version (output from rclone version)


Which OS you are using and how many bits (eg Windows 7, 64 bit)

Arch Linux 64bit

Which cloud storage system are you using? (eg Google Drive)


The command you were trying to run (eg rclone copy /tmp remote:tmp)

restic -r rclone:hubic:restic snapshots

A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)

Failed to create file system for "hubic:restic": error authenticating swift connection: failed to get credentials: 401: { "error":"invalid_token", "error_description":"not found" }

Maybe the problem is that I am using hubic like this from more machines - so my guess - if one machine renews the token, it stops working on the other ones?

It so, how to properly configure the hubic on each machine differently?

Thanks for any advices..

Did you copy the config file from one machine to the other?

It might be that you need to run rclone config reconnect hubic: on each machine to generate a unique refresh token.

I didn't know hubic worked like that, but box certainly does - the refresh tokens are only useable once.

OK, I finally put syncthing synchronization around rclone.conf - a bit sucks, but seems to work...

1 Like

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