Onlime [Jottacloud] requires reconnect every day

Help and Support
1

What is the problem you are having with rclone?

The problem I'm facing is that I have used Onlime for a while (which works via the Jottacloud setup) and had no issues so far. Then, all of a sudden, my node started to lose connection to the mount on a daily basis. I now need to reconnect to my Onlime storage every day in order to be able to use it. I do not understand what's happening or how I would be able to fix this.

Run the command 'rclone version' and share the full output of the command.

rclone v1.67.0

  • os/version: debian 12.7 (64 bit)
  • os/kernel: 6.1.0-21-amd64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.22.4
  • go/linking: static
  • go/tags: none

Are you on the latest version of rclone? You can validate by checking the version listed here: Rclone downloads
Yes

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

Onlime (Jottacloud)

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

rclone mount oshbc: /mnt/oshb --allow-other --gid 1000 --uid 1000 --umask 002 --dir-cache-time 1h --allow-non-empty --transfers 6 --vfs-cache-mode full --vfs-read-chunk-size 32M --vfs-read-chunk-size-limit 256M --vfs-cache-max-size 32G --vfs-fast-fingerprint --vfs-cache-max-age 1h --cache-dir /tmp/.oshb --cache-db-purge --tpslimit 12 --tpslimit-burst 0 --jottacloud-hard-delete

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

type = jottacloud
configVersion = 1
client_id = XXX
tokenURL = https://cloud-auth.onlime.dk/auth/realms/onlime_wl/protocol/openid-connect/token
token = XXX
device = 
mountpoint = 

[oshb]
type = alias
remote = onlime:SynologyHyperBackup

[oshbc]
type = crypt
remote = oshb:
filename_encryption = standard
directory_name_encryption = true
password = XXX
password2 = XXX
no_data_encryption = false

A log from the command that you were trying to run with the -vv flag

2024/09/03 22:21:52 INFO  : Starting transaction limiter: max 12 transactions/s with burst 1
2024/09/03 22:21:52 DEBUG : rclone: Version "v1.67.0" starting with parameters ["rclone" "mount" "oshbc:" "/mnt/oshb" "--allow-other" "--gid" "1000" "--uid" "1000" "--umask" "002" "--dir-cache-time" "1h" "--allow-non-empty" "--transfers" "6" "--vfs-cache-mode" "full" "--vfs-read-chunk-size" "32M" "--vfs-read-chunk-size-limit" "256M" "--vfs-cache-max-size" "32G" "--vfs-fast-fingerprint" "--vfs-cache-max-age" "1h" "--cache-dir" "/tmp/.oshb" "--cache-db-purge" "--tpslimit" "12" "--tpslimit-burst" "0" "--jottacloud-hard-delete" "-vv"]
2024/09/03 22:21:52 DEBUG : Creating backend with remote "oshbc:"
2024/09/03 22:21:52 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2024/09/03 22:21:52 DEBUG : Creating backend with remote "oshb:"
2024/09/03 22:21:52 DEBUG : Creating backend with remote "onlime:SynologyHyperBackup"
2024/09/03 22:21:52 DEBUG : onlime: detected overridden config - adding "{jlU5h}" suffix to name
2024/09/03 22:21:52 DEBUG : onlime{jlU5h}: Loaded invalid token from config file - ignoring
2024/09/03 22:21:53 DEBUG : onlime{jlU5h}: got fatal oauth error: oauth2: "invalid_grant" "Session doesn't have required client"
2024/09/03 22:21:53 Failed to create file system for "oshbc:": failed to make remote "oshb:" to wrap: couldn't get customer info: Get "https://api.jottacloud.com/account/v1/customer": couldn't fetch token: invalid_grant: maybe token expired? - try refreshing with "rclone config reconnect onlime{jlU5h}:"
2

Are you connecting rclone to Jottacloud from more than one machine?
Asking as Jottacloud wants you to create a separate token for each individual server/machine accessing it.

3

No; I have a debian machine that solely has access to Onlime (only one with the configuration and the mount).

Other devices access this mount through rsync.

4

Is this something that might help?

2024/09/04 18:16:44 DEBUG : onlime{jlU5h}: Loaded invalid token from config file - ignoring
2024/09/04 18:16:44 DEBUG : onlime{jlU5h}: got fatal oauth error: oauth2: "invalid_grant" "Session doesn't have required client"
2024/09/04 18:16:44 ERROR : BraveBirdSSD_092024.hbk/Pool/0/0/527.index.3: Failed to copy: Post "https://api.jottacloud.com/files/v1/allocate": couldn't fetch token: invalid_grant: maybe token expired? - try refreshing with "rclone config reconnect onlime{jlU5h}:"
2024/09/04 18:16:44 ERROR : BraveBirdSSD_092024.hbk/Pool/0/0/527.index.3: vfs cache: failed to upload try #69, will retry in 5m0s: vfs cache: failed to transfer file from cache to remote: Post "https://api.jottacloud.com/files/v1/allocate": couldn't fetch token: invalid_grant: maybe token expired? - try refreshing with "rclone config reconnect onlime{jlU5h}:"

And later

2024/09/04 23:39:59 DEBUG : onlime{jlU5h}: got fatal oauth error: oauth2: "invalid_grant" "Invalid refresh token. Token client and authorized client don't match"
2024/09/04 23:39:59 ERROR : /: Dir.Stat error: couldn't list files: Get "https://jfs.jottacloud.com/jfs/<>/Jotta/Archive/SynologyHyperBackup": couldn't fetch token: invalid_grant: maybe token expired? - try refreshing with "rclone config reconnect onlime{jlU5h}:"
2024/09/04 23:39:59 ERROR : IO error: couldn't list files: Get "https://jfs.jottacloud.com/jfs/<>/Jotta/Archive/SynologyHyperBackup": couldn't fetch token: invalid_grant: maybe token expired? - try refreshing with "rclone config reconnect onlime{jlU5h}:"
2024/09/04 23:39:59 DEBUG : /: >Lookup: node=<nil>, err=couldn't list files: Get "https://jfs.jottacloud.com/jfs/<>/Jotta/Archive/SynologyHyperBackup": couldn't fetch token: invalid_grant: maybe token expired? - try refreshing with "rclone config reconnect onlime{jlU5h}:"

So basically:

  • Session doesn't have required client
    And when I did a reconnect;
  • Token client and authorized client don't match
5

That looks just like when I tried using the same token on two servers, before I knew that Jotta needs each server to have its own token.

6

That is interesting as it is not the case that I use it for multiple devices.

I have escalated the issue with Onlime. My personal assessment based on required client is that it might have to do with the configuration client_id = . According to the manual it should be set to either jottacli, or desktop (it defaults to the latter). This always worked but maybe something changed in the API and therefore the token expires for not having the client_id set properly?

Maybe I'm looking in the completely wrong direction though.

7

I basically removed everything and started from scratch. Created a new key in the backend of Onlime and reconfigured everything. This seems to have worked as I haven't run into issues for the past 3 days now.

8

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