2015-12-30 20:45:43 +08:00
|
|
|
---
|
|
|
|
title: "Yandex"
|
|
|
|
description: "Yandex Disk"
|
|
|
|
---
|
|
|
|
|
2020-05-22 19:22:52 +08:00
|
|
|
{{< icon "fa fa-space-shuttle" >}}Yandex Disk
|
2015-12-30 20:45:43 +08:00
|
|
|
----------------------------------------
|
|
|
|
|
2017-03-29 20:38:34 +08:00
|
|
|
[Yandex Disk](https://disk.yandex.com) is a cloud storage solution created by [Yandex](https://yandex.com).
|
2015-12-30 20:45:43 +08:00
|
|
|
|
|
|
|
Here is an example of making a yandex configuration. First run
|
|
|
|
|
|
|
|
rclone config
|
|
|
|
|
|
|
|
This will guide you through an interactive setup process:
|
|
|
|
|
|
|
|
```
|
|
|
|
No remotes found - make a new one
|
|
|
|
n) New remote
|
2016-02-21 21:39:04 +08:00
|
|
|
s) Set configuration password
|
|
|
|
n/s> n
|
2015-12-30 20:45:43 +08:00
|
|
|
name> remote
|
2016-02-21 21:39:04 +08:00
|
|
|
Type of storage to configure.
|
|
|
|
Choose a number from below, or type in your own value
|
2019-08-26 17:47:17 +08:00
|
|
|
[snip]
|
|
|
|
XX / Yandex Disk
|
2016-02-21 21:39:04 +08:00
|
|
|
\ "yandex"
|
2019-08-26 17:47:17 +08:00
|
|
|
[snip]
|
|
|
|
Storage> yandex
|
2015-12-30 20:45:43 +08:00
|
|
|
Yandex Client Id - leave blank normally.
|
2017-01-09 13:09:19 +08:00
|
|
|
client_id>
|
2015-12-30 20:45:43 +08:00
|
|
|
Yandex Client Secret - leave blank normally.
|
2017-01-09 13:09:19 +08:00
|
|
|
client_secret>
|
2015-12-30 20:45:43 +08:00
|
|
|
Remote config
|
2016-02-21 21:39:04 +08:00
|
|
|
Use auto config?
|
|
|
|
* Say Y if not sure
|
|
|
|
* Say N if you are working on a remote or headless machine
|
|
|
|
y) Yes
|
|
|
|
n) No
|
|
|
|
y/n> y
|
2015-12-30 20:45:43 +08:00
|
|
|
If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth
|
|
|
|
Log in and authorize rclone for access
|
|
|
|
Waiting for code...
|
|
|
|
Got code
|
|
|
|
--------------------
|
|
|
|
[remote]
|
2017-01-09 13:09:19 +08:00
|
|
|
client_id =
|
|
|
|
client_secret =
|
2015-12-30 20:45:43 +08:00
|
|
|
token = {"access_token":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","token_type":"bearer","expiry":"2016-12-29T12:27:11.362788025Z"}
|
|
|
|
--------------------
|
|
|
|
y) Yes this is OK
|
|
|
|
e) Edit this remote
|
|
|
|
d) Delete this remote
|
|
|
|
y/e/d> y
|
|
|
|
```
|
|
|
|
|
2016-01-07 23:20:32 +08:00
|
|
|
See the [remote setup docs](/remote_setup/) for how to set it up on a
|
|
|
|
machine with no Internet browser available.
|
|
|
|
|
|
|
|
Note that rclone runs a webserver on your local machine to collect the
|
|
|
|
token as returned from Yandex Disk. This only runs from the moment it
|
|
|
|
opens your browser to the moment you get back the verification code.
|
|
|
|
This is on `http://127.0.0.1:53682/` and this it may require you to
|
|
|
|
unblock it temporarily if you are running a host firewall.
|
|
|
|
|
|
|
|
Once configured you can then use `rclone` like this,
|
2015-12-30 20:45:43 +08:00
|
|
|
|
|
|
|
See top level directories
|
|
|
|
|
|
|
|
rclone lsd remote:
|
|
|
|
|
|
|
|
Make a new directory
|
|
|
|
|
|
|
|
rclone mkdir remote:directory
|
|
|
|
|
|
|
|
List the contents of a directory
|
|
|
|
|
|
|
|
rclone ls remote:directory
|
|
|
|
|
|
|
|
Sync `/home/local/directory` to the remote path, deleting any
|
|
|
|
excess files in the path.
|
|
|
|
|
2020-06-06 00:04:23 +08:00
|
|
|
rclone sync -i /home/local/directory remote:directory
|
2015-12-30 20:45:43 +08:00
|
|
|
|
2019-10-05 17:22:43 +08:00
|
|
|
Yandex paths may be as deep as required, eg `remote:directory/subdirectory`.
|
|
|
|
|
2015-12-30 20:45:43 +08:00
|
|
|
### Modified time ###
|
|
|
|
|
|
|
|
Modified times are supported and are stored accurate to 1 ns in custom
|
|
|
|
metadata called `rclone_modified` in RFC3339 with nanoseconds format.
|
|
|
|
|
|
|
|
### MD5 checksums ###
|
|
|
|
|
|
|
|
MD5 checksums are natively supported by Yandex Disk.
|
2017-09-08 01:10:39 +08:00
|
|
|
|
|
|
|
### Emptying Trash ###
|
|
|
|
|
|
|
|
If you wish to empty your trash you can use the `rclone cleanup remote:`
|
|
|
|
command which will permanently delete all your trashed files. This command
|
|
|
|
does not take any path arguments.
|
2018-10-02 01:36:15 +08:00
|
|
|
|
2018-11-20 01:52:36 +08:00
|
|
|
### Quota information ###
|
|
|
|
|
|
|
|
To view your current quota you can use the `rclone about remote:`
|
|
|
|
command which will display your usage limit (quota) and the current usage.
|
|
|
|
|
2019-10-05 17:22:43 +08:00
|
|
|
#### Restricted filename characters
|
|
|
|
|
|
|
|
The [default restricted characters set](/overview/#restricted-characters)
|
|
|
|
are replaced.
|
|
|
|
|
|
|
|
Invalid UTF-8 bytes will also be [replaced](/overview/#invalid-utf8),
|
|
|
|
as they can't be used in JSON strings.
|
|
|
|
|
2018-12-29 16:40:45 +08:00
|
|
|
### Limitations ###
|
|
|
|
|
|
|
|
When uploading very large files (bigger than about 5GB) you will need
|
|
|
|
to increase the `--timeout` parameter. This is because Yandex pauses
|
|
|
|
(perhaps to calculate the MD5SUM for the entire file) before returning
|
|
|
|
confirmation that the file has been uploaded. The default handling of
|
|
|
|
timeouts in rclone is to assume a 5 minute pause is an error and close
|
|
|
|
the connection - you'll see `net/http: timeout awaiting response
|
|
|
|
headers` errors in the logs if this is happening. Setting the timeout
|
|
|
|
to twice the max size of file in GB should be enough, so if you want
|
|
|
|
to upload a 30GB file set a timeout of `2 * 30 = 60m`, that is
|
|
|
|
`--timeout 60m`.
|
|
|
|
|
2020-05-22 19:22:52 +08:00
|
|
|
{{< rem autogenerated options start" - DO NOT EDIT - instead edit fs.RegInfo in backend/yandex/yandex.go then run make backenddocs" >}}
|
2018-10-02 03:48:54 +08:00
|
|
|
### Standard Options
|
|
|
|
|
|
|
|
Here are the standard options specific to yandex (Yandex Disk).
|
|
|
|
|
|
|
|
#### --yandex-client-id
|
|
|
|
|
2020-09-02 23:59:04 +08:00
|
|
|
OAuth Client Id
|
2018-10-02 03:48:54 +08:00
|
|
|
Leave blank normally.
|
|
|
|
|
|
|
|
- Config: client_id
|
|
|
|
- Env Var: RCLONE_YANDEX_CLIENT_ID
|
|
|
|
- Type: string
|
|
|
|
- Default: ""
|
|
|
|
|
|
|
|
#### --yandex-client-secret
|
|
|
|
|
2020-09-02 23:59:04 +08:00
|
|
|
OAuth Client Secret
|
2018-10-02 03:48:54 +08:00
|
|
|
Leave blank normally.
|
|
|
|
|
|
|
|
- Config: client_secret
|
|
|
|
- Env Var: RCLONE_YANDEX_CLIENT_SECRET
|
|
|
|
- Type: string
|
|
|
|
- Default: ""
|
|
|
|
|
2018-11-24 21:44:25 +08:00
|
|
|
### Advanced Options
|
|
|
|
|
|
|
|
Here are the advanced options specific to yandex (Yandex Disk).
|
|
|
|
|
2020-09-02 23:59:04 +08:00
|
|
|
#### --yandex-token
|
2018-11-24 21:44:25 +08:00
|
|
|
|
2020-09-02 23:59:04 +08:00
|
|
|
OAuth Access Token as a JSON blob.
|
2018-11-24 21:44:25 +08:00
|
|
|
|
2020-09-02 23:59:04 +08:00
|
|
|
- Config: token
|
|
|
|
- Env Var: RCLONE_YANDEX_TOKEN
|
|
|
|
- Type: string
|
|
|
|
- Default: ""
|
|
|
|
|
|
|
|
#### --yandex-auth-url
|
|
|
|
|
|
|
|
Auth server URL.
|
|
|
|
Leave blank to use the provider defaults.
|
|
|
|
|
|
|
|
- Config: auth_url
|
|
|
|
- Env Var: RCLONE_YANDEX_AUTH_URL
|
|
|
|
- Type: string
|
|
|
|
- Default: ""
|
|
|
|
|
|
|
|
#### --yandex-token-url
|
|
|
|
|
|
|
|
Token server url.
|
|
|
|
Leave blank to use the provider defaults.
|
|
|
|
|
|
|
|
- Config: token_url
|
|
|
|
- Env Var: RCLONE_YANDEX_TOKEN_URL
|
|
|
|
- Type: string
|
|
|
|
- Default: ""
|
2018-11-24 21:44:25 +08:00
|
|
|
|
2020-02-01 18:31:42 +08:00
|
|
|
#### --yandex-encoding
|
|
|
|
|
|
|
|
This sets the encoding for the backend.
|
|
|
|
|
|
|
|
See: the [encoding section in the overview](/overview/#encoding) for more info.
|
|
|
|
|
|
|
|
- Config: encoding
|
|
|
|
- Env Var: RCLONE_YANDEX_ENCODING
|
|
|
|
- Type: MultiEncoder
|
|
|
|
- Default: Slash,Del,Ctl,InvalidUtf8,Dot
|
|
|
|
|
2020-05-22 19:22:52 +08:00
|
|
|
{{< rem autogenerated options stop >}}
|