Failed to rc: connection failed: Post http://localhost:5572/core/stats: dial tcp [::1]:5572: connectex

[ghost]

Hello,2020/04/30 23:22:00 Failed to rc: connection failed: Post http://localhost:5572/core/stats: dial tcp [::1]:5572: connectex: No connection could be made because the target machine actively refused it how to fix that?

[ghost]

I even opened the port on my router

[theg00s3]

Do you have a firewall installed on your machine? If so, allow access for that port, or temporarily disable it

[mesoller]

It happened to me as well, because I missed this steps:

Add service accounts into your source Team Drive: python3 add_to_team_drive.py -d SharedTeamDriveSrcID

Add service accounts into your destination Team Drive: python3 add_to_team_drive.py -d SharedTeamDriveDstID

Where the script unable to find the source and destination Team Drive ID

[theg00s3]

It is recommended to add the service accounts to a google group first

[thegreatestminer]

The same is happening for me, but this was working just yesterday...

[theg00s3]

@thegreatestminer has the source or destination drive been deleted?

[thegreatestminer]

@theg00s3 Nope. Both the source and the destination still exist.

One strange thing, is that before it starts copying, it starts checking for files that already exist, but when it attempts to copy after that, it fails.

2020/06/03 09:26:13 Failed to rc: connection failed: Post http://localhost:5572/
core/stats: dial tcp [::1]:5572: connectex: No connection could be made because
the target machine actively refused it.
No rclone task detected (possibly done for this account). (2/3)
start /b rclone --config ./rclone.conf copy --drive-server-side-across-configs -
-rc --rc-addr="localhost:5572" -vv --ignore-existing --tpslimit 3 --transfers 3
--drive-chunk-size 32M --drive-acknowledge-abuse --log-file=log_rclone.txt "src0
03:" "dst003:"
>> Let us go dst003: 09:26:13
dst003: reading source/destination | checks: 22207 files

[theg00s3]

That's odd. Does anything show up in the logs?

[aomini]

@thegreatestminer did you fixed it? same error for me. +1

[pras92]

@thegreatestminer has the source or destination drive been deleted?

Had the same issue when it was working fine up till a few hours ago. In my case, i was doing a local to cloud transfer and while both the source and destination haven't been deleted, it appears one of the local dir in the dir path was auto renamed (by another program) and correcting it fixed it for me.