Copied config file from Windows to Linux does not work

What is the problem you are having with rclone?

I set up rclone on a windows machine (version 1.58.1), and set up a Google Drive and Crypt remotes. Then I copied the config file over to a linux machine, and using that same config file am unable to see any of the files or mount the Crypt. It appears like the Google Drive is empty, but the CryptHowever, the rclone config dump --config /path/rclone.conf still appears exactly the same.

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

$ rclone version
rclone v1.58.1
- os/version: ubuntu 18.04 (64 bit)
- os/kernel: 4.16.18-galliumos5-pre1 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.17.9
- go/linking: static
- go/tags: none

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

Google Drive (with a Crypt inside)

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

rclone tree -vv --config /path/to/rclone.conf GDrive:

The rclone config contents with secrets removed.

$ rclone config dump --config /path/to/rclone.conf 
Enter configuration password:
password:
{
    "Crypt-GDrive": {
        "password": "longpass(matcheswindowsmachine",
        "password2": "morepass(matcheswindowsmachine)",
        "remote": "GDrive",
        "type": "crypt"
    },
    "GDrive": {
        "client_id": "lotsofnumbers(sameaswindows).apps.googleusercontent.com",
        "client_secret": "secretstuff",
        "scope": "drive",
        "team_drive": "",
        "token": "{\"access_token\":\"longlongtoken(different_than_windows_after_pulling_a_new_token)\",\"token_type\":\"Bearer\",\"refresh_token(matcheswindows)\":\"1//secretrefreshtoken\",\"expiry\":\"2022-06-25T03:12:50.256671886Z\"}",
        "type": "drive"
    }

A log from the command with the -vv flag

$  rclone tree -vv --config /path/to/rclone.conf GDrive:
<7>DEBUG : rclone: Version "v1.58.1" starting with parameters ["rclone" "tree" "-vv" "--config" "/path/to/rclone.conf" "GDrive:"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "GDrive:"
Enter configuration password:
password:
<7>DEBUG : Using config file from "/path/to/rclone.conf"
<7>DEBUG : Google drive root '': 'root_folder_id = 0AB6_yQrK6HBzUk9PVA' - save this in the config to speed up startup
<7>DEBUG : Stat: filePath="/"
<7>DEBUG : >Stat: fi=, err=<nil>
<7>DEBUG : ReadDir: dir=/
<7>DEBUG : >ReadDir: names=[], err=<nil>
/

0 directories, 0 files
<7>DEBUG : 4 go routines active

$ rclone  tree -vv --config /path/to/rclone.conf Crypt-GDrive:
<7>DEBUG : rclone: Version "v1.58.1" starting with parameters ["rclone" "tree" "-vv" "--config" "/path/to/rclone.conf" "Crypt-GDrive:"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "Crypt-GDrive:"
Enter configuration password:
password:
<7>DEBUG : Using config file from "/path/to/rclone.conf"
<7>DEBUG : Creating backend with remote "GDrive"
<7>DEBUG : fs cache: renaming cache item "GDrive" to be canonical "/home/asdf/GDrive"
<3>ERROR : : error listing: directory not found
<7>DEBUG : 2 go routines active
Failed to tree: directory not found

Any help or pointers would be appreciated. Like I said, when I run the same commands on the windows machine I get all the expected files.

hello and welcome to the forum,

rclone thinks GDrive is a local dir, as there is not a :

as per the docs
" Note: A string which do not contain a : will by rclone be treated as a relative path in the local filesystem. For example, if you enter the name remote without the trailing :, it will be treated as a subdirectory of the current directory with name "remote"."

"remote": "GDrive"
should be
"remote": "GDrive:"

as per the docs
"If you intend to use the wrapped remote both directly for keeping unencrypted content, as well as through a crypt remote for encrypted content, it is recommended to point the crypt remote to a separate directory within the wrapped remote"
so might want to specify a subdir, for example,
"remote": "GDrive:crypt"

Thanks! Ended up redoing the configuration with Crypt-GDrive: pointing to GDrive:Crypt and it now works smoothly on both machines.

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