Use Proxy only for a specific Cloud

Help and Support
1

What is the problem you are having with rclone?

I'm trying to migrate/sync between two different clouds. ( 1fichier and Google Drive. )

But I must to use a proxy, only to connect to 1fichier, and without proxy for Google Drive.

It's simple, my isp drop speed from 1fichier, and with proxy, works very well.

There is a way to connect only 1fichier with proxy and migrate between two clouds?

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

rclone v1.70.3
- os/version: Microsoft Windows 11 Pro 24H2 24H2 (64 bit)
- os/kernel: 10.0.26100.4770 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.24.4
- go/linking: static
- go/tags: cmount

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

1fichier and a Google Drive

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

copy "1fichier:/" "gdrive:/" --progress --verbose --multi-thread-streams 8 --checkers=16 --fast-list --multi-thread-write-buffer-size 32M --multi-thread-chunk-size 64M --buffer-size 64M

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

[1fichier]
type = fichier
api_key = 12345
https_proxy = https://192.168.178.173:3128/
2

See:

FAQ

1 Like
4

Use two different rclone sessions with only one using proxy:

rclone mount/serve -> rclone copy/sync

e.g.:

$ (export http_proxy=http://proxyserver:12345; rclone mount source_remote: /path/to/mountpoint)

and then

$ rclone copy /path/to/mountpoint destination_remote:
1 Like
5

with mount is more slow.

Seems that with this command in Windows 11 and Powershell, works:

$env:HTTPS_PROXY="http://192.168.178.173:3128"; $env:NO_PROXY="192.168.178.234"; .\rclone.exe copy "1fichier2:/" "gdrive:/" --progress --verbose --multi-thread-streams 8 --checkers=16 --fast-list --multi-thread-write-buffer-size 32M --multi-thread-chunk-size 64M --buffer-size 64M

So I use my local proxy on: http://192.168.178.173:3128

And I exclude gdrive, that is on 192.168.178.234

And seems that my local proxy, use bandwidth inside the proxy.

image
image753Ă—186 3.69 KB

1 Like
6

There's more than one way to skin a cat :slight_smile:

1 Like
7

I’ve run into the same thing—I only wanted a proxy on one remote, not all of them. What worked for me was setting the proxy just for that single command. For example in PowerShell:

$env:HTTPS_PROXY="http://your-proxy:port"
$env:NO_PROXY="other-remote-url"
.\rclone.exe copy "sourceRemote:/" "destRemote:/"

That way only the source uses the proxy, while the destination goes straight out. Another simple option is to run two Rclone sessions—one with the proxy set and one without—then move data between them

8

It is possible to do this with v1.71

You'd do it like this

[1fichier]
type = fichier
api_key = 12345
override.http_proxy = https://192.168.178.173:3128/

This is the equivalent of --http-proxy https://192.168.178.173:3128/ (which is also a new flag for v1.71) but just for the 1fichier remote.

9

Heyy.. Try running two separate rclone sessions. One goes through a proxy just for 1fichier, and the other talks to GD directly. Something like this works:

$ (export http_proxy=https://proxy-man.com:12345; rclone mount source_remote: /path/to/mountpoint)
10

welcome to the forum,

no longer a need for running two separate rclone sessions. rclone has a new feature

11

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