Hi all,
I have a new Storj account which I’d like to use to backup data from my TrueNAS ElectricEel-24.10.1 system. In Storj, I’ve created a new bucket. I’ve created a new access key for trueNAS where I granted Full Access.
Now in TrueNAS, when I try to define a new TrueCloud Backup Task, when I open the “Bucket” drop-down I can see my bucket in the list but it’s greyed out and not select-able.
Anybody know why this could be?
Thanks,
Justin
I don’t know the reason but using a bucket created in storj web interface did not work for me either. Selecting “Add new” in TrueNAS is working.
So over 2 years iXsystems did nothing to make this more user-friendly? 
How about using “Amazon S3” instead of “Storj iX” in TrueNAS to connect existing storj buckets? Could this work or am I missing something? 
Just don’t use the “integration”. It’s a pathetic half-baked nonsense. They don’t even use native storj integration - it’s still s3 anyway.
Hello @justinb,
Welcome to the forum!
You have several options:
For pp.2-4 you would not be able to get an IX Starter Package, because to apply the value attribution to your account it must be PRO, but to use an IX Starter Package you need to upgrade from a free trial account, later it will not be available. The upgrade to IX Starter Package is available only if your account has an IX systems value attribution (which is not available for the regular Storj account).
They did. You may create a new bucket bucket from the TrueNAS UI and it will allow to select it, even if this is a usual Storj account without IX system value attribution (they would add it for that specific bucket).
This is does not help. There is no reason for them to create extra friction for users who want to use storj by disallowing to use buckets (let alone accounts) created the way user wants.
The actual reason is of course they half backed the solution and it was probably easier to add restrictions than properly design it to support proper access grants or at least encryption passphrase.
This “integration” was conceived by marketing and implemented enough to put a checkmark in marketing materials and formally satisfy partnership agreements.
In my personal opinion, as a long time TrueNas (over 7? Maybe 10? years) and Storj (over 2 years) user, the IX_Storj integration in TrueNAS, as of today, is an unusable counterproductive gimmick, that casts bad shadow on an excellent NAS OS, excellent rclone under the hood, and excellent storage service Storj. It shall be redone or removed asap.
It actually works, they add a needed tuning out of the box when you use a Storj S3 credentials rather than a Generic ones (you do not have a required options in the UI).
Also:
TrueNAS and Storj works better together. I’m very excited that we finally finished the restic integration to make TrueCloud Backup possible.
Add to the confusion here that Storj’s own documentation for TrueNAS instructs you to create the bucket through the UI: TrueNAS Integration with Storj for Secure Data Storage - Storj Docs
I’m also unsure of how to create this bucket without granting TrueNAS permission to my entire account? Seems if you go the option of creating limited credentials, the bucket must be in place first, which then means you can’t select it in TrueNAS.
I agree with others. It’s not very user-friendly at the moment.
Hello @g-de,
Welcome to the forum!
The instruction for users, who registered using a special link from TrueNAS, then the required value attribution will be added automatically, so doesn’t matter how to create a bucket - using a Storj Console, or TrueNAS itself.
However, there is a difference in storage tiers and prices, and if you would create a bucket from TrueNAS, it will be on the tier Global Collaboration by default.
But for the case when your account/project doesn’t have a required value attribution the bucket will not be available in TrueNAS, if it would be created from the Storj Console.
There is a workaround though: to be able to specify a storage tier and required value attribution for a new bucket you can use rclone:
rclone mkdir storj-s3-us1:my-bucket --user-agent "ix-storj-1" --s3-location-constraint "archive-1"
You can also submit a support request to apply the required value attribution for every level:
If you would create a bucket like showed above or if your account/project(s)/bucket(s) will be updated with a required value attribution, then you can create S3 credentials limited only to the needed bucket and use them in TrueNAS.
Ok I’ve contacted support to try have the attribute added to my account. Having to use RClone, or contact support if I ever want to create additional compatible archive buckets seems very counter-intuitive, so hopefully it can be set once at account level and that be it.
This is happened because you registered a regular Storj account, not a special one using the link from TrueNAS, so the required value attribution is now missing.
There are three ways how to fix:
rclone mkdir command above