When the config file was missing I simply ran "Rclone config" when it asked if i already had an access grant I said
YES and it asked for what service I chose Storj and then it asked for the access grant and I copy and pasted
it in there.
here is the whole lot of what is in that config file :
[Storj]
type = storj
access_grant = XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX
the x's are words in mine just wanted to make sure not to post the actual one here
i am not an expert with storj, but that seems to be the problem, it should not be a bunch of words.
rclone will obscure it in the config
this is what my working remote looks like
[storj]
type = storj
access_grant = 15M6fjomdWMwh4cdbZx5YmDQpQsc8EN73sYKcfLodh6yz6PXEbNJe1WKFvKrwMotebVhRWPiihQoPEuKkaEt1reW5WhPwipmRZnqcfnA43NZ1n8kCgxqoqAwoBffxLeRCu84UQw31xZm7zhP6usBrDThdwQcPWLGC51qJRooL2Qd8mb2ovUkqK1M15eNhxv52Q3q6yZGp7CAAq5dQDbTQ3cSyW1aedbGudo3vSVmtBVrzpRgLxAma3SJii8oKLVTs4FGEthS5pdK4KzcTiim1KGnJhYF2
So should that be the "Secret Key" and not the Access grant then? the Secret key looks like the one you sent
from the docs,
Storj can be used both with this native backend and with the s3 backend using the Storj S3 compatible gateway
so which backend are using?
S3 Credentials
That's what i chose when setting up on the storj side
I also used the other format
but that does not seem to work either getting same error
iamonddog@diamonddog-desktop:~$ rclone mount Storj: ~/Storj
2023/10/16 21:12:32 Failed to create file system for "Storj:": storj: access: uplink: invalid access grant format
diamonddog@diamonddog-desktop:~$
This is not S3 remote. This is storj direct access one - which also can be used if setup properly in storj web UI.
I strongly recommend to use S3 access method over storj. The latter is extremely heavy on network resources - can be easily too much for no pro equipment as it requires connections to thousands of nodes at the same time.
FYI - this is how S3 storj remote config should look like:
[storjS3]
type = s3
provider = Storj
access_key_id = rzppqekv.....i1aqv11oaf
secret_access_key = ewgt49jykbdp...............4lm5ejvkzzq9liriv4essfg244w
endpoint = gateway.storjshare.io
chunk_size = 64Mi
disable_checksum = true
When you run rclone config you have to choose Amazon S3 remote, NOT storj remote - simply follow steps from my link if you are not sure what you are doing. Or copy/paste above example and replace access_key/secret with your values
then as @asdffdsa already mentioned you can test it with:
rclone ls storjS3: -vv
Only when this works you can move to playing with mount.
Ok I made the config file look identical to yours with the exception of your credentials
[storjS3]
type = s3
provider = Storj
access_key_id = jxulx7................ii5l6a
secret_access_key = j3eyb55ep................4hd47duww4yptfamsmem6q
endpoint = gateway.storjshare.io
chunk_size = 64Mi
disable_checksum = true
But still get this error :
diamonddog@diamonddog-desktop:~/.config/rclone$ rclone mount Storj: ~/Storj
2023/10/17 08:28:37 Failed to create file system for "Storj:": didn't find section in config file
and here is the debug below
diamonddog@diamonddog-desktop:~/.config/rclone$ rclone ls storjS3: -vv
2023/10/17 08:31:52 DEBUG : rclone: Version "v1.64.0" starting with parameters ["rclone" "ls" "storjS3:" "-vv"]
2023/10/17 08:31:52 DEBUG : Creating backend with remote "storjS3:"
2023/10/17 08:31:52 DEBUG : Using config file from "/home/diamonddog/.config/rclone/rclone.conf"
2023/10/17 08:31:52 DEBUG : Resolving service "s3" region "us-east-1"
2023/10/17 08:31:53 DEBUG : 6 go routines active
What is wrong with the mount?
Ok changed a few things and got this now :
diamonddog@diamonddog-desktop:~/.config/rclone$ rclone mount storjS3: ~/storj -vv
2023/10/17 08:37:58 DEBUG : rclone: Version "v1.64.0" starting with parameters ["rclone" "mount" "storjS3:" "/home/diamonddog/storj" "-vv"]
2023/10/17 08:37:58 DEBUG : Creating backend with remote "storjS3:"
2023/10/17 08:37:58 DEBUG : Using config file from "/home/diamonddog/.config/rclone/rclone.conf"
2023/10/17 08:37:58 DEBUG : Resolving service "s3" region "us-east-1"
2023/10/17 08:37:58 INFO : S3 root: poll-interval is not supported by this remote
2023/10/17 08:37:58 DEBUG : S3 root: Mounting on "/home/diamonddog/storj"
2023/10/17 08:37:58 Fatal error: failed to mount FUSE fs: fusermount: exec: "fusermount3": executable file not found in $PATH
I have installed FUSE3 now and i am getting this output:
2023/10/17 08:42:59 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwxr-x, err=
2023/10/17 08:42:59 DEBUG : /: ReadDirAll:
2023/10/17 08:42:59 DEBUG : /: >ReadDirAll: item=3, err=
2023/10/17 08:42:59 DEBUG : /: Attr:
2023/10/17 08:42:59 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwxr-x, err=
2023/10/17 08:42:59 DEBUG : /: ReadDirAll:
2023/10/17 08:42:59 DEBUG : /: >ReadDirAll: item=3, err=
2023/10/17 08:42:59 DEBUG : /: Lookup: name="autorun.inf"
2023/10/17 08:42:59 DEBUG : /: >Lookup: node=, err=no such file or directory
^C2023/10/17 08:43:52 INFO : Signal received: interrupt
2023/10/17 08:43:52 ERROR : /home/diamonddog/storj: Unmounted rclone mount
2023/10/17 08:43:52 INFO : Exiting...
I am now stuck here. What do I do next?
It works now. You can start using it
Looks like you pressed ctrl-C and terminated it.
I did not push control C or Z at all. It just stopped all by itself.
ok run
rclone lsd storjS3: -vv
diamonddog@diamonddog-desktop:~/.config/rclone$ rclone lsd storjS3: -vv
2023/10/17 08:51:59 DEBUG : rclone: Version "v1.64.0" starting with parameters ["rclone" "lsd" "storjS3:" "-vv"]
2023/10/17 08:51:59 DEBUG : Creating backend with remote "storjS3:"
2023/10/17 08:51:59 DEBUG : Using config file from "/home/diamonddog/.config/rclone/rclone.conf"
2023/10/17 08:51:59 DEBUG : Resolving service "s3" region "us-east-1"
-1 2023-10-16 18:53:48 -1 compdrive
2023/10/17 08:51:59 DEBUG : 5 go routines active
It looks like its working, let me try again. Also how do I make sure it mounts on boot?
Good news then.
There are many ways but I suggest you use systemd. Here some example: