I’ve been trying to mount my storj buckets to linux (Debian 11.3) and rclone 1.58.1. Sometimes the mount works, sometimes it doesnt. Even when it is mounted, I can only see the 2 buckets I have but not their contents. Both buckets have folders and files in them. I’m able to make a connection to storj using the rclone config wizard and access grant key.
I’m not sure if this is an rclone issue or storj issue or if there’s something I’m missing.
This is the mount command I’ve been using:
rclone mount arthaus_storj3 /etc/levideo --allow-other --log-file=/etc/rclonelog/storjmountlog.txt --log-level DEBUG
I tried connecting to my storj account using cyberduck on windows and faced the exact same issue. I can see 2 buckets listed, but nothing in them. Both buckets have files and folders in them, which I can see through the web browser.
Any idea why storj could be refusing to show the files in the bucket?
Not seeing the content of a bucket usually indicates an incorrect encryption/access grant/key is being used. It is possible to use multiple encryption keys on the same bucket, but with different content shown depending on the access grant used.
I haven’t done it in a while but you should be able to use the web to create the access grant, which can then be imported into rclone. Use the same encryption phrase and then the same files are visible.
Thanks Stob for the detailed instructions and screenshots. This is exactly how I’ve been doing it. Should I try deleting my buckets, reuploading the content and try again with the new encryption passphrase?
Stob, I got it working. I tried making an access grant for a single bucket instead of both and used the same decryption key I use in the browser and it worked. Thank you for guiding me through this.
So is there a way to make 1 access grant for both buckets? If yes, which of the 2 decryption keys would I use here? I had a 3rd random generated key I was using. I might have saved it when setting up my account and buckets.
While making the access grant, the permissions page does have an option to make 1 grant for all buckets, but I’m slightly lost on how to get it working.
Just don’t select a bucket when creating the access grant. It is an optional restriction. If you don’t restrict the access grant it will be for all buckets including buckets you might create in the future.
You might also want to delete all existing buckets in the satellite UI even if they look empty. You might have some leftover files in these buckets. Deleting and recreating is the best way to make sure they get removed.
Yes exactly. The only reason you might want to use a different encryption key is too limit the damage if it ever gets leaked. For example I am using 2 different encryption keys for my duplicati backups and everything else. In this situation I want to restrict access and since I will never touch my duplicati backup with any other tools there is also no downside for me.
It seems there might be some changes regarding that in the future:
Maybe it’s a good idea to have some kind of information for the user who is presented with an empty bucket that this bucket is not really empty. However this might not be preferred under all circumstances. If I share a bucket, maybe I don’t want other users to know if there are still files that they simply are not allowed to see.
You can see that on the satellite dashboard. On the project view page you can see buckets and can confirm are they empty or not (Usage per bucket section), it shows used space, used egress and number of stored objects and segments for each bucket.
I created a bucket with a passphrase, then I associated that bucket with an app to upload files but without a passphrase, when I go to the panel and enter to see the files I only see a folder that I created but not what I uploaded in another folder.
Well it is up to you! You can use 1 password for your bucket or you can use many different passwords for one bucket.
But only those files are visible that match with the correct password.
This way you can have many users share a single bucket but they can only see and access the files they have a password to.
I think it is much better this way than having only the option to use one password per bucket.