Error connection external resources

What is the problem you are having with rclone?

Hi,
I have several connections configured on rclone to external clouds on Onedrive and Google that work correctly for some time.
After a few weeks it no longer connects.

I suspect there is a connection problem on rclone because the selfupdate command also gives an error.
The file indicated in the log "https://downloads.rclone.org/version.txt" is downloaded correctly to the system with a wget command.
if I reboot the machine everything works fine

Can anyone help me ?

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

rclone v1.67.0

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

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

Onedrive and DropBox

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

2025/03/18 09:09:05 Failed to create file system for "remote:tmp": didn't find section in config file

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


[OneDrive_official]
type = onedrive
token = XXX
drive_id = XXX
drive_type = personal

[bkp_onedrive]
type = onedrive
token = XXX
drive_id = XXX
drive_type = personal

[dropbox]
type = dropbox
token = XXX
### Double check the config for sensitive info before posting publicly

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

 rclone lsf OneDrive_official: --log-level DEBUG
2025/03/18 09:07:08 DEBUG : rclone: Version "v1.67.0" starting with parameters ["rclone" "lsf" "OneDrive_official:" "--log-level" "DEBUG"]
2025/03/18 09:07:08 DEBUG : Creating backend with remote "OneDrive_official:"
2025/03/18 09:07:08 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2025/03/18 09:07:08 DEBUG : OneDrive_official: Loaded invalid token from config file - ignoring
2025/03/18 09:07:08 DEBUG : OneDrive_official: Token refresh failed try 1/5: Post "https://login.microsoftonline.com/common/oauth2/v2.0/token": dial tcp: lookup login.microsoftonline.com on [::1]:53: read udp [::1]:45846->[::1]:53: read: connection refused
2025/03/18 09:07:09 DEBUG : OneDrive_official: Loaded invalid token from config file - ignoring
2025/03/18 09:07:09 DEBUG : OneDrive_official: Token refresh failed try 2/5: Post "https://login.microsoftonline.com/common/oauth2/v2.0/token": dial tcp: lookup login.microsoftonline.com on [::1]:53: read udp [::1]:57875->[::1]:53: read: connection refused


rclone selfupdate --log-level DEBUG
2025/03/18 08:38:38 DEBUG : rclone: Version "v1.67.0" starting with parameters ["rclone" "selfupdate" "--log-level" "DEBUG"]
2025/03/18 08:38:38 Error: unable to detect new version: Get "https://downloads.rclone.org/version.txt": dial tcp: lookup downloads.rclone.org on [::1]:53: read udp [::1]:55860->[::1]:53: read: connection refused


wget https://downloads.rclone.org/version.txt
--2025-03-18 08:35:13--  https://downloads.rclone.org/version.txt
Risoluzione di downloads.rclone.org (downloads.rclone.org)... 95.217.6.16, 2a01:4f9:c012:7154::1
Connessione a downloads.rclone.org (downloads.rclone.org)|95.217.6.16|:443... connesso.
Richiesta HTTP inviata, in attesa di risposta... 200 OK
Lunghezza: 15 [text/plain]
Salvataggio in: «version.txt»

version.txt                                100%[=====================================================================================>]      15  --.-KB/s    in 0s

2025-03-18 08:35:14 (10,3 MB/s) - «version.txt» salvato [15/15]



Looks like some issues with IPv6 configuration on your end. It happens sometimes and is often related to ISP or local LAN misconfiguration. In your case it manifests as DNS connectivity refusal.

Either try with --bind 0.0.0.0 flag forcing IPv4 only or download the latest version directly from here.

When on the latest rclone version let's see if your other issues persist.

Moving forward fix your network configuration or always force IPv4 only.

PS. I can see in your last year post the same problem:

You definitely have some problems with your network.

Correct, I found out that my system didn't have DNS configured correctly, but it still worked.
I've fixed it

Thank you

1 Like

Well done with fixing it. These are the most difficult cases to troubleshoot:) It is much easier when something is totally broken compared to often nuisance randomly working or not part.

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