Create Config Always Fails on Users System

What is the problem you are having with rclone?

RClone fails to create a Config with the following error:
Error: config failed to refresh token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

I am only seeing this on one colleagues Windows 11 system.

I had tried running rclone with rcd and using --addr localhost:0 to allow get an available port from the system.
Then I issued the command again using -rc, json and the address and port returned by the rcd call.
That too returned the same error.

Additionally I have cleared the browser cache before each attempt as well.

We also retried with all Firewall and Antivirus turned off

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

rclone v1.61.1

  • os/version: Microsoft Windows 10 Pro 22H2 (64 bit)
  • os/kernel: 10.0.19045.2965 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.19.4
  • go/linking: static
  • go/tags: cmount

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

Google Drive

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

C:\Program Files\IDM Computer Solutions\Common\UltraCloudStorage>rclone config create GoogleDriveTest3 drive --log-file "C:\temp\uftp\rclone\rclone_log.txt" -vv

The rclone config contents with secrets removed.

Note: It appears to have created an entry but because of the authetication error there is little information filled out for the account.

[GoogleDrive]
type = drive
auth_url = 

A log from the command with the -vv flag

2023/07/06 14:43:56 DEBUG : rclone: Version "v1.61.1" starting with parameters ["rclone" "config" "GoogleDriveTest3" "drive" "--log-file" "C:\\temp\\uftp\\rclone\\rclone_log.txt" "-vv"]
2023/07/06 14:45:43 DEBUG : rclone: Version "v1.61.1" starting with parameters ["rclone" "config" "create" "GoogleDriveTest3" "drive" "--log-file" "C:\\temp\\uftp\\rclone\\rclone_log.txt" "-vv"]
2023/07/06 14:45:43 DEBUG : Using config file from "C:\\Users\\Troy Pennington\\AppData\\Roaming\\rclone\\rclone.conf"
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config in: state="", result=""
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config out: out=&{State:*oauth,teamdrive,, Option:<nil> OAuth:<nil> Error: Result:}, err=<nil>
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config in: state="*oauth,teamdrive,,", result=""
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config out: out=&{State:*oauth-confirm,teamdrive,, Option:<nil> OAuth:<nil> Error: Result:}, err=<nil>
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config in: state="*oauth-confirm,teamdrive,,", result=""
2023/07/06 14:45:43 DEBUG : Auto confirm is set, choosing default "true" for state "*oauth-islocal,teamdrive,,", override by setting config parameter "config_is_local"
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config out: out=&{State:*oauth-islocal,teamdrive,, Option:<nil> OAuth:<nil> Error: Result:true}, err=<nil>
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config in: state="*oauth-islocal,teamdrive,,", result="true"
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config out: out=&{State:*oauth-do,teamdrive,, Option:<nil> OAuth:<nil> Error: Result:}, err=<nil>
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config in: state="*oauth-do,teamdrive,,", result=""
2023/07/06 14:45:43 DEBUG : Starting auth server on 127.0.0.1:53682
2023/07/06 14:45:43 DEBUG : GoogleDriveTest3: config out: out=<nil>, err=config failed to refresh token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
2023/07/06 14:45:43 Fatal error: config failed to refresh token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

It looks like some windows policies being very strict and not allowing any server. Is it some sort of corporate computer?

Whatever reason - which is really Windows problem not rclone you can use Remote Setup

And authenticate it on another computer

If I understand correctly with the authentication/token information stored in the Config, this will allow rclone on the target machine to successfully connect out ( assuming it is not totally blocked by firewall/policy )?

You understand it correctly:)

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